With Google Analytics UAWe need you to create a custom dimension in Google Analytics, in which we will put the information gathered by our script.

Specifications of the custom dimension:

• scope: session

• name: Adloop Click

• number of custom dimensions: if you have GA360, a custom dimension for every 75 000 daily sessions is needed ; if you don’t have GA360, a custom dimension for every 50 000 sessions is needed.

Also, you’ll need the list of excluded referrers (especially payment platforms) when doing the set-up in Adloop.

You’ll find this list in GA > Admin > Property > Tracking Info > Referral Exclusion List.

With Google Analytics 4

• Go to "Configure"

• Go to "Custom Definitions"

• Create 2 custom dimensions dedicated to Adloop:

  • The first one:

  • Click on "Create custom dimensions"

  • Name it Adloop Click 1

  • Select "Event" as scope

  • Event parameter: adloop_click_1

* The second one:


* Click on "Create custom dimensions"


* Name it Adloop Click 1 Meta


* Select "Event" as scope


* Event parameter: adloop_click_1_meta

Also, you’ll need the list of excluded referrers that you will find in GA4 under Data Streams > Configure Tag settings > All settings > List unwanted referrals

With PianoCreate two custom dimensions adl1 and adl1_meta

Type: String

The dimension does not contain personal data

The Adloop script is not exempt from users' consent.

Our tag falls under the Statistical category, just like your Analytics one.

Contener connection and selection

• Go onto the Commanders Act platform

• Choose the appropriate contener. It is essential that the tag is triggered on all landing pages.

Tags template selection


• Go to the step of choosing tag templates

• Search for “Adloop” in the search bar

• Choose the “Adloop Tracking and Attribution” template. You’ll be redirected to the editing step.

Template edition

Fill in the 3 following fields:

• The custom dimension configured in your Analytics tool

• Subdomains that should be considered as a separate referrer

• Referrers to be excluded (the list should be the same as the one in your Analytics tool), like payment platforms


Consent

• Set the consent for the Adloop tag (Analytics/Measurement category)

Publishing

• Place the Adloop tag between the initialization of your Analytics solution and the pageview event being sent

• Proceed with the contener generation and make sure there are no error during the auto-test step

• Publish the contener

In the case of the a single tag for initialization

If you use a single tag for initializing your analytics solution and for sending the page view event, then simply place the Adloop tag before your Analytics tag and modify your Analytics tag to include the code for populating the custom dimension. Below is an example of how you can implement it with Google Analytics 4 (add line 2 and 6 in your GA4 code) :

Get the script from the attribution source setup.

You have to place it after initializing the GA script but before sending the pageview:

Example:

analytics.jsgtag.js

With Google Analytics UA

• Go to the "Variables" section

• Make sure the Container ID is listed under the Build-In Variables

  • If not, click “Configure”, search for Container ID under “Utilities” and enable it

• Create "User defined variables" following this scheme:

  • Type of variable: Data layer variable

  • Name of the data layer variable: indicate the value you set up in your custom dimension on GA4 in the event parameter field (ex: adloop_click_1).

  • And give it an adloop related name

  • Repeat these operations for all custom dimensions created in GA

• Open the configuration of the "Google Analytics settings" variable,

• In "More Settings -> Custom Dimensions, click on "Add Custom Dimension"

• Fill in the following information:

  • Index: XX (where "XX" is the index of the dimension created on GA)

  • Dimension value: {{adloop_click_XX}} (Use the brick to choose the previously created variable)

  • Repeat these operations for all variables created in GTM

• Go to the "Tags" section and add a new tag of type "Custom HTML", with the name "Adloop tag".

• Copy and paste the content provided on the Adloop interface into the "HTML" field of the tag

• Save the tag without trigger

• Open the configuration of the Google Analytics tag with the largest trigger ("All pages" or “Pageviews” for example).

• In the advanced settings of this tag, in "Tag sequencing", check "Trigger a tag before Google Analytics is triggered" and choose the "Adloop tag" previously created

