Jump to content

The OAID cookie, GDPR and cookie policy

Recommended Posts

We are currently working on becoming compliant with GDPR and the Cookie Law.

I understand that enabling "compliance mode" in v4.0.4+ updates OAID to use a static (rather than dynamic) value, preventing any way of uniquely identifying the visitor and resolving GDPR tracking / privacy issues.

The Cookie Law however requires all non-essential cookies to be disabled until consent has been given, as well as a description of what each cookie does in the cookie policy.

This page explains that OAID was introduced for an old defunct feature and no longer has any use but then goes on to say that OAID is needed to detect if the browser supports cookies (without any reason why).


This means:

1) We cannot display ads on our site until after the user has consented because of OAID and the Cookie Law

2) We cannot find a clear reason to justify OAID in our cookies policy


So the questions here are:

Why does Revive Adserver need to know if the browser supports cookies,

and what's the potential for say a "cookie law compliance mode" in the future.


I can see someone else had this issue as well:



Link to comment
Share on other sites

  • 7 months later...
  • 1 year later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...