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
No edit summary |
|||
| (22 intermediate revisions by the same user not shown) | |||
| Line 19: | Line 19: | ||
In order to capture the click event, please apply the following dcsMultiTrack call to the onClick event handler of the associated link: | In order to capture the click event, please apply the following dcsMultiTrack call to the onClick event handler of the associated link: | ||
<code> dcsMultiTrack('DCS.dcssip', 'www.mozilla.org',<br> 'DCS.dcsuri', '/en-US/download',<br> 'WT.ti', 'Link: Download Firefox',<br> 'WT.dl', | <code> dcsMultiTrack('DCS.dcssip', 'www.mozilla.org',<br> 'DCS.dcsuri', '/en-US/download',<br> 'WT.ti', 'Link: Download Firefox',<br> 'WT.dl', 99,<br> 'WT.si_n', 'Download Firefox',<br> 'WT.si_x', '2') </code> | ||
Please note the structure of the dcsMultiTrack function call:<br>dcsMultiTtrack('Name1', 'Value1', 'Name2', 'Value2', ... , 'NameN', 'ValueN') <br> <br>Here is a short description of the above parameters: <ul> | Please note the structure of the dcsMultiTrack function call:<br>dcsMultiTtrack('Name1', 'Value1', 'Name2', 'Value2', ... , 'NameN', 'ValueN') <br> <br>Here is a short description of the above parameters: <ul> | ||
| Line 40: | Line 40: | ||
In order to capture the download click event we apply the following dcsMultiTrack call to the onClick event handler of the associated link: | In order to capture the download click event we apply the following dcsMultiTrack call to the onClick event handler of the associated link: | ||
<code> dcsMultiTrack('DCS.dcssip', 'www.mozilla.org',<br> 'DCS.dcsuri', '/en-US/download',<br> 'WT.ti', 'Link: Download Firefox',<br> 'WT.z_convert', 'download_firefox',<br> 'WT.dl', | <code> dcsMultiTrack('DCS.dcssip', 'www.mozilla.org',<br> 'DCS.dcsuri', '/en-US/download',<br> 'WT.ti', 'Link: Download Firefox',<br> 'WT.z_convert', 'download_firefox',<br> 'WT.dl', 99)<br></code> | ||
<br>Notice that this may seem redundant because we already implemented a dcsMultiTrack call to track the download click associated with the Scenario Analysis tracking. In fact, it is both redundant and incorrect to make two dcsMultiTrack calls to track the same behavior. So in this case, we can combine the dcsMultiTrack call into one: | <br>Notice that this may seem redundant because we already implemented a dcsMultiTrack call to track the download click associated with the Scenario Analysis tracking. In fact, it is both redundant and incorrect to make two dcsMultiTrack calls to track the same behavior. So in this case, we can combine the dcsMultiTrack call into one: | ||
<code> dcsMultiTrack('DCS.dcssip', 'www.mozilla.org',<br> 'DCS.dcsuri', '/en-US/download',<br> 'WT.ti', 'Link: Download Firefox',<br> <font color="red">''''WT.z_convert', 'download_firefox','''</font><br> 'WT.dl', | <code> dcsMultiTrack('DCS.dcssip', 'www.mozilla.org',<br> 'DCS.dcsuri', '/en-US/download',<br> 'WT.ti', 'Link: Download Firefox',<br> <font color="red">''''WT.z_convert', 'download_firefox','''</font><br> 'WT.dl', 99,<br> <font color="green">''''WT.si_n', 'Download Firefox','''</font><br> <font color="green">''''WT.si_x', '2''''</font>)<br></code> | ||
<br>This last call will provide Webtrends with enough data to create both a Scenario Analysis report AND a Campaign Tracking report. Once this data is captured within the Webtrends logfile, custom reports can be created in the OnDemand environment. <br> | <br>This last call will provide Webtrends with enough data to create both a Scenario Analysis report AND a Campaign Tracking report. Once this data is captured within the Webtrends logfile, custom reports can be created in the OnDemand environment. <br> | ||
| Line 55: | Line 55: | ||
== 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 issues (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). | |||
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="<see below>"> </code> | |||
then in the onclick event handler of the download button please add the following dcsMultiTrack call: | |||
<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. | |||
Here is a list of products that we're currently tracking: <br> | |||
{| | |||
!Name!!WT.z_pdp!!WT.z_convert | |||
|- | |||
|Firefox||firefox||downloadfirefox | |||
|- | |||
|Firefox for Android||firefox_android||Get Firefox for Android | |||
|- | |||
|Firefox Beta||firefox_beta||Firefox Beta | |||
|- | |||
|Firefox Mobile Beta||firefox_mobile_beta||Firefox Beta for Mobile | |||
|- | |||
|Firefox Aurora||firefox_aurora||Firefox Aurora | |||
|- | |||
|Firefox Mobile Aurora||firefox_mobile_aurora||Firefox Aurora for Mobile | |||
|} | |||
== Video Tracking: How to Tag It == | == Video Tracking: How to Tag It == | ||
| Line 170: | Line 200: | ||
In any event, once the report is created add it to the relevant profiles and let them analyze. | In any event, once the report is created add it to the relevant profiles and let them analyze. | ||
== Incorporating Analytics into the Software Development Pipeline == | |||
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. | |||
== Debugging: Why Isn't My Custom Report Populating??? == | == Debugging: Why Isn't My Custom Report Populating??? == | ||