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
    • 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
      • What's New
      • Importing the Cartridge
      • Registering the Cartridge
      • Importing Metadata and Services
      • Configuring the Cartridge
      • Using the Cartridge
      • SCAPI Protection Considerations
      • Upgrading
      • Customized Block Page
      • Configuration Options
      • First Party
LogoLogo
Login
Login
HUMAN DashboardHUMAN WebsiteRequest a Demo
On this page
  • Configuring URL Redirection for Client File
  • Enabling First Party
Enforcer frameworksSalesforce Commerce Cloud Cartridge

First Party

Was this page helpful?
Previous

Varnish changelog

Next
Built with

Enabling First Party serves the HUMAN client and Captcha files from your local domain. This is recommended, as it helps prevent blocking the HUMAN JavaScript files by privacy plugins and ad blockers.

Configuring URL Redirection for Client File

  1. In Merchant Tools, select Site URLs -> Dynamic Mapping.
  2. Add the following above the catch-all rule:
1/px/** p,,,PXFP-Handle,,src,{0}

Enabling First Party

  1. In Merchant Tools, select Site Preferences -> Custom Preferences.
  2. In the Custom Site Preference Groups, click PXConfig.
  3. In the top left section of the form, select your current Instance Type (default is Sandbox).
  4. Navigate to the First Party Enabled property and change its value to True.
Important

You must let HUMAN Support know that you are configuring the HUMAN Sales Force Commerce Cloud cartridge to handle First Party requests, as there are configurations that need to be made on the backend. If you do not notify Support, your First Party configuration will not work.

After configuring HUMAN within Sales Force Commerce Cloud cartridge to handle First Party requests, complete the steps listed on the Integrate 1st-Party JS Snippet to make sure your snippet is setup to serve the Javascript Sensor via First Party.