Deleting existing targeting criteria through `POST batch/accounts/:account_id/targeting_criteria` result in a 404


#1

As found here:

Any Delete operation with the batch endpoint result in a 404 Not Found error, when the creation is successful at anytime.
Could you confirm thats still the case today? Could you provide an ETA on this?

Thanks in advance.


Batch delete FOLLOWERS_OF_USER targeting criteria throws an error
Batch delete NETWORK_ACTIVATION_DURATION targeting criteria throws error
Batch delete FOLLOWERS_OF_USER targeting criteria throws an error
Batch delete NETWORK_ACTIVATION_DURATION targeting criteria throws error
#2

Thanks for the question, @ecoutelis, and for searching through the forums before posting. This is still an issue and we don’t have an ETA to share yet. We’ll update the threads once we have more information.


#3

Thanks for the quick answer @juanshishido.
About the v3 breaking changes, to quote the changelog:

The PUT accounts/:account_id/targeting_criteria endpoint is no longer available. We’ve decided to make this change because the replace behavior with this endpoint caused advertiser confusion and it was not consistent with our other PUT endpoints that update a single resource at a time. Instead, partners should use the POST batch/accounts/:account_id/targeting_criteria endpoint, which provides greater flexibility including the ability to both add and remove targeting in a single request.

Since you’re promoting the use of this endpoint instead of the PUT one, do you think there is any chance that a working Delete operation will be live by the EOL of the v2 (1st of august 18)? Or should we implement a temporary workaround with the DELETE one?


#4

Yes, that is our plan. We will let you know once we have more information. Thanks!


#5

Hi @juanshishido , any news/ETA since the last time?


#6

@ecoutelis: Quick update. We’ve fixed this issue for the following targeting types:

  • PLATFORM_VERSION
  • NETWORK_ACTIVATION_DURATION_GTE
  • NETWORK_ACTIVATION_DURATION_LT

We are working on fixing this for FOLLOWERS_OF_USER, too. We’ll update this thread once it’s been resolved.


#7

Hi @juanshishido, any news since the last time about FOLLOWERS_OF_USER?


#8

Yes, we’ve got a fix merged. We had planned to deploy yesterday, but decided not to. The fix should be in prod soon. I’ll update the thread once it is. Thanks, @ecoutelis!


#9

Awesome, thanks @juanshishido


#10

@ecoutelis: We deployed this morning. Please let us know if this resolved all the issues you saw. Thanks for raising this!