Adback – Help centre

About Adback

AdBack is an analytics and monetization solution specialized in adblock audience that allows media, e-commerce and advertiser sites to increase their revenues and benefit from a complete vision of their data in respect of users.

Today, 25 to 30% of Internet users have an adblocker. The consequences are not only the blocking of advertisements but also the blocking of many third-party elements on your site and in analytical tools like the Analytics Suite 2 of AT Internet.

On average, 10 to 15% of your analyzes are blocked. With the AT Connect Adback:

Recover these 10 to 15% of data blocked by adblockers.
Reassemble your favorite AdBack data directly into AT Internet segments.
Avoid Marketing mistakes because of incomplete Data Sheet linked with adblockers activities.

To learn more, visit https://landing.adback.co/en/

Point differentiating

AdBack analyzes adblockers user trends and supports more than 300 sites in France, Europe, LATAM and Asia in their strategy of reconquesting advertising through two main levers:

AdBack Data: Identify adblocker user profiles, from the most refractory to the less ad-resistant. In a logic of respect for the user, we then target only the most open users with our monetization solutions.
AdBack Monetization: Monetize the part of your audience that is most receptive to advertising with non-intrusive formats. Post your own campaigns or leave us your blocked inventory and we take care of the monetization with our various advertising partners and programmatic connectors.

Advantages of the connector

The AT Connect Adback allows you to recover the blocked audience detected by Adback. The Analytics Suite 2 interfaces are thus fed by all the data of your site, including the elements impacted by adblockers.

Automatic recognition and identification of adblockers via Adback technology. This solution acts in the purest respect of the privacy of users and RGPD rules.
Recovering blocked data in the Analytics Suite 2 interfaces. Your analyzes gain precision thanks to comprehensive data.
Enrichment of the segments via relevant and complete data. Create segments involving all the elements that composed your site.
Safer decision-making. Improve your decisions based on just and accurate insights thanks to this integration.

AT Connect Adback introduction

Thanks to the AT Connect Adback the blocked data are recovered, via Adback, in the interface of the Analytics Suite 2. This integration allows you to benefit from the best of both solutions by combining the detection power of Aback adblockers with rich analytics of AT Internet.

This integration is completely transparent to the user and does not change his habits, the AT Connect Adback respects perfectly the functionalities of the two solutions.

Here is the main process of the connector:

The AT Internet Hit is blocked by an adblocker.
The blocked Hit and its associated parameters are catched by Adback.
The Hit is sent back to AT Internet via an Adback proxy.
The recovered data are then displayed in the Analytics Suite 2.

Below is a summary of this process.

AT Connect Adback implementation

You can deploy the AT Connect AdBack integration in a few clicks by adding a simple JavaScript code to your site. Here is a list of the prerequisites for the proper operation of this integration:

Have an AdBack account. You need to be customer of AdBack solution, and see with AdBack how to activate the proxy part.
Tag Composer : Use the user id first-party in your smarttag.js (activated by default since version 5.10.0.).
Tag Composer : Enable callbacks in your smarttag.js (enabled by default).

You will find below the JS code to integrate on your site:

window.ATInternet = window.ATInternet || {};
window.ATInternet.Callbacks = window.ATInternet.Callbacks || {};
window.ATInternet.Callbacks.Adback = window.ATInternet.Callbacks.Adback || function(tag) {
  tag.onTrigger("Tracker:Hit:Sent:Error", (trigger, data) => {
    var hitAt = data.details.hit;
    var configSecure = tag.getConfig("secure");
    var protocolSecure = document.location.protocol === "https:";
    var isSecure = configSecure || protocolSecure;
    var protocol = "";
    if (hitAt.indexOf("http") != 0) { protocol = isSecure ? "https:" : "http:"; }
    hitAt = protocol + hitAt;   window.parent[window.parent.document.getElementById("adback_data").getAttribute("data-adback")].API().sendATInternetPixel(hitAt);
  });
};
window.ATInternet.Utils = window.ATInternet.Utils || {dispatchCallbackEvent: function() {}};
window.ATInternet.Utils.dispatchCallbackEvent("Adback")

You can also find these elements in the AT Internet GitHub. Here is a direct link to the AT Connect AdBack page: https://github.com/at-internet/atinternet-js-smarttag-adback

Display in the Analytics Suite 2

AT Connect Adback is based on a "classic" Hit recovered via Adback. Thus, the data goes back to the Analytics Suite 2 interfaces in a completely transparent way. No distinction appears regarding the blocked audience part. The audience in add is directly displayed into your existing configuration.

The data display and the interfaces of the Analytics Suite 2 are therefore in accordance with usual usage. The example below illustrates this "classic" display of data (the blocked part recovered via Adback is integrated).

Consult the blocked audience

As you can see, the integration is totally transparent. However, there are several ways to display the distinction between blocked and unblocked audience in Analytics Suite 2.

Here are some possibilities:

Make two hits: a mark with the Adback code / a mark without the Adback code. This method makes it possible to identify the gap and the blocked audience recovered.
Use the Adback parameter already present in the Hit, currently not stored, and process it via a Data Manager rule to retrieve the information.
Use the MVT tag: Set up a test with a "classic" variation without blocking and a "blocked" variation indicating that passage through Adback.

Privacy

Activating this partnership activates the exchange of data between Adback and AT Internet. Only the data necessary for the proper functioning of the bridge are exchanged.