Collector posts (_px2, _px3)
POST /perimeterx/collector · €1.50 / 1,000You have PerimeterX when a page loads main.min.js from a px-cloud.net or px-cdn.net host, or an init.js from a short path on its own domain, and the site sets _pxhd or _pxvid. Fetch the script once and send it to us with the page's URL, your user agent, IP and language.
We answer with the collector URL and the form body to post there. Post it from your client and keep the collector's reply: send it back as collectorResponse with the context from our answer, and the next post continues the same page load. The reply that carries the bake command sets _px2 and _px3.
The script has hundreds of fields to report, from navigator properties, WebGL and fonts to focus, visibility and pointer activity. Each event is serialised, masked and encoded with noise placed where the session's id says, and checked by an integrity digest. When the site ships a new build we haven't read, the API answers 409 unknown_build: send the script again and carry on.
- userAgent
- Chrome on Windows or macOS
- pageUrl
- The page that loaded the sensor
- ip
- Your proxy's exit IP (required)
- acceptLanguage, zone
- Your language and time zone
- script / build
- init.js once, then its 16-character build id
- collectorResponse
- The collector's last reply
- context
- From our previous answer
- newPage
- true when the visit moves to a new page
- url
- collector-<app id>.px-cloud.net/api/v2/collector
- body
- payload=…&appId=…, form-encoded
- build
- Send it instead of the script next time
- context
- Sealed session state for the next call