...
| Expand | ||
|---|---|---|
| ||
 |
The verification of the script is very easy and will take only a couple of minutes.
If you have a preview mode, use it before publishing !
Click on the F12 button of your computer or right-click > Inspect to open the Console and go to the Network tab. In the filter box, type :
collect? if you use GA4
xiti if you use Piano Analytics
...
Then reload your page using CTRL+R, still with the Console being open.
Find the first hit (pageview) after accepting the cookies.
...
In the Payload tab, scroll down until you find the custom dimension you created :
ep.adloop_click_1 for GA4
adl1 for Piano Analytics
Now, the custom dimension that you created should be filled with an Adloop code, that looks like this:
4a7be6b2-2e48-4879-8756-d5ecdb16c195:JGMaP|SOu|GG:/fr-fr/
Check the value between the first two | | :
If you came through a natural search engine result : |SOu|
If you came through direct : |DR|
If you came through a link with tracking parameters : |UN|
Check several pages of the website, the custom dimension should be triggered and populated for each page view. Try also to trigger a couple of events, our custom dimension should be triggered and populated for each as well.
If that is not the case, check the set-up of the tag. Check carefully once again that you followed every step of our Adloop script installation guide. You can also contact our Customer Success team that will be able to assist you with the script installation!
If all seems good, you can publish our script.
There is another alternative way to check if your script Is being triggered
| Info |
|---|
This method only works when Google Analytics is used asynchronously |
On your website:
Open web console > F12 or right-click and click on the inspect element.
A window like this will open up at the bottom of the page.
...
Click on console and type ga.q
...
In the ‘set’ section you can find our custom dimension, after clicking on the 1st line to open.
Checking the data collection
| Info |
|---|
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. |
| Note |
|---|
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. |
| Expand | ||
|---|---|---|
| ||
Go to the Explore section to create a custom report  Create a new table report using the blank canvas. In the dimension, select:
In the events, select:
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. |
| Expand | ||
|---|---|---|
| ||
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. |