From 0d24c6c499af819ad18a786cbaa47180c3dbdbeb Mon Sep 17 00:00:00 2001 From: Liz Kane <68755692+lizkane222@users.noreply.github.com> Date: Fri, 31 May 2024 16:14:04 -0700 Subject: [PATCH 1/2] Update index.md ID Sync --- .../destinations/catalog/adwords-remarketing-lists/index.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/connections/destinations/catalog/adwords-remarketing-lists/index.md b/src/connections/destinations/catalog/adwords-remarketing-lists/index.md index 3c7ab2ca73..ce13f5b0dc 100644 --- a/src/connections/destinations/catalog/adwords-remarketing-lists/index.md +++ b/src/connections/destinations/catalog/adwords-remarketing-lists/index.md @@ -151,6 +151,9 @@ You can set an email on the user profile by including `email` as a trait, as a p If a user has more than one email address or IDFA on their account as `external_ids`, Engage sends the most recent id on the user profile to Adwords for matching. The match rate will be low if Google can't identify users based on the data that you provide. +> info [**ID Sync**]([url](https://segment.com/docs/engage/trait-activation/id-sync/)) +> Now with Segment's ID Sync feature, you can send additional identifiers to actions destinations. Since Google has a requirement on the limit of identifiers that can be sent in each request, the Google Ads Remarketing Lists destination can only be configured to send one additional identifier in its audience's payloads. If the Google Ads Remarketing Lists destination has already been receiving data from an audience, then configuring ID Sync on the destination afterwards will not be applied to the audience users retroactively, and would require a resync in order to add those identifiers to the entire user base. [Contact Segment support](https://segment.com/requests/integrations/) if you would like to request a resync of your audience to its Google Ads Remarketing Lists destination with the newly enabled ID Sync configuration added. + ### Invalid Settings error in Event Delivery Make sure that this destination was created in [Engage](/docs/engage/) as it requires additional event data not available in standard destinations. From 7529e6224e32710d8b0365c628534118be7e3c69 Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Tue, 29 Oct 2024 11:55:26 -0500 Subject: [PATCH 2/2] minor rewording --- .../destinations/catalog/adwords-remarketing-lists/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/connections/destinations/catalog/adwords-remarketing-lists/index.md b/src/connections/destinations/catalog/adwords-remarketing-lists/index.md index ce13f5b0dc..87467c4695 100644 --- a/src/connections/destinations/catalog/adwords-remarketing-lists/index.md +++ b/src/connections/destinations/catalog/adwords-remarketing-lists/index.md @@ -151,8 +151,8 @@ You can set an email on the user profile by including `email` as a trait, as a p If a user has more than one email address or IDFA on their account as `external_ids`, Engage sends the most recent id on the user profile to Adwords for matching. The match rate will be low if Google can't identify users based on the data that you provide. -> info [**ID Sync**]([url](https://segment.com/docs/engage/trait-activation/id-sync/)) -> Now with Segment's ID Sync feature, you can send additional identifiers to actions destinations. Since Google has a requirement on the limit of identifiers that can be sent in each request, the Google Ads Remarketing Lists destination can only be configured to send one additional identifier in its audience's payloads. If the Google Ads Remarketing Lists destination has already been receiving data from an audience, then configuring ID Sync on the destination afterwards will not be applied to the audience users retroactively, and would require a resync in order to add those identifiers to the entire user base. [Contact Segment support](https://segment.com/requests/integrations/) if you would like to request a resync of your audience to its Google Ads Remarketing Lists destination with the newly enabled ID Sync configuration added. +> info "ID Sync" +> [Segment's ID Sync](/docs/engage/trait-activation/id-sync/), you can send additional identifiers to Actions destinations. However, due to Google’s restrictions on identifier limits per request, the Google Ads Remarketing Lists destination can only include one additional identifier in audience payloads. If the Google Ads Remarketing Lists destination is already receiving data from an audience and you enable ID Sync afterward, the new identifiers won’t be applied retroactively to existing users. To update identifiers for the entire user base, a full resync is required. [Contact Segment support](https://segment.com/requests/integrations/){:target="_blank"} to request a resync with your new ID Sync configuration. ### Invalid Settings error in Event Delivery