> 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.

# JavaScript snippet

## Integrate 3rd-Party Client

### Background

The third-party snippet serves the sensor and manages server communication. Insert the snippet on all pages you want to protect.

### Deploy

See our Getting Started guide for [3rd-Party JS Snippet Integration](/applications/getting-started-with-sightline-cyberfraud-defense#2-integrate-the-sensor) for more details.

## Integrate 1st-Party Client

### Background

The first party mechanism is a way for serving Sensor and for sending activities using your domain (1st party) rather than our own domains (3rd party).\
1st party is needed since 3rd party scripts and XHR request can get blocked either by network policy or privacy tools (like ad blockers) - we see more and more privacy tools targeting 3rd party scripts.\
The first party mechanism uses the enforcer as a proxy, taking advantage of the fact that the enforcer runs on your server. The enforcer uses predefined reserved routes for first party.

### Deploy

See our Getting Started guide for [1st-Party JS Snippet Integration](/applications/getting-started-with-sightline-cyberfraud-defense#2-integrate-the-sensor) for more details.