Expand my Community achievements bar.

Join us at Adobe Summit 2024 for the Coffee Break Q&A Live series, a unique opportunity to network with and learn from expert users, the Adobe product team, and Adobe partners in a small group, 30 minute AMA conversations.
SOLVED

Analytics tracking

Avatar

Level 2

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?

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

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...

View solution in original post

3 Replies

Avatar

Community Advisor

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?

Avatar

Level 2

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.

Avatar

Correct answer by
Community Advisor

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...