Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Expand
titleWithout GTM: gtag.js

The verification of the script is very easy and will take only a couple of minutes.

On the GTM preview mode, access your website.

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?”

...

 

Then reload your page using CTRL+R, still with the Console being open.

Find the line with “pageview” in it and click on it to open it.

...

 

In the Payload tab, scroll down until you find the list of custom dimensions. They are indicated as cd1, cd2, cd3 etc. Find the custom dimension(s) that you created for Adloop.

...

 

Now, the custom dimension that you created should be filled with an Adloop code, that looks like this:

1ed2bf2f-1706-47ff-c3c8-1865373dcd9a:Ep0hc|DR|/

If you see the Adloop code, you can publish our script !

If your custom dimension is not filled with a value, then there is something wrong with the script. 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!

 

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
titleChecking with GA4

Go to the Explore section to create a custom report

image-20240119-105717.pngImage Added

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 :

image-20240119-110511.pngImage Added

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
titleChecking with Piano

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

image-20240219-163721.pngImage Added

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%.