#1

We used to be able to append new audience to the same list before Sept 5th. But after we received

400 Bad Request {“errors”:[{“code”:“DUPLICATE_DETECTED”,“message”:“An audience with this name already exists. Please use a different name.”}],“request”:{“params”:{“account_id”:“xxxxx”,“name”:“yyyyy”}}

as error. We are using v7 of the Ads API : https://ads-api.twitter.com/7/

Has there been a change to the policy ? How should we do append operation ?

Thanks

#2

It started working as before today without any change from our end.

#3

Hey @DoKiet

This was an issue on our end and has since been resolved.

Thanks!

#4

Hi @imit8me,

Can you check again ? We are seeing the same error just now . Time is UTC. Thanks

2020-09-09 16:35:39.785 +0000 : Error while creating TailoredAudienceID: Response 400 Bad Request {“errors”:[{“code”:“DUPLICATE_DETECTED”,“message”:“An audience with this name already exists. Please use a different name.”}

#5

Hi

Looks like this is v8 specific behavior. Can you check why v7 also apply the logic ?

#6

Hi @imit8me

Can you check again ? Is this a permanent behavior ?

#7

Hey @DoKiet

Apologies for the confusion. We’ll double check on our end and get back to you. This behavior is incorrect and should only apply to v8.

Thanks!

#8

Quick update, the fix has been put in place and we expect the issue to be resolved later today. Let us know if you’re still experiencing issues.

Thanks!

#9

Hello, I am also getting this error.

Help…

#10

Hi!

I’m a user, not a developer.
I got to this forum after I found nowhere else to get help from.

So I think the problem that prompted the aforementioned error notification (“An audience with this name already exists. Please use a different name”) is still there.

I tried to add a CSV list and encountered the error message.
What can I do to solve this?

Thank you,

2
21864×767 42.2 KB

#11

@imit8me - Hey imit8me; I encountered this error on a client account when trying to update an existing user list. You mentioned above that this was resolved in the version 7 back in september but does not seem to work now. We are able to pass over lists successfully but updating is the issue. Can you assist?

{“errors”:[{“code”:“DUPLICATE_DETECTED”,“message”:“An audience with this name already exists. Please use a different name.”}],

#12

Hey @Tim_M_ActionIQ

To clarify, the constraint on duplicate audience name still exists though only the behavior has changed. Prior to v7, creating an audience with a duplicate name would return the id of the existing audience. After v7, an error message is returned instead.

Thanks!

#13

Hey @imit8me thank you for the feedback - I’m not sure that helps to solve what we are trying to do. Essentially our goal is to continue to dynamically update our advertising targeting audience. Why would it not be feasible to do so in V7? What version supports the ability to update the same list daily?

#14

Hey @Tim_M_ActionIQ

You should still be able to update user memberships to your list, however as mentioned only duplicated audience names aren’t currently allowed. Given the change in behavior for the endpoint, you’d have to use the GET custom_audiences endpoint to fetch the list of audiences, and use the name field to determine the appropriate id to use in any user membership update requests.

Thanks!