Page Scroll Depth: Discrepancies between Evars and Props Page Name | Community
Skip to main content
E
EMeyer79
Level 3
June 30, 2020
Solved

Page Scroll Depth: Discrepancies between Evars and Props Page Name

  • June 30, 2020
  • 1 reply
  • 2311 views

Hello All!

We recently implemented page scroll depth events. We have events fire on 25, 50, 75 and 100 percent scrolled. We also, have a Page Name Prop and evar that we're using for reporting on scroll depth. 

 

When I create a table with Page Name as the Evar (dimension) and then add the scrolling events, I return suspicious looking data. 100% scrolled is way higher than 25% scrolled and the numbers are quite large. 

 

When I use the Page Name Prop (dimension) against the events I get what seems to be more correct numbers. 

 

My question is why do are the numbers against the Page Name prop and evar so widely different? Should I use the Prop against the events? I thought evars were better paired with events? Or are the evar numbers correct? 

 

Lot's to digest and thanks for the help!

 

Eric

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by kainth

@emeyer79Page Name (prop) & Page Name (eVar) are showing different results because of the expiration of the variable. Props has the expiration set to the hit level whereas you can set custom expiration for the eVar like you can set the eVar to expire at hit, visit, visitor & day etc. So, when we are looking at the scroll event data against a Prop it will report the data when the Prop value & event was set in the same hit. But, if you look at the scroll event data against an eVar then in reporting, it will show us the data when the event & eVar values are either set in the same hit or when the eVar value was already persisting from the previous hits & then the event was set.

So, you can opt for either prop or an eVar depending upon your requirement as I am not sure what the expiration is set for the eVar.

Please let me know if you have any further questions.

Regards,

Abhinav

1 reply

K
kainthAccepted solution
Level 6
June 30, 2020

@emeyer79Page Name (prop) & Page Name (eVar) are showing different results because of the expiration of the variable. Props has the expiration set to the hit level whereas you can set custom expiration for the eVar like you can set the eVar to expire at hit, visit, visitor & day etc. So, when we are looking at the scroll event data against a Prop it will report the data when the Prop value & event was set in the same hit. But, if you look at the scroll event data against an eVar then in reporting, it will show us the data when the event & eVar values are either set in the same hit or when the eVar value was already persisting from the previous hits & then the event was set.

So, you can opt for either prop or an eVar depending upon your requirement as I am not sure what the expiration is set for the eVar.

Please let me know if you have any further questions.

Regards,

Abhinav

    E
    EMeyer79Author
    Level 3
    June 30, 2020
    Thank you Abhinav. That makes so much sense. Is there a good cheat sheet resource for best practices setting expirations for evars? Or is this up to us? Also, I assume this isn't retroactive once we change it from visit to hit? Page Name makes the most sense at the hit level. I really appreciate it.
    Terms & ConditionsAccessibility statement

    Loading footer...