Correlating pdf downloads with pages | Community
Skip to main content
jim_klockow
jim_klockow
October 16, 2015
Solved

Correlating pdf downloads with pages

  • October 16, 2015
  • 2 replies
  • 1747 views

I'd like to know from which pages a certain pdf was downloaded, but I can't seem to get at this by breaking down the file downloaded by the page or vice versa. The pageName is passed in the image request. I don't understand why I can't get at this. I hope I'm just being stupid, but please shout out if you know.

Thanks.

    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 AdamGreco

    This old blog post of mine should tell you all you need to know to solve your File Download issue...

    http://adam.webanalyticsdemystified.com/2010/02/08/stop-using-the-file-downloads-report/

    2 replies

    AdamGreco
    AdamGrecoAccepted solution
    Level 4
    October 16, 2015

    This old blog post of mine should tell you all you need to know to solve your File Download issue...

    http://adam.webanalyticsdemystified.com/2010/02/08/stop-using-the-file-downloads-report/

      B
      beau0269
      Level 2
      November 17, 2015

      Hi Adam,

      I'm having trouble following the steps in the blog post and hoping you can help. I'm using DTM and don't quite grasp how to treat a file download as a page name or make the system recognize a file download is taking place. Below, I've outlined the approach I've taken -- however, I may be completely off-target.

      In DTM, I created a "click" event based rule for paths that contain a file extension (doc, docx, pdf, ppt, etc). When this event fires I associate a success event and eVar. My issue is defining the Data Element to record in the eVar...I don't understand how to capture the file name instead of the page name I'm currently on.

       

      Is there a different approach I can take with DTM -- or do you have any suggestions?

       

      Thanks!

      Terms & ConditionsAccessibility statement

      Loading footer...