Added some more context to my initial reply.  No: don't tick it on page views since the user will likely stay long enough to make the request go through tick it in cases where you experience aborted tracking callsas mentioned, none of your extensions, even the Experience Platform Debugger will be ab...

Hi @gmadala  ticking the checkbox will turn the request into a beacon/ping that is choosing a different request type. You regular requests are GET or POST requests, whereas a beacon is designed/intended to be sent in the browser background which will likely improve tracking accuracy. This can be cru...

Especially since it's China, it may have to be set up differently. let us know if support had some answers 

No, API access should suffice 

Hi @leozh1  your general setup looks ok. Not 100% sure about whether the IP ranges will be the same as the data collection servers.     I would reach out to support for more details on the error. Maybe they can see something in the logs. 

OneTrust has built-in dashboards that show you consent rates per category (shown/accepted/rejected), so I would rather look at those 

Support acknowledged the issue and confirmed these are not billable calls but somewhat a UX issue that will be fixed beginning of next year (low prio)   Numbers have gone down again in the meantime    not sure how this can be a UX issue and only affect a single month though... But let's trust what t...

The key is that the necessary parameters are appended to the href of your link. One way or another, you will need to be able to get these parameter appended to the links. If you are having completely different domains, you will not be able to read these cookies. Do you see a demdex cookie on your we...

You can actually use the same value for all of them. It is the domain you see your tracking events being sent through when you look at the network tab and filter for "/b/ss".

Hi @reddy_y-11  the API has nothing to do with AEP nor WebSDK. You will just get access to individual Launch properties.   there used to be a Reactor Sync repository which I think was no longer maintained and still uses JWT tokens and not Oauth https://github.com/adobe/reactor-sync