JS file parameters

Choose your implementation in this step.

...

Script generation

The script is generated at the next step, based on the information given in the previous steps.

Cookie consent set-up

Before installing the Adloop tag on your website, please not that the Adloop tag is not exempt from users' consent. Our tag is first party and falls under the “Statistical” category, just like your Analytics tag.

Please take that into account when you set-up our tag!

Installation instructions

...

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

...

• 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

  • Image Removed

  • 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

...

...

...

...