What is the test_cookie cookie?
test_cookie is set by the doubleclick.net domain, Google's advertising platform. Google describes its purpose as checking whether the user's browser supports cookies before other DoubleClick advertising scripts are activated.
It typically appears when a Google Ads, Google Marketing Platform, or DoubleClick-served ad tag is running on a site, even if the site doesn't display Google ads directly but only uses a conversion or remarketing pixel.
What data it stores
The stored value is minimal, essentially a boolean flag (usually "1"), and contains no user-identifying information. It is set on the doubleclick.net domain, making it a third-party cookie from the visited site's perspective.
The cookie's data isn't transmitted separately, but its presence signals to Google and other DoubleClick-family scripts that the environment accepts cookies, which then allows the actual tracking and advertising cookies to be set afterward.
What it is used for
For Google, test_cookie is a technical checkpoint: if the browser blocks cookies, the DoubleClick advertising stack avoids loading further scripts unnecessarily. It has no direct role in behavioral measurement or ad targeting on its own.
For a site owner, the presence of this cookie confirms that a Google advertising tag (Ads, DV360, GAM, etc.) is active and will typically set additional marketing/tracking cookies afterward.
Does it require consent?
Although the cookie's technical purpose seems harmless, test_cookie is set by a third-party advertising domain and belongs to a flow that leads, directly or indirectly, to ad tracking. Under Romania's Law 506/2004 and ANSPDCP guidance implementing the ePrivacy Directive, marketing/advertising cookies require prior user consent regardless of their short lifespan.
Site owners should classify this cookie under the "marketing" category in their cookie policy and ensure the script generating it (Google Ads/DoubleClick tag) doesn't load before explicit consent is obtained.
How to block or delete test_cookie
Visitors can delete or block this cookie from their browser settings (Chrome, Firefox, Edge, Safari – "Cookies and site data" section), including by disabling third-party cookies generally or using dedicated privacy extensions.
- Site owners must block the Google/DoubleClick script that generates this cookie until consent is given.
- A CMP such as CookieFix can automate this, keeping marketing scripts disabled by default and activating them only after the visitor accepts the "marketing" category.
Frequently asked questions
No, its value is minimal and doesn't directly identify the user. It is, however, part of a chain of Google DoubleClick scripts oriented toward advertising.
Because many sites use Google conversion or remarketing pixels (e.g. Google Ads), which load the DoubleClick infrastructure even without displaying banner ads.
Yes, since it's tied to Google's advertising infrastructure, it's classified as marketing and requires prior consent under Law 506/2004 and ANSPDCP guidance.
It's a short-term technical check cookie; the brief duration reflects its narrow purpose of testing browser cookie support at the moment the script loads.