Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>2 options, both using onclick :</p> <p>(1) Create a <a href="http://code.google.com/apis/analytics/docs/tracking/asyncMigrationExamples.html#VirtualPageviews" rel="nofollow">virtual Pageview</a> (not recommended) :</p> <blockquote> <pre><code>&lt;a href="http://www.example.com/downloads/PC.exe" onClick="_gaq.push(['_trackPageview', '/downloads/PC.exe');"&gt; PC Download &lt;/a&gt; </code></pre> </blockquote> <p>(2) Use <a href="http://code.google.com/apis/analytics/docs/tracking/eventTrackerGuide.html" rel="nofollow">Event Tracking</a> (recommended):</p> <blockquote> <pre><code>&lt;a href="http://www.example.com/downloads/PC.exe" onClick="_gaq.push(['_trackEvent', 'Category', 'Download - Pc.exe','Label', optional_value]);"&gt;Play&lt;/a&gt; </code></pre> </blockquote> <p>Google Analytics recommends the latter, but there are pros and cons for both methods :</p> <ul> <li>Using Virtual PageViews will increase the number of page views and distort metrics like Pages/Visits, Bounce Rate, and related metrics. By contrast, Events are tracked separately, but also count towards Bounce Rate (a Visit consisting of only 1 page and a download will not be considered a Bounce)</li> <li>Event Tracking is more flexible, as you can choose a Category, Action, Label and a Value for the Event, and view them independently from Pages. However, that means you need to think carefully about how you want to use the data model. </li> <li>Event Tracking has the following default metrics : Total Events, Unique Events, Event Value and Average Value.</li> <li>Pages have the following default metrics : Pageviews, Unique Pageviews, Avg. Time on Page, Bounce Rate, % Exit.</li> <li>An interesting 'bug' is that filters applied to URLs/hostnames will not filter out Events. In fact, there is no way to filter out Events - they will show up in all Profiles. Problematic if you use Profile filtering a lot.</li> </ul> <p>Best way to go is to test both options and make up your mind after you see the data.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload