The next thing to track is PDF downloads.
Posted: Tue Feb 11, 2025 8:45 am
PDF downloads
Now there's a limitation to this, of course, in that if people Google something and your PDF comes up and then they click on it directly from Google, of course it won't show up in your analytics. It might show up in Search Console, but you won't be able to get it in Analytics. So just keep that in mind. This is when someone clicks on your PDF from a specific page on your website. Again, you're decorating the link to say that if this link has a PDF, I want to get it.
Scroll tracking
Then we also track scroll tracking. Now scroll tracking is bolivia number data when people scroll down the site, you can track and fire an event at 25%, 50%, 75%, and 100% of the way down the page. Now the thing with this is that your mileage is going to vary. You'll probably choose different percentages. By default, in all our containers we put 25%, 50%, 75%, and 100%. Based on the client, we can change that.
An advanced, level-up strategy would be to pick specific elements and then when they enter the viewport, you can fire an event. So let's say, for example, you have a really important call to action and since different devices are different sizes, it will be a different percentage of the way down the page, but you want to see if people have reached that central CTA. Then you'll want to add an event that will indicate whether that CTA was shown in the viewport or not.
Now there's a limitation to this, of course, in that if people Google something and your PDF comes up and then they click on it directly from Google, of course it won't show up in your analytics. It might show up in Search Console, but you won't be able to get it in Analytics. So just keep that in mind. This is when someone clicks on your PDF from a specific page on your website. Again, you're decorating the link to say that if this link has a PDF, I want to get it.
Scroll tracking
Then we also track scroll tracking. Now scroll tracking is bolivia number data when people scroll down the site, you can track and fire an event at 25%, 50%, 75%, and 100% of the way down the page. Now the thing with this is that your mileage is going to vary. You'll probably choose different percentages. By default, in all our containers we put 25%, 50%, 75%, and 100%. Based on the client, we can change that.
An advanced, level-up strategy would be to pick specific elements and then when they enter the viewport, you can fire an event. So let's say, for example, you have a really important call to action and since different devices are different sizes, it will be a different percentage of the way down the page, but you want to see if people have reached that central CTA. Then you'll want to add an event that will indicate whether that CTA was shown in the viewport or not.