Where the datadome cookie comes from
DataDome hands out the datadome cookie in two different ways, and a request-based client has to handle both:
- As a normal
Set-Cookieheader 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 acookiefield. 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.
Why your cookie jar has to keep it current
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.
When a new cookie does not help
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.
Is it a tracking cookie?
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.