From 7c5210b75c8300f352658ad2c800346a8567edcd Mon Sep 17 00:00:00 2001 From: Kartheek Ganesh Date: Sun, 29 Sep 2024 20:50:55 -0700 Subject: [PATCH] AMP-108054 Minor updates to Google Ads and Streaming limitations --- .../collections/data/en/destination-event-streaming-overview.md | 1 - content/collections/destination-catalog/en/google-ads.md | 2 +- 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/content/collections/data/en/destination-event-streaming-overview.md b/content/collections/data/en/destination-event-streaming-overview.md index fb79c53d2..c3d220c5f 100644 --- a/content/collections/data/en/destination-event-streaming-overview.md +++ b/content/collections/data/en/destination-event-streaming-overview.md @@ -21,7 +21,6 @@ With event streaming, you gain access to user-friendly, configuration-based tool ## Limitations -- **Forwarding transformed data:** Amplitude event streaming only supports raw (untransformed) events, event properties, and user properties. [Transformed](/docs/data/transformations) events and properties (such as merged properties) aren't supported. - **Format for user properties:** All forwarded user properties are currently sent as strings except for [Braze streaming](/docs/data/destination-catalog/braze) and [Iterable streaming](/docs/data/destination-catalog/iterable) destinations - **Reserved keywords:** Specific keywords, including `_all` and `_identify`, can't be used as event names when streaming events from Amplitude. - **Historical data:** Amplitude's streaming integrations focus on data from the setup point forward. Historical data isn't included in this process, which ensures that Amplitude transmits only events captured post-configuration. diff --git a/content/collections/destination-catalog/en/google-ads.md b/content/collections/destination-catalog/en/google-ads.md index c48f3f975..4ba7c65de 100644 --- a/content/collections/destination-catalog/en/google-ads.md +++ b/content/collections/destination-catalog/en/google-ads.md @@ -50,7 +50,7 @@ After you create the destination, you must configure the settings. 5. Enter the [Google Ads Customer ID](https://support.google.com/google-ads/answer/1704344?hl=en): A Google Ads Customer ID is a unique identifier assigned to each advertiser or business that uses Google Ads. It helps Google track and manage accounts, campaigns, and billing information for advertisers. Find the Google Ads Customer ID at top-right when logged into Google Ads. Enter the ID **without** hyphens. 6. Enter the [Google Ads Conversion Action ID](https://support.google.com/google-ads/thread/105330243?hl=en&sjid=5504033552721490234-EU): This is a unique identifier associated with a specific conversion action in Google Ads, and represents an action that you want your visitors or users to take. For example, make a purchase, submit a contact form, or sign up for a newsletter. Once the conversion action is visible on Google Ads, click it to visit the details page (path: `/conversions/detail`). The URL has a parameter `ctId=`. Copy the value of that parameter as the Conversion Action ID. 7. To send events ingested by Amplitude to Google Ads, toggle *Send Events* to *Enabled*. Expand the *Select and filter events* panel, and select which events to send. Amplitude recommends that you send only the events you need in Google Ads, rather than selecting *All Events*. -9. Map the `event_time` Amplitude property to the `Conversion Date Time` property in Google Ads +9. Map the `gclid` Amplitude property to the `GCLID` property in Google Ads. 10. Save when finished. ### Setup tracking conversion in Google Ads