-
Hi,
I was wondering if there was any possibility of transmit the GDPR Consent-String (located in the cookies) into the VAST ad Tag. It’s needed for our ad-provider
Kind regards
-
-
or can I somehow add variables to the shortcode, other than those already defined?
Hello Eva,
please let us know what is the cookie name, perhaps there is some standard which we can follow.
Other than that the only possible solution I can see if to support custom URL variables which would put in true or false based on the condition. So that:
gdpr=[have_cookie:consent]
would evaluate as either gdpr=1 or gdpr=0 based on the presence of the cookie with name “consent”.
Thanks,
Martin
Hi,
thanks for the reply. The javascript we use to extract the constent-string is as follows:
const vast_url_cookies = document.cookie.split(“; “).find(row => row.startsWith(“euconsent-v2”));
const vast_url_consent = vast_url_cookies.split(“=”)[1];The name of the cookie is “euconsent-v2” and it looks something like this:
euconsent-v2=CPFnbqlPFnbqlAVACADEBaCsAP_AAH_AAAYgHhNf_X9VbWNjuX59YttkYIEX1tRvo-QjCg[…]AAAAAAAA
We only need the string after the “=” so we split it.
Best regards
Hello Eva,
so technically we could support something like:
gdpr=[cookie:euconsent-v2]
…which would check for that cookie and append it. We will discuss the possibility of this addition as we didn’t get a similar request before.
Please let us know what ad network you are using.
Thanks,
Martin
Hi again
is it maybe possible to construct the FV Player yourself?
For example is it possible to do something like this:<script type=”text/javascript”>
vid1 =fvplayer(“vid1″)
vid1.ima({
adTagUrl: vast_url,
disableAdControls: true
});
</script><video id=”vid1″ class=”video-js vjs-default-skin vjs-big-play-centered vjs-fluid” poster=”” preload=”auto” controls=”” >
<source src=”https://player.vimeo.com/external/12345″ type=”video/mp4″>
</video>Best regards
Hello Eva,
we could support the vast_url argument in the JavaScript initialization of FV Player as seen here: https://foliovision.com/player/advanced/api-programming#js-usage -> 1. Player initialization via JavaScript
But it appears to me using the URL agument like this would be a better fit for your use-case:
gdpr=[cookie:euconsent-v2]
Thanks,
Martin
Hi Martin,
yes you’re right, the second solution would be very helpfull, but we need some solution sa soon as possible.
So I think I will try the first option in the meantime until you decide whether or not to implement the gdrp-Tag.Best regards
Hello Eva,
we are happy to prioritize your request and get it done this week if you purchase our Pro support: https://foliovision.com/pro-support That way it would allow you to use these GDPR cookies with VAST ads rightaway and it would save you from any coding.
Thanks,
Martin
Hi Martin,
we purchased the pro support. I hope you can resolve our issue quickly.
Best regards
Hello Eva,
to conclude this ticket – we improved FV Player VAST and now you can use a tag like this in the URL to get “argument={your cookie value}”:
&your-argument=[cookie:your-cookie-name]
Thanks,
Martin
