Skip to main content

Akamai sensor data

Challenge/Akamai

Also known as sensor_data, Akamai sensor

Akamai sensor data is the payload that Akamai Bot Manager's client-side script builds in the browser from environment and behavior signals and POSTs to the site's Akamai script endpoint. A valid submission updates the _abck cookie.

How to recognize it

How to recognize it
Request
A POST to the dynamic Akamai script path with a JSON body containing a single sensor_data field
Response
A Set-Cookie that updates _abck
Pattern
Several of these POSTs during one page visit in a browser capture

What sensor data is

Akamai Bot Manager does not ask the browser to solve anything visible. Its script runs in the background, collects information about the browser environment and about how the page is being used, and sends the result back to Akamai as sensor data. Akamai uses that payload to decide whether the session behaves like a real browser.

The payload is generated by Akamai's own script, and its contents and encoding change between script versions. For a developer, three facts matter more than the format:

  • it is built from the current script the page loaded, not from a fixed template;
  • each post builds on the previous one in the same session;
  • its only visible effect is an updated _abck cookie.

Where it is sent

The Bot Manager script is loaded from a long, randomly generated path near the end of the page's HTML. That path is different per site and can change from one session to the next, so it cannot be hardcoded. The browser posts the sensor data back to the same path as a JSON body with a single sensor_data field. Akamai answers with a Set-Cookie header that updates _abck.

  1. First page load: the site sets an unvalidated _abck and a bm_sz cookie, and the HTML references the script path.
  2. Sensor posts: the browser posts sensor data, often several times during one visit. Each accepted post updates _abck. On many sites a validated cookie contains the marker ~0~.
  3. Protected action: login, add-to-cart or checkout checks _abck. Afterwards the cookie is usually invalidated.
  4. Next protected action: new sensor data is needed.

The Hyper Solutions flow posts at most three sensors per round. If _abck is still invalid after three, the problem is usually the client, not the payload.

How to recognize sensor traffic in a capture

In a HAR file or proxy capture of a real Chrome session, look for:

  • a GET to the long script path, right after the page HTML;
  • one or more POSTs to that same path with a JSON body that contains sensor_data;
  • a Set-Cookie for _abck in each POST response;
  • on some sites, a second script with a ?v= query parameter. That is SBSD, a separate Akamai check with its own payload.

No sensor posts in a capture does not always mean you missed them. Some Akamai sites never post sensor data: the script puts it in an Akamai-BM-Telemetry request header on each protected API call instead, and the API answers 403 without a valid one. An "Access Denied" page from AkamaiGHost with a Reference # ID is different again: it is an edge or WAF rule, and no sensor data changes it.

Why sensor data gets rejected

A correctly generated payload still fails when the rest of the session gives the client away:

  • the TLS fingerprint or HTTP/2 settings do not match Chrome;
  • the header order differs from the browser's;
  • the User-Agent or IP address changes between the page load and the sensor posts;
  • the script path or script content comes from another session.

Generating sensor data that Akamai accepts requires the current script and a client that matches the browser it claims to be. The Hyper Solutions Akamai API generates the payload from a single call; your client fetches the script, posts the result and keeps the session consistent. The step-by-step flow is in the Akamai getting-started docs.

Questions

What is Akamai sensor data?

It is the payload Akamai Bot Manager's background script builds from browser environment and behavior signals. The browser posts it to the site's Akamai script path, and Akamai answers by updating the _abck cookie.

Where is Akamai sensor data sent?

To the same long, randomly generated path the Bot Manager script was loaded from, as a POST with a JSON body containing a single sensor_data field. The path differs per site, can change between sessions and cannot be hardcoded.

How many sensor posts are needed?

It depends on the site. Many sites mark a validated _abck with ~0~, after which no more posts are needed. Where that marker is missing, the Hyper Solutions flow posts three sensors before the protected action.

Why is my Akamai sensor data rejected?

Usually because the client around it does not match a browser: a non-Chrome TLS fingerprint, a different header order, or a User-Agent or IP address that changed during the session. A script path or script from another session also causes rejections.

Is sensor data the same as SBSD?

No. SBSD is a separate Akamai check with its own script and its own payload. Sites can use both.

Further reading

Technical review: Hyper Solutions engineering, Nov 18, 2026