Hello Gabriel,
So, in summary, targeting certain user lists and the affected regions at the same time result in no incoming bid requests? The term "branding campaign" isn't used in our APIs, so it may be helpful if you described what pretargeting settings are equivalent to one.
> No point of presence in the region: While we currently lack a local presence, branding campaigns successfully receive traffic from the region, which makes this issue even more puzzling.
Does this mean that you don't have any bidding endpoints local to the trading location for Asia?
> What could be causing pre-targeting with user lists to fail while branding campaigns work normally in Oceania and Asia?
For cases involving user lists in general, it is possible that the size of these lists have not reached the threshold needed to become targetable. If they aren't targetable, you wouldn't receive bid requests for pretargeting configurations that specifically target them, regardless of the region. It could also be the case that the targeted users aren't in the targeted location, as such a mismatch in the pretargeting configuration also wouldn't result in any bid requests.
As an aside, assuming I was correct that you don't have any bidding endpoints located in and configured for the Asia trading location, that would greatly reduce (but not necessarily eliminate) the traffic coming from that location. It could be that the branding campaigns you mentioned are receiving some of the minority of requests for those locations that do not originate from the Asia trading location. Given that bidding endpoints that are not configured for the Asia trading location won't receive the majority of traffic from that region, it could be that the combination of that and further filtering via your pretargeting configuration is resulting in no bid requests.
> Are there additional steps or configurations we should check to resolve this issue?
It would be worthwhile to see how this behavior changes w/ bidding endpoints located in and configured for the Asia trading location. Otherwise, you may want to investigate how large these affected user lists are. If there are under 1,000 IDs, it is fair to say that the issue could
be related to that. There is, unfortunately, no programmatic or UI solution for this on our end at this time, so the only way to be reasonably sure is if you logged how many IDs were successfully added to these lists.
