Once the plugin has been correctly set up and installed on your site, we can test that it works as expected.
In this article, we will cover the following two approaches, which correspond to the two types of integrations we detailed:
1. Custom
Once cookie syncing has been set up, we can check that everything is working correctly.
To do this:
-
Go to your site.
-
Open your browser's developer console and then click the "Elements" tab (in Google Chrome) or the "Inspector" tab (in Firefox).
💡 By default, you should see that the scripts associated with your configuration's vendors do not appear in the tab.
-
If you have not already done so, open the Axeptio widget, then click the "Accept all" button.
-
Look again at the "Elements" or "Inspector" tab. You should see the scripts for your vendors.
✅ The integration is now complete!
2. Google Tag Manager (GTM)
You now want to verify that your Google Tag Manager integration is valid.
To do this, you need to check your settings using GTM's preview mode.
Here, we will see:
GTM preview mode
Google Tag Manager's preview mode lets you verify which tags have been triggered and when.
It's a good idea to use it after updating your GTM tags to make sure that everything is working correctly before publishing your GTM online. Note that the preview is available only in English.
To launch a preview:
- Click the Preview button in the top-right corner.
- In the window that appears, enter your site's URL.
⚠️ GTM must be integrated into your site for this to work.
Next, two windows open:
- The first is the Tag Assistant: This is where we will see how all the events, tags, and other variables change in response to the actions in the second window.
- The second window shows your site: The actions you perform on it will be observable in the Tag Assistant.
💡 Example of the Tag Assistant window :
- Summary: This shows you all the tags that were triggered or not.
- An event: Selecting an event in the list shows you if a tag is triggered on the right event or, if applicable, why it was not triggered.
Some examples
- Case #1: Facebook Pixel tag triggered on the Axeptio event
- Case #2: Purchase tag triggered by a custom event
Case #1: Facebook Pixel tag triggered on the Axeptio event
In this scenario, we want to verify that our Analytics tag is triggered on the corresponding Axeptio event: axeptio_activate_facebook_pixel.
Selecting the event in the event list shows that the tag was triggered:
When we click our "Facebook Pixel" tag, we can see the details of its triggering, and we can check why it did or did not trigger:
✅ The observed event is the same event that was requested for the trigger, which means that the tag was triggered.
If the user has rejected cookies, the Axeptio events will not take place, and the associated tags are not triggered:
Case #2: Purchase tag triggered by a custom event
Here, we have added a condition to our "purchase" trigger, which verifies that the Axeptio variable contains "facebook_pixel":
✅ Our tag was triggered on the "Purchase" event.
Now, let's take a closer look:
✅ It is not the variable's name that appears, but its value, providing a list of all the accepted cookies.
✅ Our condition on the Axeptio variable was met, meaning that it contains "facebook_pixel.
✅ The observed event is the same event that was expected for the trigger. Because both conditions were met, the tag was successfully triggered.
Now, if the user rejects cookies:
✅ Because one of the conditions was not met, our tag was not triggered.
✅ The observed event is still good. However, because the variable is empty, it does not contain "facebook_pixel".