There appears to be a bug in the batch DELETE endpoint for targeting criteria. Can you investigate why it can’t find all the targeting criteria that are returned by the batch GET endpoint?
Also, when I delete all the targeting criteria via the non-batch endpoint, some of them will be returned with “deleted=false” from the batch GET endpoint.
I’d like to understand if there is some kind of cache or latency within your system that is affecting these batch endpoints. They are returning inconsistent data from the non-batch endpoints, and its causing difficult to reproduce issues with our campaign targeting.
On our campaigns, we sometimes have 300-400 targeting criteria we need to delete when changing the targeting. It is not a scalable solution to use the non-bulk endpoint for this kind of thing.