Google Tag Manager integrations: GA4, Ads, and consent
GTM's value comes from what it connects to, not the container itself. The integrations that matter most for most businesses are GA4, Google Ads, a consent platform, and whatever CRM or ecommerce system holds the transaction data.
GA4 integration
A GA4 Configuration tag loads once per page and establishes the base connection; GA4 Event tags, triggered by data layer pushes, send specific actions - purchases, sign-ups, form submits - to GA4. The integration is only as reliable as the data layer feeding those event tags, which is why GA4-specific implementation depth lives on our GA4 practice site rather than being duplicated here.
Google Ads integration
GTM ships native tag types for Google Ads Conversion Tracking and Remarketing. Because they read the same data layer events as GA4 tags, a single well-built purchase or lead event can feed both platforms - the common mistake is building two separate, slightly different implementations instead of one shared event.
Consent platform integration
A consent management platform (OneTrust, Cookiebot, and others) sets a consent state, typically via Google's Consent Mode v2 API. GTM tags then read that state - either through built-in consent settings on each tag or through load-rule logic - and only fire when the visitor's consent allows it. Getting this sequencing wrong (tags firing before consent is read) is one of the most common privacy-compliance gaps we find in an audit.
| Integration | What it needs | Common gap |
|---|---|---|
| GA4 | Config tag + event tags reading a specified data layer | Events fired without matching parameters GA4 expects |
| Google Ads | Conversion/remarketing tags on the same data layer events | Duplicate, separately-built implementation vs. GA4 |
| Consent platform | Consent Mode v2 signals wired before tags evaluate | Tags firing before a consent decision is recorded |
| CRM / ecommerce | Data layer populated from the platform's native events | Values read from the DOM instead of the platform's own data |
Platform-specific notes
WordPress and Shopify usually populate the data layer through theme code or a tag-management-aware plugin. Magento and HubSpot follow the same contract with their own population method. None of these change what GTM itself needs - a clean data layer and correctly scoped triggers - only how that data layer gets filled in.
Need OneTrust-specific configuration detail? See our OneTrust practice site for the consent-platform side of this integration.
Common questions
How does Google Tag Manager integrate with GA4?
Through a GA4 Configuration tag that loads once per page, and GA4 Event tags triggered by data layer pushes for specific actions - purchases, form submits, sign-ups. The integration is only as good as the data layer feeding those event tags.Can GTM integrate directly with Google Ads?
Yes - GTM has native Google Ads Conversion Tracking and Remarketing tag types that read your data layer the same way GA4 tags do, so a single well-built event can feed both platforms without duplicate implementation work.How does GTM work with a consent management platform like OneTrust?
The CMP sets a consent state (via Consent Mode v2 or its own API); GTM's built-in consent settings on each tag - or load-rule logic - gate whether marketing and analytics tags fire based on that state. See our OneTrust practice site for platform-specific configuration detail.Do you integrate GTM with WordPress, Shopify, Magento, or HubSpot?
Yes, on all four. The container and data layer contract are identical across platforms; what differs is how the platform populates the data layer - a plugin, theme code, or a CRM's native event pipeline.
Get your integrations reconciled to one data layer.
GA4, Google Ads, and your consent platform should all read the same events - we make sure they do.
Book a Strategy Session