Yes, in version two all you would need to do is to change whatever you
decided to call your virtual pageviews.

But

What I meant by "route" was an assumption that the pdf was available to
download from a known set of multiple pages.

I was just suggesting it as a way of knowing which page the pdf was
dowloaded from

eg a product is treated as available in several categories

category1/the-product-page/download-spec-sheet.pdf
category2/the-product-page/download-spec-sheet.pdf

If that's not the situation, my first idea is more relevant.

Tim

2009/11/20 New High Score <new_high_score@...>

>
>
> Tim,
>
> That second tip of yours sounds interesting. Does that mean that all I need
> to do is tag the buttons differently, like you said, and nothing else? I
> must try this out on a website.
>
> How would I know the 'route' of getting to the pdf while tagging it?
>
> Or did I not 'get it' at all?
>
> NHS
>
> ________________________________
> From: Tim Leighton-Boyce <tim.lboyce@... <tim.lboyce%40gmail.com>>
> To: webanalytics@yahoogroups.com <webanalytics%40yahoogroups.com>
> Sent: Thu, November 19, 2009 6:11:25 PM
>
> Subject: Re: [webanalytics] G.A. custom event tracking for PDF - examples?
>
> Two further thoughts:
>
> 1) If the site is so dynamic that there is no real structure to the path to
> the download, then set up the virtual pageview for the download as a goal.
> Then use the GA Reverse Goal Path to report on the last 3 pages leading to
> the goal. (One of the few uses for this report, instead of a funnel report,
> is when you have no idea what the routes to the goal might be and want
> something which will report on whatever they are.
>
> 2) Structure the virtual page view in a counter-intuitive way. Have the pdf
> id as a virtual directory, followed by virtual directories "leading" to it
> eg
>
> /pdf1/route1/ subroute1
> /pdf1/route1/ subroute2
> /pdf1/route2/ etc
> /pdf2/route3/ subroute1
> /pdf2/route3/ whatever
>
> With that kind of structure the GA Content Drilldown report could start to
> sing for you, with the rolled-up totals at the top level, followed by a
> series of drill-downs to allow you to report on the relative use of the
> different routes.
>
> Tim
>
> that
>
> [Non-text portions of this message have been removed]
>
>
>


[Non-text portions of this message have been removed]