Skip to content

Commit a0b8207

Browse files
authored
Merge pull request #6043 from segmentio/estgc-patch-2
Add Troubleshooting for invalid list ID.md
2 parents 975e163 + 94f7967 commit a0b8207

File tree

1 file changed

+4
-0
lines changed
  • src/connections/destinations/catalog/adwords-remarketing-lists

1 file changed

+4
-0
lines changed

src/connections/destinations/catalog/adwords-remarketing-lists/index.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -127,6 +127,10 @@ If a user has more than one email address or IDFA on their account as `external_
127127

128128
Make sure that this destination was created in [Engage](/docs/engage/) as it requires additional event data not available in standard destinations.
129129

130+
### Invalid user list ID error in Event Delivery
131+
132+
When you first connect a destination to an audience, Segment triggers a call to the destination to create the audience downstream. Once Segment creates the audience, the destination API returns an audience ID. For subsequent updates to the audience in the destination (adding or removing users), Segment uses this ID to send requests to the destination. The invalid user list ID error usually means that the audience ID no longer exists in the destination. To resolve this, you'll need to either recreate the audience or create a *new instance* of the destination and link it to the audience. Removing and re-adding the same instance of the destination will not work.
133+
130134
## FAQs
131135

132136
#### What Google Ads campaigns does Engage support?

0 commit comments

Comments
 (0)