Advertising · Magnite Inc.

Magnite (Rubicon Project): cookies and consent

Auctions and delivery of targeted ads.

Cookies and how long they last

What Magnite, Inc. declares it stores in visitors’ browsers, from its disclosure to the IAB TCF registry.

NameTypeLifetime
khaosCookie12 months
khaos_pCookie12 months
auditCookie12 months
audit_pCookie12 months
trp_optoutCookie12 months
trp_optout_pCookie12 months
uidsCookie3 months
uids-auditCookie3 months
cdCookieSession
FPTrustCookieSession
fcapLocal storageNo expiry
emilyRanLocal storageNo expiry
khaosLocal storageNo expiry
sample_numberLocal storageNo expiry
puxLocal storageNo expiry

Source: Magnite, Inc.’s disclosure, published for IAB Europe’s Transparency & Consent Framework.

Spot it on your site

  1. Open your site in a private window, without clicking the banner.
  2. Developer tools › Application › Cookies.
  3. khaos is already there? Magnite (Rubicon Project) fires before consent.

Block Magnite (Rubicon Project) until consent

When the scan finds Magnite (Rubicon Project), Nodbar files it under “Advertising” and holds its scripts back until the visitor chooses. After the install, a new scan checks that nothing fires before consent any more.

Your banner in your colours, with Magnite (Rubicon Project) blocked until the visitor chooses.

Create my banner

FAQ

Is the khaos cookie required?

No. It is used for advertising: the site works without it, so it may only be set with the visitor’s consent.

Can I use Magnite (Rubicon Project) without a cookie banner?

No. An advertising tracker needs the visitor’s prior consent: without a banner to collect it, it must not load.

What happens if the visitor rejects it?

Magnite (Rubicon Project) must not load, on this page or the next ones. The visitor must be able to change their mind at any time, as easily as they chose.

Sources: Nodbar’s tracker database and Open Cookie Database, EDPB guidelines on the ePrivacy Directive. Updated on . This is not legal advice.