> This page is for Applications Protection.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.humansecurity.com/llms.txt.

# First Party

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**:

```javascript
/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](/applications/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](/applications/integrate-1st-party-client) to make sure your snippet is setup to serve the Javascript Sensor via First Party.