What is the datadome cookie?

Last reviewed 10 November 2026 · 5 min read

Short answer: datadome is the cookie DataDome sets once a client has been cleared. It packs a client-side signal payload plus a signature, and it is short-lived and fingerprint-bound. It is also the cookie people blame for the wrong problem: most DataDome blocks are caused by the client's behaviour before the cookie is ever issued.

How DataDome decides

DataDome runs a script on the page that fingerprints the browser: canvas, WebGL, fonts, timezone, hardware and a dozen smaller tells. The result is POSTed and answered with a cookie. The decision point is that POST — not your HTTP headers, and not the cookie itself.

Which is why the usual sequence looks like this:

1. Your script requests a page and gets 403 with a DataDome captcha or interstitial.
2. You rotate the proxy and retry.
3. You get blocked faster, and on more URLs than before.

Rotating the exit IP changes the strongest single signal DataDome has. A fresh IP with the same broken fingerprint reads as a bot evading a ban, so the score drops rather than resets.

Two different challenges

They need different handling, and mixing them up wastes a lot of API budget.

Keeping the cookie alive

• Stay on one IP. DataDome pins clearance to the exit that earned it. Proxy rotation should happen between sessions, not inside one.
• Keep the user agent and TLS stack consistent. A cookie earned by a real browser and replayed by requests is a mismatch DataDome detects cheaply.
• Refresh on a schedule, not on error. By the time you see a 403, the session is already scored; solving then costs more than rotating the whole session did.
• Slow the first requests. A brand-new session that hits ten URLs in two seconds is scored on that pattern alone.

Where the API fits

For scripted workloads, a solving API is the pragmatic path: it runs the interstitial in a controlled browser, returns the datadome cookie, and (with SolveHub at least) tells you which proxy exit to send the real traffic through. SolveHub handles DataDome interstitial and slider tasks on one REST endpoint, billed per completed task.

FAQ

Does the cookie survive a page reload? Yes, until it expires or the session is re-scored. It does not survive an IP change.

Can I reuse it across workers? Only from the same IP and fingerprint. Otherwise it is worse than having no cookie, because it looks like replay.

Is datadome the same for every site? No — each customer has its own configuration and keys, so a cookie is valid for one site only.