Configure GTM / Changes to Triggers

Byscuit is designed to send a custom event on all pages, which GTM can then read. This event is triggered when Byscuit confirms the user's consent status—either when the user confirms their choice or when they navigate the site after accepting or refusing cookies. This event can replace the classic Page Views triggers. Here are the options:

  • Continue using Page Views tags: Tracking will work, but there is a risk of losing some specific tracking elements. Since the Page View tag fires when the page is fully loaded, it can fire on the user's landing page before they have enabled cookies. If the Page View tag fires before cookies are accepted, this interaction with the website might be missed.
  • Use a Custom Event Trigger: The “consent_byscuit_updated” event fires on all pages, after Byscuit confirms the user’s consent status. It can therefore replace the Page View tag. Use a Custom Event trigger with “consent_byscuit_updated” in the Event Name field. Keep the same trigger conditions as your original Page View tag and the tag should work as before.

Page View (All Pages)

This tag will fire on all pages, effectively replacing the Page View tag.

Page View (Other)

This tag is an example of a trigger that should be activated when a user submits a form.

 

Let's assume we choose to use the custom event instead of keeping the Page View tags. We now need to apply the new triggers to the tags. Let's take this tag as an example:

This is the Google Tag from GA4. This tag should fire on all pages. We simply need to change the trigger to the trigger we created earlier. We need to do this same step for all Page Views triggers in the GTM container.

The tags changed in this way will have an event tag instead of the Page View tag.