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:32, 28 December 2011
, 28 December 2011→Custom Conversion Events: DCS Tracking Code
| Line 24: | Line 24: | ||
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> | ||
<li>DCS.dcssip - the domain of the page you wish to track<li>DCS.dcsuri - the uri of the page you wish to track<li>WT.ti - the link title<li>WT.dl - a parameter that specifies a given action - for dcsMultiTrack clicks we use 1<li>WT.si_n - the name of the associated 'scenario' you are tracking<li>WT.si_x | <li>DCS.dcssip - the domain of the page you wish to track<li>DCS.dcsuri - the uri of the page you wish to track<li>WT.ti - the link title<li>WT.dl - a parameter that specifies a given action - for dcsMultiTrack clicks we use 1<li>WT.si_n - the name of the associated 'scenario' you are tracking<li>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 (or other conversion point) it is equal to 2 </ul> | ||