I'd imagine a potential issue with this is that your pageload/top/bottom rules won't fire on the new library... by the time you set this in the console, those triggers have already run.

Do we know at what point this issue started? In what version of the Analytics Extension?

I think that'd be great, as a bare minimum.

As a followup, I just retested this.... and it is still a problem. It doesn't seem to make a difference whether the "subsequent" beacons are s.t() or s.tl()... my global variables only get set on my initial rule.

It sounds like this is actually a defect (with the analytics extension), based on discussions with the product folks- something to do with the timing on pageBottom if you are using the Experience Cloud ID service. I believe it's been communicated to the folks in charge of that extension so hopefully...

This is also true for on the Data Element creation page:

jen.lasser Alas, I have some followup- I'm doing a training on Wednesday and have given a training account the same sorts of access/rights that my users will have, so we see the same things. And now I see that without fuller rights to Virtual Report Suite admin, I don't even GET the "add new compone...

Note this is related to/a duplicate of Have components addition in Virtual Report Suites be "exclude only" .

I'd say duplicating things in an eVar AND a prop used to be a common (even a best) practice but agree with Gigazelle​ that it isn't needed as much anymore, because Adobe is continually removing barriers that used to exist between "traffic" and "conversion" information. Because they aren't needed to ...

Thanks for looking into this and responding, Jen! That "component may not appear" message does help a bit, though the messaging is a bit weird (something more along the lines of "would you like to include this component in the VRS? Yes/No" would be much clearer, and if I'm in a VRS it should default...