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...

Yes, this is a really big issue for anyone using a Virtual Report Suite to "curate" their components. If I create a new segment, not only do I need to do the standard sharing to make it accessible to my peers, I have to also go into the VRS editor and make sure that segment is on the "include" side....

On another note, this also impacts getQueryParam functionality- I believe s(.Util.)getQueryParam takes advantage of s.pageURL, so unless you're updating s.pageURL currently, you might inflate tracking on query params.

In addition to the need for an "OR" operator (Allow for "OR" conditions in rules ), being able to nest conditions would be very powerful. For instance, I just did this custom code condition for a client:This would allow us to move out of custom code conditions, and possibly reduce redundant rules fo...

Currently, multiple conditions seem to always take an "AND" operator- for anything "OR", I go to custom code. It would be very helpful to be able to use "OR" conditions.For instance, if I needed to have a condition like "if the pagename is 'home' OR the page type is "product details", I would have t...

Add my votes to:crossVisitParticipationtimeParting (note- the DST values need to be updated, we're going in to 2019)getPercentPageViewed (not my favorite, but lots of folks still want it)appendListhitGovernorgetPreviousValue (see my note above as to why I still see this as needed)getValOnce (I'm sur...

Beautiful list!I do disagree on one point, though:  I'd say getPreviousValue is NOT replaced by data element persistence, unless you're VERY careful about timing- if I want to set the previousPageName, my PageName data element is going to return the CURRENT pageName, regardless of how long I told it...