FWIW, this question came up again and I just retested, and it really is problematic as it is. Take a look at https://digitaldatatactics.com/test/testGlobalVars.html, which walks through the problems, which essentially boils down to:Global Variables only evaluate once, on page view, which is bad if y...

That would be great, thank you. I'll send a PM.

These are the questions that remain AFTER I've spoken to account reps:) (which, in general, as a consultant, I don't have much access to, though a few have kindly met with me and answered some of my questions and helped me understand the different options for purchasing, just not the nitty gritty of...

I'm really excited about this series, I'd love to see more of what CJA can do. A lot of the questions in the chat of the first session are about this vs Adobe Analytics vs Experience Platform, and I'll admit I've really struggled to sort that out for myself in the last year or so. The documentation ...

I had a very similar issue a few months back- after a LOT of back-and-forth with client care, we figured it out: Customer Attributes is now kinda buried behind Audience Library (when you click "People", it wants to take you to Audience Library, then you'd click the tab that takes you to Customer Att...

I'm assuming this is for version 5 SDKs? (https://aep-sdks.gitbook.io/docs/using-mobile-extensions/mobile-core/configuration ?)In launch, go to "Environments" in the left rail: Then click the little box icon for the appropriate environment (dev, staging, production- I'm assuming you're still in dev ...

I want to say sometimes the "submit" trigger is looking for the element of the FORM that is being submitted, not the submit button.  If you can't get the developers to set a reliable direct call for you, I'd try either changing the trigger to be click-based on the submit button, or submit-based on t...

Did you ever find a way to do this?

After testing, I can confirm- the global variables only fire on s.t beacons. They may hang around until an s.tl beacon, but they're not freshly set for s.tl beacons. If you fire clearvars after a page view, you will not have the global variables on subsequent s.tl beacons. 

I only just got around to testing this and for me, the global variables still not fire on on an s.tl beacon (if I had set clearvars on the page view beacon- I suspect this might be the difference?).