For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
HUMAN DashboardHUMAN WebsiteRequest a Demo
Product GuidesEnforcer GuidesMobile SDKAPI ReferenceCustomer support
Product GuidesEnforcer GuidesMobile SDKAPI ReferenceCustomer support
  • General
    • About Enforcers
    • Support first-party HUMAN calls
    • Troubleshoot Enforcer configurations
  • Enforcer frameworks
    • Akamai ESI
      • Akamai ESI changelog
      • Installation
      • Configuration
      • First Party Configuration
    • Apache - C Module
    • ASP.NET
    • Callout Enforcer
    • Envoy Proxy
    • F5 BIGIP
    • Fastly JavaScript Compute@Edge
    • Google Cloud Platform (GCP) Callout Enforcer
    • Kong Plugin
    • NGINX - C Module
    • NGINX - LUA Module
    • PHP
    • Python
    • Ruby
    • Salesforce Commerce Cloud Cartridge
LogoLogo
Login
Login
HUMAN DashboardHUMAN WebsiteRequest a Demo
Enforcer frameworksAkamai ESI

First Party Configuration

In First Party Mode, the HUMAN Akamai ESI Enforcer acts as a reverse proxy for client requests and sensor activity.

As an Edge Enforcer, the Akamai ESI Enforcer is configured with First-Party enabled by default. In case of failover, the Javascript Snippet sends requests directly to the HUMAN servers in Third-Party Mode.

To confirm that you have configured your HUMAN Akamai ESI Enforcer in First-Party mode,

  1. Login to Akamai Property Manager
  2. Make sure that the PX_FIRST_PARTY_ENABLED property variable is set to true
  3. After configuring the Enforcer to handle First-Party requests, complete the steps in the Integrate 1st-Party JS Snippet section to make sure your snippet is setup to serve the Javascript Sensor via First-Party.
Was this page helpful?
Previous

Apache - C Module

Next
Built with