• Check if the script is working without error in the preview mode (find our documentation [[here|Checking-that-the-script-is-triggered]]), then deploy the new version.

Google Analytics 4

• Make sure the Container ID is listed under the Build-In Variables

  • If not, click “Configure”, search for Container ID under “Utilities” and enable it

• Go to the "Variables" section

• According to the custom dimensions created earlier, create "User defined variables" following this scheme:

  • First one:

  • Type of variable: Data layer variable

  • Name of the data layer variable name : adloop_click_1

  • Give the variable an Adloop related name

  • Second one:

  • Type of variable: Data layer variable

  • Name of the data layer variable: adloop_click_1_meta

  • Give the variable an Adloop related name

• Open the configuration of the GA4 Configuration tag (type: Google Tag)

• In "Fields to Set”, click on "Add Row"

• Fill in the following information:

  • Field Name: adloop_click_1

  • Value: Use the brick to choose the previously created variable (the 1st one)

  • Add another filed: adloop_click_1_meta

  • Value: Use the brick to choose the previously created variable (the 2nd one)

• Go to the "Tags" section and add a new tag of type "Custom HTML", with the name "Adloop tag"

• Copy and paste the content provided on the Adloop interface into the "HTML" field of the tag

• Save the tag without trigger

• Open the GA4 Configuration tag (type: Google Tag) that was opened in a previous step

• In the advanced settings of this tag, in "Tag sequencing", check "Trigger a tag before this tag is triggered" and choose the "Adloop tag" previously created

• For your GA4 events (purchase, add to cart, view item etc.) set-up on GTM, add the Adloop event parameters & values :

adloop_click_1_meta and for the value select the second user defined variable you created previously using the brick button

• Check that all your events (add to cart, purchase etc.) are triggered after the pageview is sent. Otherwise our script won’t be able to catch those events.

• Deploy the new version

Before publishing the Adloop script, you need to check it is correctly triggered!

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

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.

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.

Checking with Google Analytics UAFor this verification, you need to go to your Google Analytics account, into the Custom Reports section.

There click on the New Custom Report button.

Give an Adloop related title to your report so you can identify it quickly, for example Adloop check.

Name the first report content tab “Adloop CD1”. You will need to create a tab for every custom dimension that you set up for Adloop.

Choose the Explorer type.

As metrics, choose: sessions, revenue (if applicable), page views, transactions (or your main conversion event) and new users.

As dimension drilldown, choose the Adloop custom dimension.

You need to repeat this step for every Adloop custom dimension, using the Duplicate this tab button. Just don’t forget to update the Adloop custom dimension for every report.

If you have two custom dimensions, you can name the second tab Adloop CD 2, if three the third can be named Adloop CD 3 and so on.

When you are finished, click on duplicate this tab once again.

Name this tab “source/medium” and as dimension drilldown choose source / medium.

You can now save the report.

Now we need to check that the Adloop script is gathering the same information as the Google Analytics one.

For that, you can open a table (Excel for example) and create the create a file like this one :

That you will fill out with the informations from the Google Analytics Custom Report we just created in the previous step for each line.

If you have several custom dimensions, create a Total Adloop CD line in which you will sum all the numbers from the different Adloop custom dimensions.

You can now create a line to calculate the percentage of difference between the data gathered in the Adloop custom dimension(s) and the data gathered in Google Analytics.

Use the following formula: (Adloop cell) / (GA cell) for every metrics.

Ideally, you have 100% everywhere, but that is that always the case!

For revenue and transactions, it is very important that we aim at a 100% score, meaning that we get all conversions.

But for sessions, pageviews and new users, our script, for some reason (including cookie consent), doesn’t get triggered. The discrepancy should be under 2-3% for those metrics.

Bigger discrepancies mean that the Adloop tag is not triggered as often as it should. Please check the trigger rule for the Adloop tag: it should be fired before the GA pageviews tag.

Checking with GA4Go to the Explore section to create a custom report

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

Checking with PianoOpen 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%.

If you have discrepancies and need help, please contact our Customer Success team that will help you!