Skip to content

Commit f2d8a05

Browse files
Merge pull request #4784 from segmentio/bobbyatsegment-patch-11
Add section covering tracking UTM parameters
2 parents 0532220 + bb7663b commit f2d8a05

File tree

1 file changed

+9
-0
lines changed
  • src/connections/destinations/catalog/actions-google-analytics-4-web

1 file changed

+9
-0
lines changed

src/connections/destinations/catalog/actions-google-analytics-4-web/index.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -84,4 +84,13 @@ Google may take [24-48 hours](https://support.google.com/analytics/answer/933379
8484

8585
Ensure that at least one mapping has been configured and enabled in the destination mappings for an event you want to send to Google Analytics. If no mappings are enabled, the destination does not send events.
8686

87+
1. Disable the **Page Views** advanced setting (set it to *False*) so only Segment's `analytics.page()` sends to the GA4 SDK. Or,
88+
2. Edit or disable the preset **Set Configuration Fields** mapping so only the `page_view` included in the gtag.js snippet sends to the GA4 SDK.
89+
90+
### Tracking UTM Parameters
91+
92+
UTM Parameters are automatically tracked and sent to Google when they are present in the URL. For example, with the following URL:
93+
`https://www.example.com/?utm_content=email_variation1&utm_medium=email&utm_source=email_promo&utm_campaign=summer_sale&utm_id=abcd`
94+
95+
Without any further configuration, traffic-source data for `campaign`, `campaign_id`, `content`, `medium`, and `source` will populate in GA4. This can be observed on Google's side by triggering a `Page` call with UTM parameters present in the URL and navigating to the **Realtime overview** report in GA4 to see the resulting `page_view` event under the _Event count by Event name_ card.
8796

0 commit comments

Comments
 (0)