165
edits
Engagement/Analytics/Webtrends/Tracking: Difference between revisions
Engagement/Analytics/Webtrends/Tracking (view source)
Revision as of 16:54, 25 January 2012
, 25 January 2012→How To Track Product Downloads
| Line 56: | Line 56: | ||
== How To Track Product Downloads == | == How To Track Product Downloads == | ||
Product download reports are useful for measuring the effectiveness of product download landing pages. For example you may have a marketing campaign that lands on the Firefox download page but for some reason the number of downloads is low. This could be due to any number of things (e.g. a mis-configured marketing campaign, | Product download reports are useful for measuring the effectiveness of product download landing pages. For example you may have a marketing campaign that lands on the Firefox download page but for some reason the number of downloads is low. This could be due to any number of things (e.g. a mis-configured marketing campaign, the site going down, etc...). A good place to start ruling things out is the landing page itself. Maybe there are several third party advertisements with similar looking download buttons confusing the user, maybe the download button is in a confusing spot, you get the picture. | ||
The best approach here is to let the data speak by adding some custom parameters to the landing pages and then creating a custom report. The metric we will use to measure the effectiveness of the landing page will be conversions (or conversion %). This is the number of product downloads divided by the total number of visits to the associated landing page. To capture this data we will need two parameters, one to track the loading of the landing page (WT.z_pdp, pdp is short for product download page) and the other to track the clicking of the download button (WT.z_convert). | The best approach here is to let the data speak by adding some custom parameters to the landing pages and then creating a custom report. The metric we will use to measure the effectiveness of the landing page will be conversions (or conversion %). This is the number of product downloads divided by the total number of visits to the associated landing page. To capture this data we will need two parameters, one to track the loading of the landing page (WT.z_pdp, pdp is short for product download page) and the other to track the clicking of the download button (WT.z_convert). | ||
| Line 62: | Line 62: | ||
To track the loading landing please add the following meta tag to the header of your page: | To track the loading landing please add the following meta tag to the header of your page: | ||
<meta name="WT.z_pdp" content="my_product_name"> | <code><meta name="WT.z_pdp" content="my_product_name"> </code> | ||
then in the onclick event handler of the download button please add the following dcsMultiTrack call: | then in the onclick event handler of the download button please add the following dcsMultiTrack call: | ||
<code> dcsMultiTrack('DCS.dcssip', 'www.mozilla.org',<br> 'DCS.dcsuri', '/en-US/download',<br> 'WT.ti', 'Link: Download My Product',<br> 'WT.dl', 99,<br> 'WT.z_convert', 'my_product_name') </code> | |||
Once the page and appropriate buttons have been tagged a custom report can be created to track the conversion rate and other metrics. More on that later. | |||
== Video Tracking: How to Tag It == | == Video Tracking: How to Tag It == | ||