The script was correctly triggered in the preview? Great! But that is not the only thing you need to check when installing the Adloop script. You need to check that we are getting all the data from your site.
This verification step can only be done after the Adloop script has been installed for a full day!
If the script is installed on a Monday, you can do the checking only on Wednesday for Tuesday’s data.
Also, if you have discrepancies, please keep in mind that Google Analytics data can change for the last 48 hours. If you have small discrepancies, especially on the revenue & transactions metrics, please check data that is more than 48 hours old, as it can explain most of the small discrepancies.
Go to the Explore section to create a custom report
Create a new table report using the blank canvas.
In the dimension, select:
the adloop_click_1 dimension
event name
In the events, select:
event count
event value
transactions
Filter on the event name to include only your purchase event :
The amount of events attached to a (not set) Adloop custom dimension must be very low. We allow a tolerance of 5%.
The same check must be performing for all the events that you track: pageviews, add to cart, product page view etc. That way we are sure that our script is triggered as it should on every page.
Open the Data Query section of Piano
Lines : the Adloop custom dimension you created, Events
Columns: Events
Date: From the first full day of data-collection
Be careful to display N/A lines
Compare the number of events attached to an Adloop value to the global number of events on your website for each event. The amount of N/A for each event has to be very low.
The amounts should be very close - we allow a tolerance of 5%.
Please note! If Piano works in consent mode, please filter the data to only compare when consent is given. Otherwise, since Adloop can only work with the consent of the user, you won’t have the same basis for data comparison.