165
edits
Engagement/Analytics/Webtrends/Tracking: Difference between revisions
Engagement/Analytics/Webtrends/Tracking (view source)
Revision as of 19:30, 19 March 2012
, 19 March 2012→How To Track Product Downloads
| (5 intermediate revisions by the same user not shown) | |||
| Line 60: | Line 60: | ||
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). | ||
To track the loading landing please add the following meta tag to the header of your page that contains the download link: | To track the loading landing please add the following meta tag to the header of your page that contains the download link (Note: If multiple products are available for download please use a semi-colon delimited list): | ||
<code><meta name="WT.z_pdp" content=" | <code><meta name="WT.z_pdp" content="<see below>"> </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', | <code> dcsMultiTrack('DCS.dcssip',document.location.host,<br> 'DCS.dcsuri',document.location.pathname,<br> 'WT.ti',document.title,<br> 'WT.dl',99,<br> 'WT.z_convert','<see below>') </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. | 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. | ||
| Line 202: | Line 202: | ||
== Incorporating Analytics into the Software Development Pipeline == | == Incorporating Analytics into the Software Development Pipeline == | ||
Prior to deploying site modifications please have a | Prior to deploying site modifications please have a designated Webtrends analyst provide verification that all necessary analytics tags are in place and properly configured. The hope is to minimize the introduction of human error and thus the disruption of data collection. This could be as simple as including the desginated Webtrends analyst on the Bugzilla bug and requiring their sign-off as part of the QA process. | ||
Note: Inadverdent placement or misconfiguration of analytics tags can have a significant impact on both data collection and historical accuracy of data. | Note: Inadverdent placement or misconfiguration of analytics tags can have a significant impact on both data collection and historical accuracy of data. | ||