Personalized and Non-Personalized Ads

If I understand correctly no change is needed if you use standard ad units.

Which ad units are considered as standard? Does the directives of the Google’s link I sent you concern another type of ads?

• This reply was modified 6 years, 6 months ago by PapGeo.

Yes, for standard ad units I’m considering ad units you generate in your AdSense account.

I think there is a misunderstanding or I don’t understand well ?? That’s from Google:

Link: https://support.google.com/adsense/answer/7670013

“You can choose to serve non-personalized ads to all of your users in the EEA using the “Non-personalized ads” setting below. However, if you want to give each of your users a choice between personalized and non-personalized ads, select “Personalized ads” and follow the instructions for serving non-personalized ads on a per-request basis.”

The later sentence redirects you here: https://support.google.com/adsense/answer/7670312 and shows how to change your code if you’re using Personalized ads. But it’s very confusing.

• This reply was modified 6 years, 6 months ago by PapGeo.
• This reply was modified 6 years, 6 months ago by PapGeo.

It’s confusing also to me.

I understand this as a general setting for all ads but if you need to make a choice for individual ads there is no clear explanation for standard AdSense ad units.

I understand it this way:

The original AdSense code:

<script async src=”//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js”></script>
<ins class=”adsbygoogle”
style=”display:inline-block;width:300px;height:250px”
data-ad-client=”ca-pub-xxxxxxxxxxxxxxxx”
data-ad-slot=”xxxxxxxx”>
<script>
(adsbygoogle = window.adsbygoogle || []).push({});
</script>

Non-personalized ads:

<script async src=”//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js”></script>

<ins class=”adsbygoogle”
style=”display:inline-block;width:300px;height:250px”
data-ad-client=”ca-pub-xxxxxxxxxxxxxxxx”
data-ad-slot=”xxxxxxxx”>
<script>
(adsbygoogle=window.adsbygoogle||[]).requestNonPersonalizedAds=1;
(adsbygoogle = window.adsbygoogle || []).push({});
</script>

I just came across https://www.huffingtonpost.com/
Perhaps if you are located in Europe, you’ll be able to see the popup they have about personalized ads. However, I don’t know if they use Adsense.

Need to check with Google.
Will post any findings here.

Ok, thanks.

I came across https://huffingtonpost.com (the popup loads after 1-2 seconds – if you’re located in eu I suppose) and I think this could be a perfect example and hopefully help you more.

• This reply was modified 6 years, 6 months ago by PapGeo.
• This reply was modified 6 years, 6 months ago by PapGeo.

I don’t know about the codes yet but what I know is this:

By default they are Personalized Ads (which means that Google can display both, personalized or not, depending on the data they have from the customer).

The consent for this type of Ads unfortunately are more restricted. Which means that in you cookie plugin, you need to have explicit consent before the Ad is served. Scrolling is not allowed. The user needs to click OK and only afterwards the personalized Ad can be served.

You can use, somewhere, I still don’t get this, to serve only Non-personalized Ads. In this case, they still use cookies but they are another type of cookies, so the only scrolling for consent is allowed.

You can serve both, like the huffingtonpost you saw, with a cookie plugin that can manage that, and it gives Personalized Ads if the user says yes, or Non-Personalized Ads if they user says no.

This should be the general concept but I still don’t need all the technical details about it.

I’m in Europe and did not get any popup on the Huffington Post site. They are not using Google ads but Oath (found when clicking on ‘AdChoices’ below an ad).

Until May 25th, Google did serve personalized ads. As from this date, the easiest way to comply with the GDPR in Europe regarding ads is to change the settings in your AdSense account so that only non-personalized ads are served to all visitors.

As this may bring a serious drop in the AdSense revenue (particularly if your visitors are mainly non-European), it may be useful to:
– filter based on the geographic origin of the visitor (no solution found until now)
– if the visitor is European, ask for its contents to receive personalized ads. I found the “GDPR Cookie Compliance” plugin useful as you can gain separate consent for statistics, social networks and personalized ads cookies. If the consent for personalized ad is gained, you can add lines in the HEAD, BODY and/or FOOTER section of your page.

From there, you can then adapt the AdSense code in Ad Inserter (based on the user’s consent) and serve either personalized or non-personalized ads (see code shown above).
I’m now in this latest part. Hopefully, I’ll have it working soon.

Any additional tip is welcome.