25 Jan 2019
In 2018 some Admitad publishers experienced significant changes in statistics: the approval rate could considerably diminish, the number of orders on hold could rise up, as well as the conversion rate and the number of approved orders changed. Admitad Academy is revealing what happened and how it affects the work of publishers and advertisers.
At the end of May 2018, Admitad released an updated tracking code named TagTag. Gradually, the advertisers began to switch from older tracking codes to TagTag, and it affected the reports of publishers joined to the affiliate programs. Admitad started tracking significantly more orders (including cross-device) what caused the decrease in the percentage of approved orders, at the same tim the absolute number of approved orders increased.
Let’s examine how the updated tracking of Admitad works, what has been changed, which opportunities the publishers now have, and what advertisers should pay attention to in order to make TagTag properly track the orders.
What is TagTag?
TagTag is a tracking code placed on the advertiser’s website. The main purpose of this code is to track if an order has been made and how customers proceeded to the website, in other words, which publisher has attracted them and deserves the reward now. The tracking code is activated at the moment of confirming the order (when a customer presses the button “Checkout” and pays for the order, or in any other way confirms the fact of making the purchase, proceeding to the “Thank you for the order” page). Right after this, the order, containing the full information about the purchase (such as total sum and the order number) is transmitted to Admitad system.
What is the main objective of the tracking code?
The most important is that the tracking code registers the performance of the required action on the advertiser’s website and transmits it to the Admitad statistics. When the tracking code is triggered, a request with the information about the target action (order number, sum of order and other information) is sent to Admitad server.
The tracking code is responsible for properly attributing the order (assigning the order) to the source. Admitad works upon the model Last Cookie Wins, in other words, the reward is given to the publisher (or to any other paid channel) whose link the user clicked the last before making the purchase — whose cookie-files were the last attached. By paid channels we mean not only publishers’ ad spaces but also the paid promotion performed by the advertiser (e.g. contextual ads, banners, work with bloggers and many others). In other words, if the analytics is set properly on the advertiser’ website, it will be easier to identify each channel and see which channel was the last, and thus attribute the order to this channel. And the tracking code helps to do so.
What issues does TagTag solve?
The more complicated the system is the easier an error can occur. Here are several examples of issues that advertisers face and how TagTag solves them:
Duplicated payment. It happens if advertiser’s analytics receives data that a customer has proceeded to the website from different sources, but it doesn’t identify them. Let’s examine an example:
An advertiser attracts customers through different channels: affiliate programs in two different affiliate networks, as well as paid promotion on social networks using their own resources. The user firstly proceeds through the contextual ad and starts thinking of buying a product, then he opens YouTube and watches the reviews of this product filmed by two bloggers. The first blogger works with one affiliate network, the second — with another, and they both place affiliate links in the video descriptions (the user clicks the affiliate links of both bloggers). Having watched the second review, the user decides to buy the product and proceeds to the advertiser’s website via the link in the video description. Each time the user proceeds to the website, he gets the cookie-files of those channels where he clicked on the links. The first cookie-files he got from the contextual ad, the second ones — from the first YouTube channel of the publisher, the third — from the second YouTube channel. Therefore the system sees three different traffic channels — contextual ads of the advertiser and two from affiliate networks. So who should receive the reward for the purchase? Whose cookie-files were the last ones?
The deduplication is needed to exempt the advertiser from paying twice for one order. It provides an opportunity to single out the traffic according to the channels and to identify who attracted the client (whose link was clicked the last). In c ase the advertisers work with several affiliate networks, they can set up deduplication on their side using TagTag.
Ad blockers. While working with the old integration code (so-called “pixel”) the following issue could occur: the page with the code could not fully load (it means that the code was not activated), or the ad blockers blocked the code as mistakenly took it for an advertisement. At the same time, the pixel of conversions was the easiest solution in terms of technical integration. TagTag is same easily integrated on the website but it prevents the erroneous block of the load of the script by the ad blockers and antivirus software. At the moment this feature has been released only by a couple of affiliate market players (apart from Admitad).
Loss of orders when switching browsers and devices. The majority of users use several devices for selecting goods and purchasing them. They can click an advertisement on the pc, then examine the good in more details using the smartphone on their way home, and in the end, buy it using the lap at home. Moreover, they can use not only different devices but also different browsers what makes tracking even more complicated (how is it possible to understand if it was one user or three different?). TagTag collects the depersonalized technical information of the user: as the code is activated on each device, it records that all the devices belong to one person. Even if the user clears the cookie-files and uses the private browser mode or uses another browser, the system will still track his way from the first click on the affiliate link till the purchase. The technology of cross-device and cross-browser tracking decreases the number of lost orders and makes reconciliation easier.
Why is TagTag useful to publishers?
It is good news for publishers working with mobile traffic. Now they can be sure that an order or a lead won’t be lost when a user switches from smartphone to desktop. Cross-device tracking will provide the correct attribution of actions to the publishers and their ad spaces. It is especially relevant to the trend of 2018 — Telegram-channels.
If you work as a publisher with the advertiser which has just set up TagTag, you can expect that the number of approved orders from mobile traffic will increase. Even if the percentage of approval decreases, more orders will be passed to the system, therefore, it means that while the relative value of this parameter may decrease, the absolute rate of income will grow. According to the data of Admitad, over the past three months, the commission sum to the publishers has increased by approximately 10% (from 50 largest advertises that switched to TagTag in 2018).
How can you find out if the advertiser has integrated with TagTag? — You can simply ask the manager of the affiliate network. Such a filter will be also added to the section “Programs” — it will help publishers working with mobile traffic to find the advertisers integrated with TagTag.
Why is TagTag useful to advertisers?
Simplified integration. Placement of tracking code is believed to be the simplest way to integrate with an affiliate network as it doesn’t require any additional developments from the side of the advertiser and doesn’t imply any significant changes in the website structure. The script should work on all pages and should be placed in the tag <head> before any other tags (so that it is activated before a user leaves the website). The code TagTag is integrated equally simple with both websites built by publishers and websites on CMS.
&n bsp; To avoid incorrect payments and optimize the reports. Thanks to deduplication there will be no more disputable situations regarding who should get the reward. The setup of this parameter isn’t obligatory for those who work only with Admitad. If advertisers use other paid channels apart from Admitad (for instance, their own paid advertisement or services of other affiliate networks), they should use this guide or contact Admitad technical support where they will get help.
Attraction of new publishers. Publishers who work with mobile traffic used to try to choose only mobile offers as it was hard to track the orders made via several devices, and some orders were lost (what caused the need to search manually and took time). But the mobile traffic keeps increasing: new mobile channels with quality traffic appear (for example, users of Telegram messenger shows higher conversion and average check comparing to other traffic sources). TagTag solves the issue of searching the orders in cross-device, what makes desktop offers (travel, online shops, etc.) more attractive to publishers who have mobile traffic of high quality.
There are some aspects which should be taken into account by advertisers when they decide to integrate. They will allow switching to TagTag easier and faster.
Placement of code. The code should be inserted between the tags <head> before all other scripts placed in this directory. If you place it in the container Google Tag Manager (GTM), it will be blocked by popular ad blockers and will lose its main advantage. It can cause the loss of orders, discrepancies in statistics and make reconciliation problematic.
Full Integration. If advertisers have mobile version of the website, quick order form or 1-click ordering, they should be also integrated. In case an advertiser has a mobile application, it should be also integrated using Admitad SDK (we will talk about it very soon).
Monitor the updates. If you make significant changes in the website structure, make sure that these changes do not affect the integration code. If the changes affect TagTag script, it can cause its incorrect work, thus it is better to test it after making changes.
Deduplication. Do not forget to include all paid traffic types in the deduplication parameter. This is especially important if the terms of working with the affiliate network change, and you start allowing new or prohibit the old traffic channels.
Test. Checking if the script works correctly is the last step of successful integration. Use this guide to check it properl. If you have any doubts or want to ask a question, you can always contact our technical support to get the help with integration.