Thanks Brandon! That is excellent news, I looked over the documentation.New question, how would I leverage the EU compliance cookie sat_track? That is what we are currently using to control the analytics implementation, so it would easiest to keep using the same thing. Thanks!
I created a rule which loads at the top, and the custom code is the visitorAPI.js file and added a condition. Any reason why this won't work? Then the code is still controlled by Launch but you can add the consent condition.
I have implemented a test with TrustArc, and I can stop everything but the Experience Cloud ID. The only solution I can find is to put the code outside of Launch and wrap the entire launch include in a conditional statement. If anyone has a better suggestion I would love to hear it.
I used the notation field at the bottom every time to add a note about what change I made and why. (well, most of the time ) I would like to see that in brought back in Launch. It's a good habit to get into.
In DTM it didn't matter which order you put in the s.props once you saved they resorted into order. So for example you could enter them in s.prop1, s.prop23, s.prop2, s.prop11. And when you saved and reloaded the rule it would sort them s.prop1, s.prop2, s.prop11, s.prop23. Which is really handy ...