But how do you accomplish step 1:
“Work with your developer to treat every file download as if it were a web page on your site such that it is passed to the Pagename variable (s.pagename).”

Do you have to set up an onClick event on every single PDF link? or is that a more efficient way to pass the file name into the s.pagename variable?

Does anybody have a suggestion?

Thanks so much,
rich

I also had the same question as comment #2 earlier by Andreas. I just want to clarify whether your solution offers the ability to measure entries to the site on the document itself? If so, are you wrapping the documents in some code to make manual tracking calls? Our implementation uses the s_code to make the calls so the host page needs to load first. In our case the documents are never entry pages so we cannot measure bounce rate.

Finally, comment #9 by Michael is really useful. We have a lot of content categories on our site and it would it is useful to have category counts for our assets. This also would provide a simple way to drill down to document level reporting.

Thanks for the post.

Rob

I might not have been clear in my previous comment.
I was suggesting adding the downloads measurement to the s.channel. I wasn’t refering to the Pathing being enabled.

Hope this makes more sense.

Michael

I would consider extending this solution to the s.channel variable for sites with various content groups and downloads per each content group (e.g. large B2Bs or electronics companies such as HP, Canon, Dell etc.).

This would give the analyst an aggregate level view of download per content group (with the right naming structure, of course).

Thank you for a great post.

Michael

Adam

A couple of things I want to clarify with your post.

My understanding of file download in Omniture is that it is not like looking at logs. It is merely, a link tracker and takes a count on the links that have been clicked. Wont tell you if the file clicked was downloaded successfully.

So using the s.pagename for pathing reporting, won’t that inflate your data as you would want to assign a unique click value of that action for visitors?

eg// pre/post site usage as per the event/action.