Skip to content

Commit f9be96d

Browse files
authored
Add Troubleshooting for invalid list ID.md
Typical error that comes up when the client deleted the audience in the destinaton
1 parent 4eb7bd9 commit f9be96d

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 the destination into an audience, a call to the destination will be triggered to create the audience downstream. Once that succeeds and the audience is created, the destination API returns an ID for that audience to Segment. Later on, for subsequent updates to the audience in the destination (adding/removing users), Segment uses this ID to send the request to it. This error usually means that the audience ID Engage is using no longer exist in the destination. To sort this issue, you will 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 instace of the destination will not work.
133+
130134
## FAQs
131135

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

0 commit comments

Comments
 (0)