Analytics tracking | Community
Skip to main content
N
narayanad670284
Level 2
August 12, 2019
Solved

Analytics tracking

  • August 12, 2019
  • 3 replies
  • 2079 views

We are using adobe analytics for tracking clicks on videos and download attempts. We are able to implement and track the clicks on videos and send the required tags etc.. of the particular video to analytics tool but for the download attempts where the browser redirects happen, we are unable to track and see any data in the adobe analytics tool. I guess the browser redirects are happening before the adobe analytics has a chance to fire, do we need to suppress the re-directs - wait for some time, letting the adobe analytics to fire the event and then allow re-directs?

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 Urs_Boller

if you track the login page, you could try to add a parameter on the redirect, something like ?redirect=source

then on the login page you would know that the user has been redirected by trying to get to the download and track this information somewhere...

3 replies

Urs_Boller
Community Advisor
Urs_BollerCommunity Advisor
Community Advisor
August 12, 2019

normally I don't have any issues to track "download clicks" on a website. is this your case? or do you publish a link somewhere (outside) which takes the user to your website and forwards directly to a download?

N
narayanad670284Author
Level 2
August 12, 2019

We have some assets which are restricted, so attempting to download those assets (Initial Download attempt) will redirect the user to a login page and upon successful login (sso), he will be redirected to our site and if the user clicks accept and download (Final Download attempt), the download starts. we were unable to track the initial download attempts as the user is being redirected to a login page immediately.

Urs_Boller
Community Advisor
Urs_BollerCommunity AdvisorAccepted solution
Community Advisor
August 12, 2019

if you track the login page, you could try to add a parameter on the redirect, something like ?redirect=source

then on the login page you would know that the user has been redirected by trying to get to the download and track this information somewhere...

Terms & ConditionsAccessibility statement

Loading footer...