@zach_shearer What we decided to go with was a bit of a simpler
approach: Instead of adding custom conditions for each rule, we instead
created a separate property for all of our rules that don't require any
non-essential cookies and moved them there. That way, we load in the
pre-consent container first, and the rest after consent is given.
I figured out the solution. What was happening is that we are loading 2
properties on our page: One for scripts that can run before a cookie
consent check, and one for scripts that can run when the consent was
given. But the property scripts are set up to not load if: 1) The
window.__satelliteLoaded variable is set to true2) window.satellite is
already set But that's easy to solve if you do the
following:window.__satelliteLoaded = false; window._satellite = null;
Before loading the next property...
Hi, I'm trying to get a rule to load via firing a custom event on the
rule. We have the following event set up for it: However when we run
CustomEvent('ConsentGiven'));Nothing happens. The odd thing is when we
attach the Adobe Experience Cloud Debugger, and have it replace the
Launch Embed code with one in dev, then it works. But otherwise, it
an async script tag into the header.Can ...