Versions Compared

Version Old Version 3 New Version 5
Changes made by

Audrey Marissal

Audrey Marissal

Saved on

Key

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

...

Expand
titleWith CAX

Contener connection and selection

  • Go onto the Commanders Act platform

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

Tags template selection

Capture d'écran 2023-03-13 115313-20240111-152136.png

  • 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(s) dimension(s) configured in your Analytics tool

    • If several, they should be separated by a comma ( , )

  • 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

Capture d'écran 2024-01-11 141320-20240111-152202.pngImage Removedimage-20250218-150922.pngImage Added

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 container 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) :

image-20240219-153828.pngImage Removed

  • Install the new “Adloop Tracking & Attribution” tag and place it in first position. There is no need to add some triggers (except Container loaded)

Image Added

There are two ways to set up the custom dimensions:

  1. Using a function just before the page_view event

There is function that you can call anywhere you want. This function automatically fills the custom dimensions when using GTAG, GA or PA analytics objects.
It is mandatory to call this function just before the page view event and any other event (add_to_cart, purchase etc.)

Code Block
if(typeof window._ADLOOP_SET_CUSTOM_DIMENSIONS != "undefined"){
          window._ADLOOP_SET_CUSTOM_DIMENSIONS(true);
}

  1. Using the stored value

In case of a specific setup, it is also possible to set the custom dimensions manually.
It is mandatory to write this code just before the page view event and any other event.

The Adloop dimensions values are stored in a variable called (you write this in the console debugger of your browser if you want to see what’s inside) :

Code Block
window.__ADLOOP_VALUES__

For example (in this case, the example implements the queue system of Piano, ‘paq’) : 

Code Block
if(typeof(__ADLOOP_VALUES__) != "undefined" {
  var adloopValues = window.__ADLOOP_VALUES__
  window._paq.push(['setProperty', adloopValues.clickDimension, adloopValues.clickCode])
  window._paq.push(['setProperty', adloopValues.clickDimensionMeta, adloopValues.clickCodeMeta])
}

Notes for debugging:

There are some debugging logs for this new feature, that you can access in the console debugger of your browser.

For you to be able to see it, you need to create a new cookie for the website that you are setting up (using a browser extension, like Cookie Master)

Image Added

The cookie must be named “tCdebugLib” and can have any value (1, for example).

With this cookie, you will see that kind of logs : 

Image Added
Expand
titleWith GTM

  • 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 and for the value select the first user defined variable you created previously using the brick button

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

Note: the name of the value between {{ }} depends on how you named your user defined variable ; it might be different from the screenshot above.

  • 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

...

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

On the GTM If you have a preview mode, access your website.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?”

...

:

  • 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 line with “pageview” in it and click on it to open it.

...

the first hit (pageview) after accepting the cookies.

...

 

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.

...

 

:

  • 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:

1ed2bf2f4a7be6b2-2e48-17064879-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 script8756-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

...

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

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.