165
edits
Engagement/Analytics/Webtrends/Tracking: Difference between revisions
Jump to navigation
Jump to search
Engagement/Analytics/Webtrends/Tracking (view source)
Revision as of 17:40, 9 September 2011
, 9 September 2011no edit summary
No edit summary |
|||
| Line 12: | Line 12: | ||
} | } | ||
</script> | </script> | ||
| Line 26: | Line 28: | ||
In order to capture this behavior within Webtrends you would apply the following tags as specified below: | In order to capture this behavior within Webtrends you would apply the following tags as specified below: | ||
In the page header please apply the following META tags (it is these tags that specify the above-mentioned 'impression'): | In the page header please apply the following META tags (it is these tags that specify the above-mentioned 'impression'): | ||
<code><META name="WT.si_n" content="Download Firefox" /><br><META name="WT.si_x" content="1" /> </code> | <code><META name="WT.si_n" content="Download Firefox" /><br><META name="WT.si_x" content="1" /> </code> | ||
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', 1,<br> 'WT.si_n', 'Download Firefox',<br> 'WT.si_x', '2') </code> | <code> dcsMultiTrack('DCS.dcssip', 'www.mozilla.org',<br> 'DCS.dcsuri', '/en-US/download',<br> 'WT.ti', 'Link: Download Firefox',<br> 'WT.dl', 1,<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: | 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: | ||
<br>DCS.dcssip - the domain of the page you wish to track<br>DCS.dcsuri - the uri of the page you wish to track<br>WT.ti - The link title<br>WT.dl - a parameter that specifies a given action - for dcsMultiTrack clicks we use 1<br>WT.si_n - the name of the associated 'scenario' you are tracking<br>WT.si_x = the step of the associated 'scenario' you are tracking -note for the impression this value is equal to 1 and for the click it is equal to 2 | |||
<br>2. Another type of reporting that requires the use of dcsMultiTrack is campaign tracking. Campaign tracking is also usually a 2-step process. Typically, a banner ad exists on an external site that 'lands' on Mozilla.org. This banner ad is identified by a custom Webtrends parameter called WT.mc_id; it is included as a query parameter on the banner link. The landing page usually presents an action like downloading Firefox. The goal is to determine the effectiveness of a campaign by identifying how many downloads originated from users that clicked the banner ad -or in other words, how many downloads can be 'attributed' to the campaign effort. | <br>2. Another type of reporting that requires the use of dcsMultiTrack is campaign tracking. Campaign tracking is also usually a 2-step process. Typically, a banner ad exists on an external site that 'lands' on Mozilla.org. This banner ad is identified by a custom Webtrends parameter called WT.mc_id; it is included as a query parameter on the banner link. The landing page usually presents an action like downloading Firefox. The goal is to determine the effectiveness of a campaign by identifying how many downloads originated from users that clicked the banner ad -or in other words, how many downloads can be 'attributed' to the campaign effort. | ||
| Line 42: | Line 45: | ||
<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', 1)<br></code> <br>Notice that this may seem redundant because we already implemented a dcsMultiTrack call on 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> 'WT.z_convert', 'download_firefox',<br> 'WT.dl', 1)<br></code> <br>Notice that this may seem redundant because we already implemented a dcsMultiTrack call on 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"> | <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', 1,<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. This will be the topic of the next Wiki entry.<br> | ||
== DCS Tracking - How to Create a Report == | == DCS Tracking - How to Create a Report == | ||