Named Actions - Revision history

Admin at 20:50, 14 October 2016

2016-10-14T20:50:27Z

Admin at 15:28, 26 February 2016

2016-02-26T15:28:35Z

Admin at 15:24, 15 February 2013

2013-02-15T15:24:29Z

Admin at 06:14, 15 February 2013

2013-02-15T06:14:28Z

Admin at 06:09, 15 February 2013

2013-02-15T06:09:36Z

Admin at 03:47, 15 February 2013

2013-02-15T03:47:59Z

Admin: Created page with 'As of February 2013, you can use action names instead of numbers for your actions in ConversionRuler. The usage is almost identical in ConversionRuler, except that you must pass …'

2013-02-15T03:45:21Z

Created page with 'As of February 2013, you can use action names instead of numbers for your actions in ConversionRuler. The usage is almost identical in ConversionRuler, except that you must pass …'

New page

As of February 2013, you can use action names instead of numbers for your actions in ConversionRuler. The usage is almost identical in ConversionRuler, except that you must pass action codes in quotes when passed to ConversionRuler. It simply makes it easier to associate the actions with their meaning in the JavaScript code.

So, for example:

<script type="text/javascript">
cr_track('order', '$129.99', '#571298120');
</script>

Is far simpler to understand than:

<script type="text/javascript">
cr_track('3', '$129.99', '#571298120');
</script>

You '''must''' quote actions passed to [[cr_track]] (unless you are actually passing a variable - for advanced [[JavaScript]] marketers.), so,

<script type="text/javascript">
// ERROR DO NOT DO THIS
cr_track(order, '$129.99', '#571298120');
</script>

will produce an error and will not track.

The named actions functionality was rolled out simultaneously with the [[Tracking Queue]] functionality for [[AJAX]] applications. So, an alternate way to use named actions is:

<script type="text/javascript">
_crq.push(['order', '$129.99', '#571298120']);
</script>

[[Category:ConversionRuler]]
[[Category:ConversionRuler Features]]
[[Category:ConversionRuler Tracking]]
[[Category:ConversionRuler JavaScript Functions]]

← Older revision		Revision as of 15:24, 15 February 2013
Line 1:		Line 1:
		+	[[File:ConversionRuler-Action-Edit-Code-By-Name.png\|400px\|right]]
		+
	As of February 2013, you can use action names instead of numbers for your actions in ConversionRuler. The usage is almost identical in ConversionRuler, except that you must pass action codes in quotes when passed to ConversionRuler. It simply makes it easier to associate the actions with their meaning in the JavaScript code.		As of February 2013, you can use action names instead of numbers for your actions in ConversionRuler. The usage is almost identical in ConversionRuler, except that you must pass action codes in quotes when passed to ConversionRuler. It simply makes it easier to associate the actions with their meaning in the JavaScript code.

@@ Line 34: / Line 34: @@
   </script>
-## Before you rename everything
+= Before you rename everything =
 Before you rush out and rename all of your actions, please note that any existing tracking code which uses the old action numbers (e.g. 1,2,3,4, etc.) will suddenly break when you change your actions to use a new name. '''So use action names for new installations''', or for when you know that you no longer need to use an old action.

← Older revision		Revision as of 03:47, 15 February 2013
Line 21:		Line 21:

	will produce an error and will not track.		will produce an error and will not track.
		+
		+	Action names:
		+
		+	* Do not have to match by case to track correctly (so, "Order", "order", and "oRdEr" are considered identical)
		+	* Can have spaces in them, but not at the beginning or end
		+	* Should avoid using quotes, although technically they are allowed (so, "they're leaving" is valid, although we suggest avoiding it for JavaScript syntax errors.)

	The named actions functionality was rolled out simultaneously with the [[Tracking Queue]] functionality for [[AJAX]] applications. So, an alternate way to use named actions is:		The named actions functionality was rolled out simultaneously with the [[Tracking Queue]] functionality for [[AJAX]] applications. So, an alternate way to use named actions is:

@@ Line 15: / Line 15: @@
   </script>
-You '''must''' quote actions passed to [[cr_track]] (unless you are actually passing a variable - for advanced [[JavaScript]] marketers.), so,
+You '''must''' quote actions passed to [[__CR.track]] (unless you are actually passing a variable - for advanced [[JavaScript]] marketers.), so,
   <script type="text/javascript">

@@ Line 6: / Line 6: @@
   <script type="text/javascript">
-     cr_track('order', '$129.99', '#571298120');
+     __CR.track('order', '$129.99', '#571298120');
   </script>
@@ Line 12: / Line 12: @@
   <script type="text/javascript">
-     cr_track('3', '$129.99', '#571298120');
+     __CR.track('3', '$129.99', '#571298120');
   </script>
@@ Line 19: / Line 19: @@
   <script type="text/javascript">
      // ERROR DO NOT DO THIS
-     cr_track(order, '$129.99', '#571298120');
+     __CR.track(order, '$129.99', '#571298120');
   </script>

@@ Line 33: / Line 33: @@
      _crq.push(['order', '$129.99', '#571298120']);
   </script>
 [[Category:ConversionRuler]]