Skip to main content

_abck cookie

Cookie/Akamai

Also known as abck, Akamai _abck

_abck is the main cookie of Akamai Bot Manager. The protected site sets it, and it becomes valid after the browser posts sensor data to the site's Akamai script endpoint. Protected actions such as login, add-to-cart or checkout check it.

How to recognize it

How to recognize it
Cookie
_abck
Cookie
bm_sz
Script
A script tag with a long, dynamically generated path near the end of the HTML body
Cookie value
Contains ~0~ once the session is validated, on sites that use this marker
Symptom
Page loads work, but protected actions (login, add-to-cart, checkout) fail

The first response from an Akamai-protected site sets the _abck cookie together with bm_sz. At that point the cookie exists, but it is not valid yet: it only marks a client that has not proven anything.

The same HTML loads Akamai Bot Manager's script from a long, randomly generated path near the end of the body. In a browser, that script collects sensor data and posts it back to the same path. Every accepted post returns a Set-Cookie header with an updated _abck.

Ordinary page loads do not depend on the cookie. Akamai checks it when the client performs an action the site has marked as protected: typically login, add-to-cart, checkout or a search API. That is why a scraper can read product pages for hours and still fail on the first add-to-cart.

Valid or invalid: what to look for

  • Right after the first page load: _abck is present, but not validated.
  • After accepted sensor posts: many sites write ~0~ into the cookie value once the session is validated. Not every site uses this marker. Where it is missing, the Hyper Solutions flow posts a fixed number of sensors (three) before the protected action.
  • After a protected action: the cookie is usually invalidated again. The next protected action needs fresh sensor data.
  • Never validates: if _abck stays invalid after three posts, the cause is usually the client rather than the sensor: a handshake that does not match Chrome's TLS fingerprint, a header order no browser sends, or an IP address that changed mid-session.

The Hyper Solutions SDKs include a helper that reads the stop signal in the cookie and compares it with the number of sensors you posted (IsCookieValid in Go, is_cookie_valid in Python). On sites without the marker it stays false, so you stop after three posts yourself.

The cookies around it

Akamai Bot Manager sets more than one cookie, and you will usually see them together in a capture:

  • bm_sz is set on the first response. Its value is an input when sensor data is generated, so it has to come from the same session.
  • ak_bmsc and bm_sv are further Bot Manager cookies. The sensor flow does not use them as inputs. A few sites also run Akamai's pixel check, which validates ak_bmsc with its own payload. Keep both in your cookie jar and send them back the way the browser does.
  • Some sites also run SBSD, a separate Akamai check with its own script and its own payload.

A validated _abck belongs to the session that earned it. The same values Akamai saw while the sensors were posted have to stay the same until the protected action:

  • the TLS fingerprint and HTTP/2 settings of your client;
  • the User-Agent and the client hints that go with it;
  • the exact header order of every request;
  • the IP address, which is why rotating proxies break the flow halfway.

Copying a valid _abck from your own browser into a script rarely works for long. The protected action invalidates it, and the next one needs a new round of sensor data from a client that matches the session.

When the block is not about _abck

Not every Akamai block comes from this cookie. An "Access Denied" page from a server named AkamaiGHost, with a Reference # ID, is an edge or WAF rule: there is no challenge to solve, and a valid _abck does not change it. Fix the IP and the client first. Some Akamai sites also never post sensor data; their protected API calls carry an Akamai-BM-Telemetry request header instead, and the API answers 403 without a valid one.

Where to go next

The full flow, from parsing the script path to posting sensor data, is in the Akamai getting-started docs and the request-based Akamai guide. The Hyper Solutions Akamai API generates the sensor data, so your client only has to fetch the script, post the payload and keep the session consistent.

Questions

What is the _abck cookie used for?

Akamai Bot Manager uses _abck to decide whether a client may perform protected actions such as login, add-to-cart or checkout. The cookie starts out unvalidated and becomes valid after the Bot Manager script has posted sensor data that Akamai accepts.

How do I know if my _abck cookie is valid?

On many sites a validated _abck contains the marker ~0~. Not every site uses it; there, three accepted sensor posts are the practical threshold. The real test is whether the protected action succeeds.

Why does my _abck cookie stop working after login or checkout?

That is expected. Akamai usually invalidates _abck after a protected action, so the next protected action needs fresh sensor data posted from the same session.

Can I copy the _abck cookie from my browser into my scraper?

Rarely for long. The cookie is invalidated after protected actions, and Akamai expects the TLS fingerprint, headers and IP address of the session that earned it. A script that differs on those points gets an invalid cookie back.

Is the _abck cookie a tracking cookie?

No. It is a security cookie set by the site's bot protection, not an advertising cookie. Blocking it in a browser usually leads to extra checks or failed actions on Akamai-protected sites.

Further reading

Technical review: Hyper Solutions engineering, Nov 18, 2026