Skip to content

Commit 346b8ca

Browse files
authored
Merge pull request #392 from segmentio/repo-sync
repo sync
2 parents 730f217 + e541bec commit 346b8ca

File tree

2 files changed

+4
-7
lines changed
  • src/connections/destinations/catalog

2 files changed

+4
-7
lines changed

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

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -128,3 +128,7 @@ The Google Analytics 4 [debug mode](https://support.google.com/analytics/answer/
128128
### Mobile Data
129129

130130
Google recommends use of their Firebase SDKs to send mobile data to Google Analytics 4. To assist in your implementation, Segment has a [Firebase destination](/docs/connections/destinations/catalog/firebase) available for mobile analytics. For more information on linking Google Analytics 4 properties to Firebase, see [Google Analytics 4 Firebase integration](https://support.google.com/analytics/answer/9289234?hl=en){:target="_blank"}. Segment's Google Analytics 4 destination is currently only compatible with web streams.
131+
132+
### Reserved Names
133+
134+
Google reserves certain event names, parameters, and user properties. Google silently drops any events that include [these reserved names](https://developers.google.com/analytics/devguides/collection/protocol/ga4/reference?client_type=gtag#reserved_names){:target="_blank"}. If you notice that your data isn't appearing in Google, please check that you're not using a reserved name.

src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,6 @@ hide-dossier: false
66
id: 60ae8b97dcb6cc52d5d0d5ab
77
---
88

9-
> info ""
10-
> This document is about a feature that is in beta. This means that the destination is in active development, and some functionality may change before it becomes generally available.
11-
12-
> success ""
13-
> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Google Enhanced Conversions Segment destination.
14-
15-
169
The Google Enhanced Conversions destination enables you to improve the accuracy of your conversion measurement. You can supplement existing conversion tags by sending first-party customer conversion data from your website, such as email address, to Google Ads. Segment hashes this data and sends it in a privacy-safe way. Google matches hashed data with signed-in Google accounts to attribute the conversion to ad events, such as clicks or views. To learn more about Google Enhanced Conversions, see Google's documentation [About enhanced conversions](https://support.google.com/google-ads/answer/9888656?hl=en-GB){:target="_blank"}.
1710

1811
> warning "Before you begin"

0 commit comments

Comments
 (0)