Yeah, sometimes it's easy to forget about when you are so used to using your custom value, lol

Yes, but I would be a little concerned about that Visit attribution...   On one hand, this means that you don't have to set the value explicitly on your clicks and actions (the value will persist)... on the other hand, clicks and actions that occur before the page view, or pages that fail for some r...

Yep, we got hit by it too... I don't recall seeing an official statement about it... I only see basic info available about the issue in status.adobe.com... that there was a major outage, and that it was resolved....

Page and Page Name are the same thing.... s.pageName is "Page" in workspace...   If you want to have the page / page name available on your clicks/actions, you need to track it as a custom dimension.   I call my custom dimension "Page Name", and I use an eVar so that I can have longer names than the...

In addition to this... Page Name cannot be used with Click / Action calls...    Interestingly, Adobe doesn't actually have a reserved metric for "Page View"... this metric is calculated based on the existence of "pageName" and/or "pageURL" in the data... anything with either or both of these values ...

Bonjour,    Cette réponse a été rédigée avec l'aide de Google Traduction.   J'utilise rarement le panneau « Résumé de la page ». Je préfère généralement créer mon propre rapport et inclure les visualisations les plus pertinentes pour le public visé. Ceci dit, c'est un moyen simple de créer rapidemen...

Yes, and this might kick off some additional needs and discovery into the implementation... 

One more thing... splitting this with classifications wouldn't work well... at least not without some prefix for each value (which would use even more characters, risking truncation even sooner)... since there is no defined order... unless you are just using generic buckets like "first", "second", "...

Not a bad idea, assuming they aren't at risk of having the values truncated... I use eVars (with a Hit expiry) in lieu of props all the time, to get around the 100 character limit in props.   Given the ever growing list of values, if all filters are eventually selected, this could very easily exceed...

That's a good check... if the scope of the segment is incorrect, it could be looking at All Visits from all visitors that performed action X at any time during the report period... instead of limiting the data to Visits where Action X is performed.   Given this table, and what it is trying to show b...