We are seeing counts that are drastically different as one system is using eVar for page name tracking and another system is using prop for page name tracking. Regarding page name tracking, which is preferred, eVar or prop? Why?
Solved! Go to Solution.
Views
Replies
Total Likes
Like most answers, it really depends on what you are trying to achieve...
I for one prefer to use a Hit Level eVar...
This ensures that only where I set the value, it will exist... but the eVar allows for 255 characters, which is more than the standard pageName will hold (truncated at 100).
I also send the pageName value on all my actions, so that I have full correlation to the page where the click/action is performed...
When I use the page view metric, it will match the original page counts, when I pair with occurrences, I will get ALL page views and clicks/actions; and when I pair it with specific custom events for specific actions, I will only get those actions.
If you have a different count, I am guessing you have a visit level expiry, and you are not setting the value all all pages (assuming you are using the page view metric)....
Example:
Like most answers, it really depends on what you are trying to achieve...
I for one prefer to use a Hit Level eVar...
This ensures that only where I set the value, it will exist... but the eVar allows for 255 characters, which is more than the standard pageName will hold (truncated at 100).
I also send the pageName value on all my actions, so that I have full correlation to the page where the click/action is performed...
When I use the page view metric, it will match the original page counts, when I pair with occurrences, I will get ALL page views and clicks/actions; and when I pair it with specific custom events for specific actions, I will only get those actions.
If you have a different count, I am guessing you have a visit level expiry, and you are not setting the value all all pages (assuming you are using the page view metric)....
Example:
Awesome. Thanks @Jennifer_Dungan