GDPR notes

[giuliopons]

Obviously I'm not a lawyer, but all the talks about the GDPR leads me to create a discussion here to evaluate how to improve AdAdmin on this side.

AdAdmin is honest and light, it does not save user data, therefore it does not collect data, but it uses some personal data and for transaparency it's correct to discuss about those data, probably the information in the next points must be at least mentioned in the privacy policy of your site.

Personal information used:

• when geo location is activated on a banner the IP of the visitor is used to determine the country, state or city of the user. The IP address is not sent to external server but is analysed locally do determine the location.
• when frequency cap is used just a cookie is used by the software to keep track of the number of times that the user has seen that specific banner. Cookie is stored on the user computer and no data are saved on the software to track the specific user.
• when the targeting by mobile or desktop device is applied to a banner, the user agent string is used to determine the device type.

If you have any suggestions feel free to write here.

[giuliopons]

News with version 4.3.0 about CMPs that provide IAB TCF API interface

With the version 4.3.0 AdAdmin started implementing a more robust support for GDPR.

We started to handle the tracking of pageviews by third party scripts for publishers who have clients that run an external third party tool to track views.

Normally these clients have also pageviews tracking scripts (a <script> tag that contains {GDPR} placeholders) and ask the publisher to add these scripts to the banner to compare and review the publisher data. If the publisher already has installed a CMP (Consent Management Platform, also known as the cookie banner) now AdAdmin can talk with it and handle the user consent to allow the tracking.

If the publisher doesn't use a CMP, this improvement cannot be used.

How it works

To enable this feature, the publisher must use a CMP and include an additional script in the <head> section of its site, after the CMP script. This script connects AdAdmin with the IAB TCF API provided by your CMP.
Add the following tag:
<script src="YOURADADMINURL/amb.js"></script>
Replace YOURADADMINURL with the URL that points to the amb folder in your AdAdmin installation (you should see the amb.js file there).

Once this script is loaded, AdAdmin will process any third-party tracking code entered in the "Third party tracking script" field of a banner.

AdAdmin will not immediately inject that code in your pages. Instead, it waits for the user's consent via the IAB TCF API. Only if the user provides consent for the relevant vendor and purposes, the tracking script will be activated and loaded into the page.

Important Notes

• Note 1: If you are using static image banners or video uploaded to AdAdmin they will always be displayed to the user, even without consent, because GDPR rules apply to tracking, not to the visual display of the advertisement itself.
• Note 2: GDPR-based control currently applies only to pageview tracking scripts. If the “Link” field, used to redirect the banner to the client site, contains placeholders like {GDPR} or {GDPR_CONSENT_XXX}, AdAdmin will not replace them. Therefore, the click action still transfers the user to the client site but click tracking on the advertiser's side may show slightly different counts.