Ideal Trigger Order in Google Tag Manager

If you work with Google Tag Manager (GTM), sooner or later you'll run into the question: in what order should your tags load? Do you simply put everything on the 'All Pages' trigger? If so, you risk your tags conflicting, or your marketing data firing before the visitor has given consent. This leads to GDPR fines, or conversely to huge data gaps in GA4.

To stay GDPR-compliant while retaining 100% of your measurable data, a tight trigger order is crucial.

The ideal GTM trigger order in 3 steps

A properly configured container follows a logical hierarchy. The browser must know the consent status first, before any marketing pixels fire.

1. Consent Initialization – All Pages (Step 1: Consent)
   • Tag: Consent Studio (Google Certified CMP)
   • Function: The legal and technical starting point. The browser immediately reads which cookies are allowed to be placed. All subsequent tags automatically inherit this status via Google Consent Mode v2.
2. Initialization – All Pages (Step 2: The Foundation)
   • Tag: Google Tag (GA4 / Google Ads Config)
   • Function: The measurement engine. Privacy settings and data routing are built up here. This must run before you can measure specific events or conversions.
3. All Pages / Page View (Step 3: Marketing Tags)
   • Tags: Conversion Linker, Meta Pixel, LinkedIn Insight Tag, Hotjar, HubSpot
   • Function: Now that the foundation is in place, the marketing pixels fire only with the correct consent status.

The big pitfall: missed page views from new visitors

Many marketing tags (such as the Meta Pixel or Hotjar) have no built-in consent check. When a new visitor lands on your site, it often takes a few seconds before they click 'Accept'. By that time, the standard 'All Pages' trigger has long since fired.

The result? The very first page view — and its associated attribution — is lost entirely from your reports. Even if the visitor gives consent, you no longer measure the landing page.

The solution: DataLayer events & Consent Mode v2

You close this data gap by using smart triggering:

• Use Consent Overview: Turn this feature on in GTM to instantly see which tags have no Built-In Consent.
• Attach a Custom Event: Use Consent Studio's consent_update or custom dataLayer event as the trigger instead of 'All Pages'.
• Instant activation: The moment the visitor clicks 'Accept', Consent Studio fires an event immediately. Your marketing tags still fire within a few milliseconds — with the attribution of that first page view intact.

Conclusion

The difference comes down to milliseconds, but it determines whether you steer on clean data or on blind spots. Always put Consent Initialization first, then set up your Google Tag, and only let marketing tags fire based on the consent event. That way your container stays GDPR-compliant and you still measure the first page view of new visitors.