New to Google Tag? See the Google Tag Overview for general information about gtag.js and architecture options.

Google Tag (GTag) - Decoupled Architecture

This section covers the decoupled architecture for configuring Google Tag syncs in MetaRouter. In the decoupled model, Google Tag Settings acts as a parent that manages gtag.js library loading, with each Google product configured as an independent child sync beneath it.

Google Tag Settings (Parent)
├── GTAG.js Tag ID
├── Load GTAG library
├── Load GTAG when zero consent granted
│
└── Syncs (Children)
    ├── Google Analytics 4
    ├── Google Ads
    └── Google Campaign Manager 360

This architecture gives you granular control over each product — you can add, remove, or update individual syncs without affecting the others. The parent Google Tag Settings must be configured and deployed before any child sync can function.

When to use the decoupled architecture: Choose decoupled when you need to manage GA4, Google Ads, and CM360 independently, or when your consent requirements differ across products.

New to Google Tag? See the Google Tag Overview for general information about gtag.js, how MetaRouter manages Google identifiers, and a comparison of decoupled vs. coupled architecture options.

Child Sync Guides

• Google Analytics 4 Sync
• Google Ads Sync
• CM360 Floodlight Sync