Engagement/Analytics/Webtrends/Tracking: Difference between revisions

Engagement/Analytics/Webtrends/Tracking (view source)

No change in size , 28 December 2011

165

edits

@@ Line 30: / Line 30: @@
 <b>CRITICAL</b>:  When creating a scenario analysis please consider that it 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:
+In cases where the conversion action is not unique (e.g. downloading Firefox) it is still necessary to uniquely identify each pathway 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>