"Page" is essentially a special reserved prop, and either props or eVars (set at a HIT level expiry) could be used. You don't have to leave your eVars with a persisting value... Since props have a max length of 100 and eVars have a max length of 255, I have many eVars set up to track like props, to capture larger value items.... (and also because 75 props isn't enough for us.. I had to spill over into using eVars like props). And for this type of data, i.e. "Page Name" I wouldn't recommend using anything other than a HIT level dimension...
No matter what you use, even multiple of the same page within the visit will automatically de-duplicate at the visit level, next sample:
Visit 1
- Page A
- Page C
- Page D
- Page A
Visit 2
- Page B
- Page E
- Page B
- Page A
| |
|
Page Views |
Visits |
| Pages |
|
8 |
2 |
| |
Page A |
3 |
2 |
| |
Page B |
2 |
1 |
| |
Page C |
1 |
1 |
| |
Page D |
1 |
1 |
| |
Page E |
1 |
1 |
So Page A was viewed twice in Visit 1, and once in Visit 2; you can see that all 3 PVs are accounted for, and only the two Visits as a whole show up in your Visits column.
Likewise, Page B was viewed twice in Visit 2, and not at all in Visit 1... both PVs are counted, and only the single Visit is shown in the row for that page.
You don't need to sum the Visits... in this sample, if you summed them, you would be ended up with 6 Visits (but in no way did that data come from that many visits).. this would inflate your data, and any division done on that would also be divided by an inflated value.... this seems like a way to build inaccuracies than anything...
Even if you were looking at a specific sub-set of pages, adding the individual visits for Page A, Page B and Page C for example could end up being a greater number than your total visits. Is let's say you added these up and every visit had page A and Page B and Page C during the visit..
If you added visits to Page A and Visits to Page B and Visits to Page C... you would have three times the value of your total visits, resulting in something like:
300/100 (Visits to A, B and C / Total Visits) < Which I do not think is really what you want.
Sticking with the A/B/C sample for now, are you trying to get a "Percent of Visits that came to A, B or C"? Or maybe a "Percent of Visits that came to A, B and C"?
Because if you are trying to do that, like my earlier suggestion stated, you can create a segment:
HIT
Page equals A
OR
Page equals B
OR
Page equals C
OR
VISIT
Page equals A
AND
Page equals B
AND
Page equals C
The second means that all three must occur within the same visit.
Then you can just do a calculated metric of:
(segment + Visits) / Visits
You leave it formatted as decimal to get something like "0.48" or format it as a percent like "48%" so that you can say that 48% of Visits came to A/B/C (whether you are using the OR or AND segments)
If you need this by Visitor, are you looking for Visitors that Visited those pages? In the same visit or over multiple visits? So something like "Percent of Visitors that came to A, B or C"? etc.. then you will need some new segments, but the logic for the calculated metric would be similar...
Or maybe I am not understanding what you are trying to do.. but summing the columns that will result in inflated Visit numbers does not make sense to me the way you have described it....