I am using Adobe Standard v2 consent standard for communicating the consent preference via Web SDK extension. It works fine for non-gdpr regions but, for GDPR regions, it shows the CORS error. Below is the the error am getting. Access to fetch at 'https://adobedc.demdex.net/ee/v1/privacy/set-consent...

Yes, we were able to find out the root cause. It was with the ECID opt in settings. Looks like the extension was not properly published so it was considering the AA flag to be false. After republishing, it resolved the issue.

We have a condition (One trust extension) to be evaluated in the page load rule but since, the logs show that the condition is met and the firing page view beacon, I believe this shouldn't be impacting this. I suspect this is something related to either ECID or the One trust Extension

There is no page bottom script on the page as we are deploying the launch asynchronously. Also, I believe even if all of the data layer values are not there but the tag should still fire with at least those which are already populated by that time?

HI @Kishore_Reddy ,Yes, I tried it on different machines, connections and browsers as well.

It is a standard web application.

I am facing an issue where my Adobe Analytics page view beacon is not firing. I could see my rule getting fired, the tracker with all the variables is getting set and the logs also show "Firing Page View Beacon". However, there is no beacon triggered. When I call s.t() with a delay of 500ms in a cus...