Using Events on a page to measure scroll depth | Community
Skip to main content
AngelDee77
AngelDee77
Level 4
November 4, 2020
Solved

Using Events on a page to measure scroll depth

  • November 4, 2020
  • 1 reply
  • 6385 views

i'm using the Time and Scroll Event plugin in Launch.  The plan is to track on a page the scroll depth by 25, 50, 75, 100 percent.  i'm not using getpercentplugin because the business wants to know on first page visits the interaction so it wouldn't work.

 

i'm running into issues with my implementation for a few reasons.  First, although i've allocated success events to each percentage, when the rules are successfully firing, i'm getting extra calls.  For example:

 

🚀 [Adobe Analytics] Applying the following properties on tracker: "{"events":"event10","linkTrackVars":"events,channel,server","linkTrackEvents":"event10,event8,event7,"}".

 

Secondly, when i look at my data in workspace, its not showing data for the scroll events.

 

i'm not sure what i'm doing wrong here.  Ideally, at the very least i want to look at a given page and see how many scroll events for a particular depth has occurred.  Is it the rule order in Launch?  Is it the action or, eg Set Variables, Send Beacon, Clear Variables/?

 

Please help!

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 Brian_Johnson_

@angeldee77 - I think you have a couple of things going on here:

  • The extra events may be coming from previous calls that fired on the current page. If you're not doing a clearVariables action before you begin populating the variables for your scroll depth tracking (or other tracking calls, for that matter), you may want to do that. Otherwise, you'll likely see unexpected variables/events on your calls.
  • The "Page" dimension, isn't much use on s.tl() calls, which is what I'm assuming you're firing here. To prove this out, I recommend doing two things: 
    1. Make sure the pageName is included on the scroll depth tracking calls. (From what you shared, it doesn't look like it's set on the tracker.)
    2. Implement another variable (either prop or an eVar with hit expiration) to which you also pass the pageName and make sure it is included on all calls. Use this variable for your reporting.

 

1 reply

Brian_Johnson_
Brian_Johnson_Accepted solution
Level 8
November 4, 2020

@angeldee77 - I think you have a couple of things going on here:

  • The extra events may be coming from previous calls that fired on the current page. If you're not doing a clearVariables action before you begin populating the variables for your scroll depth tracking (or other tracking calls, for that matter), you may want to do that. Otherwise, you'll likely see unexpected variables/events on your calls.
  • The "Page" dimension, isn't much use on s.tl() calls, which is what I'm assuming you're firing here. To prove this out, I recommend doing two things: 
    1. Make sure the pageName is included on the scroll depth tracking calls. (From what you shared, it doesn't look like it's set on the tracker.)
    2. Implement another variable (either prop or an eVar with hit expiration) to which you also pass the pageName and make sure it is included on all calls. Use this variable for your reporting.

 

    AngelDee77
    AngelDee77Author
    Level 4
    November 4, 2020
    Thanks i'll try this out. i did think of having a custom page prop to test. But you are right there are a few separate issues - just trying to figure them out.
    Terms & ConditionsAccessibility statement

    Loading footer...