Correct.. there is an option to change from "calculate percentage by
row" vs "by column" and i have both the high level dimension and the
breakdown dimension set to "row".... but its calculating across all high
level dimensions and not only within the breakdown.
Ok bear with me here...Row percentages with in a breakdown seem require
the full metric field to be included in order to be calculated across
the row. Otherwise it calculates across the entire report. Why does the
system generated percentages not match the calculated percentages?
Within a breakdown, the system generated ROW percentages are actually
percentages of the higher level dimension for that specific day. See
screenshots below... i.e. Reference and Tools breakdown for Sept 1...
Aud Non Re...
Typicall evars are set to persist although that can be changed to not
persist.... Instances: Shows the number of times a given variable was
defined in any image request, including PageView and Non-PageView Server
Calls.Occurrences: Counts the number times a variable was defined or
persisted across both PageView and Non-PageView Server Calls.
Events can be configured to increment at several levels... i.e. once per
visitor or visit or every time. so if an "event trigger" happens 10
times during a single user session, depending on how you have that event
configured it could show 1 or it could show 10. Evars persist (unless
explicitly built to not) beyond the hit they are set on. So to use
"instances" with an evar can be strange because it will only count the
number of times it was set and will not include persisted values.
"The ‘Instances’ metric shows the number of times a dimension was
explicitly defined in an image request. Some dimensions, such as eVars,
persist dimension items past the hit they are set on. This metric is
useful when you want to see the number of times a dimension item was set
without the hits where that value persisted."
Based on everything i know the full URL is not an available dimension
via workspace unless you are setting that value into an actual prop.We
use custom beacon code to parse out specific query parameters from URLs
and set those into their individual props for reporting purposes
When a user clicks we write the page name, module and link they click on
to a cookie. When the next page loads we set those 3 values into props
referring_page, referring_module and link. Correlate page to referring
page.. or breakdowns in workspace and you'll always have the page
before. For true before and after, flow might be your best bet. I'm
still trying to figure it out myself.