Engagement/Analytics/Webtrends/Tracking: Difference between revisions

No edit summary
Line 25: Line 25:
Please note the structure of the dcsMultiTrack function call:<br>dcsMultiTtrack('Name1', 'Value1', 'Name2', 'Value2', ... , 'NameN', 'ValueN')&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; <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')&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; <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 = 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 </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 = 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 </ul>
<font color="orange">
<b>CRITICAL</b>:  When creating a scenario analysis please consider that each scenario analysis represents a unique set of steps that ultimately result in a conversion.  For example, there are several unique pathways a user can follow to download Firefox.  Each of these should be considered a separate scenario analysis and tagged accordingly.  Re-using scenario analysis names (WT.si_n) across multiple scenario analyses will result in incorrect data and inaccurate reports. 
In cases where the conversion action is not unique (e.g. downloading Firefox) it is still necessary to identify each pathway uniquely to our system.  This can be accomplished by assigning multiple values to both WT.si_n and WT.si_x using a semi-colon as the delimiter.  For example on the Firefox download 'Thank You' page (the loading of this page is considered the conversion point) you can set the following META tags:
<META name='WT.si_n', content='download_firefox_A; download_firefox_B'><br>
<META name='WT.si_x', content='2;2'>
<b>NOTE: </b>The number of semi-colon delimited values for both WT.si_n and WT.si_x must always match.
</font>


<br>2.&nbsp; Another type of reporting that requires the use of dcsMultiTrack is campaign tracking.&nbsp; Campaign tracking is also usually a 2-step process.&nbsp; Typically, a banner ad exists on an external site that 'lands' on Mozilla.org.&nbsp; 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.&nbsp; The landing page usually presents an action like downloading Firefox.&nbsp; 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.&nbsp; Another type of reporting that requires the use of dcsMultiTrack is campaign tracking.&nbsp; Campaign tracking is also usually a 2-step process.&nbsp; Typically, a banner ad exists on an external site that 'lands' on Mozilla.org.&nbsp; 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.&nbsp; The landing page usually presents an action like downloading Firefox.&nbsp; 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.  
165

edits