-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable Google Limited Ads #208
Comments
I've got a PR ready If you give me the rights on the repo, I can I submit it whenever you want @jaanauati |
Hi @sl-pierrevautherin, that sounds good!, the development flow is pretty straitforward:
You should be able to submit a pull request (step #1), let me know if you are still facing any issues/errors. Thanks. |
Hi @jaanauati , Thanks for your kind reply!
Could you grant me access rights to the repo please ? |
OK done => #209 |
v 0.20.0 has been pushed to npm. @sl-pierrevautherin please give a try and let me know if u find any issues. Thank you for your work on this. |
Thanks @jaanauati ! The last version on NPM is 0.19.0. I'll check again in a few minutes Edit : it works fine! (12th March 2021) |
use case: lots of companies are moving to Limited Ads for data-privacy and compliance reasons
about: Google Limited Ads gives publishers the ability to serve ads in a limited way, in the absence of consent for the use of cookies or other local identifiers.
Limited Ads only require the GPT library to be fetched from the pagead2 source:
Standard => https://securepubads.g.doubleclick.net/tag/js/gpt.js
Limited ads => https://pagead2.googlesyndication.com/tag/js/gpt.js
docs: https://developers.google.com/publisher-tag/guides/general-best-practices#load_from_an_official_source
suggested change: add an optionnal src prop to handle Limited Ads
The custom src provided by the user would replace the current "securepubads" value here => https://github.com/jaanauati/react-dfp/blob/master/js/utils.js#L6
I would be happy to open a PR if that's OK for you @jaanauati ?
The text was updated successfully, but these errors were encountered: