What is the audit cookie?
The audit cookie belongs to Rubicon Project, an ad-tech company that now operates under the name Magnite, one of the largest independent sell-side platforms (SSP) for programmatic advertising.
It is set from the .rubiconproject.com domain, typically when a webpage loads ad units participating in RTB (real-time bidding) auctions run through Magnite's infrastructure. It commonly appears on content, news, or blog sites that monetize ad space through programmatic networks including Rubicon Project as an SSP partner.
What data it stores
The cookie typically stores a unique identifier associated with the visitor's browser, used to correlate events across the ad-bidding chain (request, bid, ad delivery). The exact value format is not publicly documented by the provider and may vary.
The collected data is sent to Rubicon Project/Magnite servers and may be shared within the programmatic ecosystem (publishers, agencies, other ad-tech platforms) for ad delivery verification and fraud prevention purposes.
What it is used for
The stated purpose of the audit cookie is to support verification (audit) processes within the programmatic advertising chain — for example, confirming that an ad was delivered correctly, detecting invalid traffic or fraudulent activity, and maintaining the integrity of RTB auctions.
For a site owner, this cookie provides no direct functionality to visitors; it is part of the infrastructure that enables ad-space monetization through programmatic networks connected to Rubicon Project/Magnite.
Does it require consent?
CookieFix classifies the audit cookie under the marketing category (advertising/tracking), as it is used for ad targeting and verification purposes rather than being strictly necessary for the site to function.
- Under the GDPR (Regulation 2016/679) and the ePrivacy Directive 2002/58/EC (transposed in Romania via Law 506/2004), this cookie requires the visitor's prior, explicit consent before being set.
- Site owners must disclose the cookie in their cookie policy, assign it to the marketing category in the consent banner, and ensure the related script does not load before consent is given.
How to block or delete audit
Visitors can delete or block this cookie via browser settings (Chrome, Firefox, Edge, Safari — per-site cookie management) or by using ad-tracker blocking extensions. Blocking it does not affect core site functionality but may reduce ad relevance.
For site owners, the cookie should be blocked automatically until consent is obtained. A CMP such as CookieFix can classify the Rubicon Project/Magnite script under the marketing category and blocks it by default until the visitor gives consent, in line with GDPR/ePrivacy requirements.
Frequently asked questions
It is not technically harmful, but it is used for advertising tracking, which is why it requires consent under GDPR and may be seen as invasive by some users.
It is set by Rubicon Project, now owned by Magnite, a sell-side platform (SSP) provider for programmatic advertising, on the .rubiconproject.com domain.
Its typical duration is 1 year from the time it is set, though this may vary depending on the platform's specific configuration.
Yes, since it is a marketing/tracking cookie, prior visitor consent is required before it is set, in accordance with applicable Romanian law.