great idea, really support this to be implemented ... might solve a lot of use cases where we currently add segments all over the tables ... @jenlasser 

can't you just change permission in the product profile for users who shouldn't see the anomaly detection?

as far as I know a tag will disappear as soon as it isn't used anymore. that means you should change the "misspelled" tags and they should disappear from the list (might take a few days...)if this is not the case, I suggest you file a ticket for CustomerCare

just right-click in the header column and select "show change to previous month". if that doesn't work you can create a calculated metric on your own.

and what happens if you have two (or more) s.tl() on the same page (without page reload an clear vars)? will it keep all the variables/events or always start "from scratch"?

the question is if you need a "clearVariables" at the end of all rules? otherwise I think it will keep the old variables/events and messing up tracking (eg. you set a specific event on s.t() and it will appear on the subsequent s.tl() call...

yes, please! thanks for adding the idea!

the problem with the event on first page view is that you miss the actions in the first page.to isolate the first page view (and actions on the first page) is just like Audrey's Tipp about "how many... until..." (just adopt "all hits until PageView 2" and set the event on the 2nd pageview).

Hi AndrewHere's your segment for the last page view (including all following s.tl() calls:

fully agree! thanks for adding the idea!