165
edits
Engagement/Analytics/Webtrends/Tracking: Difference between revisions
Jump to navigation
Jump to search
Engagement/Analytics/Webtrends/Tracking (view source)
Revision as of 23:43, 14 September 2011
, 14 September 2011→DCS Tracking Code
| 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', 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: <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 | 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 | ||
| Line 27: | Line 27: | ||
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', 1)<br></code> | <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: | <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">''''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. br> | <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. br> | |||
== DCS Tracking - How to Create a Report == | == DCS Tracking - How to Create a Report == | ||