Skip to main content

datadome cookie

Cookie/DataDome

Also known as DataDome cookie

datadome is the cookie DataDome uses to identify a client session. DataDome sets it on the protected site's responses, including block pages, and issues a new value when a challenge is solved or telemetry is accepted. The current value goes with every later request.

How to recognize it

How to recognize it
Cookie
datadome
API response
A JSON body with "cookie": "datadome=..." after a slider or interstitial check
API response
The same JSON shape after a tags POST to the /js/ endpoint

DataDome hands out the datadome cookie in two different ways, and a request-based client has to handle both:

  • As a normal Set-Cookie header on responses from the protected site, including the 403 block page. The value from the block page is part of the challenge link, so it has to be kept.
  • Inside a JSON body. When a slider captcha or an interstitial is solved, and when telemetry ("tags") is posted to DataDome's /js/ endpoint, the response is JSON with a cookie field. That field contains the complete cookie string, including its domain and expiry.

The second case is where most clients go wrong. A cookie that arrives inside a JSON body is not a Set-Cookie header, so an HTTP library's cookie jar does not pick it up. Your code has to parse the JSON and set the cookie itself, on the domain given in the string.

When the value changes

The cookie string carries a Max-Age of one year, but the value is replaced much more often:

  • after every solved slider or interstitial;
  • after each accepted tags post. In the Hyper Solutions flow, tags are posted twice, and the second post uses the cookie returned by the first;
  • on block pages, which set a value of their own.

Each new value replaces the previous one. Sending an older value after a newer one has been issued is a common cause of challenge loops.

Most persistent DataDome blocks with a "valid" cookie come down to one of these:

  • The JSON cookie was never applied. The challenge was solved, but the next request still carried the old value.
  • Wrong domain. The cookie string names the domain it belongs to, often the parent domain. Set it there, or requests to a subdomain go out without it.
  • Parallel workers overwrite each other. Sessions that share one cookie jar mix values from different solves.
  • The value outlived its session. A cookie earned with one IP address, User-Agent and set of client hints does not carry over to another.

If the block page's dd object contains 't':'bv', the IP address itself is blocked. Solving the challenge and storing the new cookie changes nothing; the session needs another IP. If blocks continue on a clean IP, look at the rest of the request: the TLS fingerprint, the header order and how the capture you copied it from was recorded. Request-based scraping against DataDome only holds when the cookie and the request around it both look like the same browser.

It is a security cookie set by DataDome's bot protection, not an advertising cookie. According to DataDome's documentation, its value is encrypted and contains no personally identifiable information.

The full challenge and tags flows are in the DataDome getting-started docs. The Hyper Solutions DataDome API generates the slider, interstitial and tags payloads that produce a new cookie.

Questions

What is the datadome cookie?

It is the session cookie DataDome's bot protection uses to recognize a client. DataDome sets it on the site's responses and issues a new value whenever a challenge is solved or telemetry is accepted. Every later request has to carry the current value.

How long does the datadome cookie last?

The cookie string carries a Max-Age of one year, but in practice the value is replaced far more often: after every solved challenge, after accepted telemetry posts and on block pages. Always send the most recent value.

Why does DataDome keep blocking me with a valid cookie?

Usually because the newest value was never applied, because it was set on the wrong domain, or because the cookie was earned in a different session (another IP address, User-Agent or set of client hints). If the block page shows 't':'bv', the IP itself is blocked.

Where do I get the new datadome cookie after solving a challenge?

From the JSON response of the challenge check. It contains a cookie field with the complete cookie string. Parse it and set it in your cookie jar yourself, because it does not arrive as a Set-Cookie header.

Is the datadome cookie a tracking cookie?

No. It is a security cookie for bot detection. DataDome's documentation states that its value is encrypted and contains no personally identifiable information.

Further reading

Technical review: Hyper Solutions engineering, Nov 18, 2026