Google Gtag
The Google Gtag destination provides a unified interface for sending events to Google Analytics 4 (GA4), Google Ads, and Google Tag Manager (GTM) through a single destination configuration. Loads gtag script dynamically, initializes the gtag function with your config, handles Consent Mode v2 commands automatically, and pushes mapped events to Google services.
Gtag is a destination in the walkerOS flow:
Installation
- Integrated
- Bundled
Configuration
This destination uses the standard destination config wrapper (consent, data, env, id, ...). For the shared fields see destination configuration. Package-specific fields live under config.settings and are listed below.
Settings
| Property | Type | Description | More |
|---|---|---|---|
como | boolean | object | Consent mode configuration: false (disabled), true (use defaults), or custom mapping | |
ga4 | object | GA4-specific configuration settings | |
ads | object | Google Ads specific configuration settings | |
gtm | object | Google Tag Manager specific configuration settings |
Mapping
Per-event rules under config.mapping. For the standard rule fields (consent, condition, data, batch, name, policy) see mapping.
| Property | Type | Description | More |
|---|---|---|---|
ga4 | object | GA4-specific event mapping | |
ads | object | Google Ads-specific event mapping | |
gtm | object | GTM-specific event mapping |
Examples
Add to cart
A product add event is mapped to the GA4 add_to_cart event with item details and value.
Google Ads init
The destination bootstraps gtag and configures a Google Ads account via its conversionId.
Consent Mode v2
A walker consent command with marketing and functional granted updates gtag Consent Mode v2 parameters.
GA4 init
The destination bootstraps gtag and configures a GA4 property via its measurementId.
GA4 include all
Include flattens every event section into prefixed GA4 params, exposing data, context, user, source, and event fields.
Ads conversion
An order complete event is sent as a Google Ads conversion with a configured label and transaction value.
GTM dataLayer push
A page view event is pushed to window.dataLayer for GTM with the mapped event name and parameters.
GTM init
The destination initializes the dataLayer and pushes the gtm.js start event for a GTM container.
Multi-tool push
A single order event fans out to GA4, Google Ads, and GTM from one mapping rule with per-tool settings.
Page view
A page view event is forwarded as a GA4 page_view event with no additional mapping.
Purchase
An order complete event is mapped to the GA4 purchase event with transaction details and nested product items.
Next steps
- Mapping: transform events for Google's expected format
- GA4 configuration: detailed GA4 setup
- Google Ads: conversion tracking
- Consent management: control when events are sent