Market Ruler HelpDifference between revisions of "Unknown actions handling"
m |
(updating code to 2023) |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | {{release-1.9.10}} | ||
| + | |||
ConversionRuler supports the ability to create conversion actions directly from JavaScript code, simply by submitting an action from a page on your site. This can often simplify site configuration and facilitate simpler migration to new types of action, by avoiding the need to require sites to register an action's code name prior to its use. | ConversionRuler supports the ability to create conversion actions directly from JavaScript code, simply by submitting an action from a page on your site. This can often simplify site configuration and facilitate simpler migration to new types of action, by avoiding the need to require sites to register an action's code name prior to its use. | ||
| − | For new sites after | + | For new sites after this release, this option is, by default, enabled for all new sites added to ConversionRuler. For all sites created prior to the release date this setting is, by default, '''off.''' |
When this option is checked, it means you wish ConversionRuler to create a conversion action automatically when it encounters one on the site. | When this option is checked, it means you wish ConversionRuler to create a conversion action automatically when it encounters one on the site. | ||
| − | == How do I submit a conversion action like this? | + | == How do I submit a conversion action like this? == |
Simply pass a <span class="code">string</span> parameter to ConversionRuler from the [[__CR.track]] call, like so: | Simply pass a <span class="code">string</span> parameter to ConversionRuler from the [[__CR.track]] call, like so: | ||
<script> | <script> | ||
| − | + | (function (w, q) { | |
| + | (w[q] = w[q] || []).push(function (cr) { | ||
| + | cr.track("action-name"); | ||
| + | }); | ||
| + | })(window, '_crq'); | ||
</script> | </script> | ||
| − | When this option is enabled, the above code will create an action with '''Code''' "''action-name''" the first time the action is encountered. Every subsequent time the action is encountered, it will use the existing conversion action previously created with the same '''Code''' name. | + | When this option is enabled, the above code will create an action with '''Code''' "''action-name''" the first time the action is encountered. Whether this action is initially visible upon creation is related to the [[Unknown action visible]] setting. Every subsequent time the action is encountered, it will use the existing conversion action previously created with the same '''Code''' name. |
== Why would I want to enable this option? == | == Why would I want to enable this option? == | ||
| Line 37: | Line 43: | ||
* [[Unknown action visible]] | * [[Unknown action visible]] | ||
* [[Conversion Action Automatic Registration]] | * [[Conversion Action Automatic Registration]] | ||
| + | * [[Conversion action list]] | ||
[[Category:ConversionRuler]] | [[Category:ConversionRuler]] | ||
[[Category:ConversionRuler Features]] | [[Category:ConversionRuler Features]] | ||
[[Category:ConversionRuler Site Settings]] | [[Category:ConversionRuler Site Settings]] | ||
Latest revision as of 21:15, 10 December 2023
This feature is only available in release 1.9.10, released October 2016.
ConversionRuler supports the ability to create conversion actions directly from JavaScript code, simply by submitting an action from a page on your site. This can often simplify site configuration and facilitate simpler migration to new types of action, by avoiding the need to require sites to register an action's code name prior to its use.
For new sites after this release, this option is, by default, enabled for all new sites added to ConversionRuler. For all sites created prior to the release date this setting is, by default, off.
When this option is checked, it means you wish ConversionRuler to create a conversion action automatically when it encounters one on the site.
Contents
How do I submit a conversion action like this?
Simply pass a string parameter to ConversionRuler from the __CR.track call, like so:
<script>
(function (w, q) {
(w[q] = w[q] || []).push(function (cr) {
cr.track("action-name");
});
})(window, '_crq');
</script>
When this option is enabled, the above code will create an action with Code "action-name" the first time the action is encountered. Whether this action is initially visible upon creation is related to the Unknown action visible setting. Every subsequent time the action is encountered, it will use the existing conversion action previously created with the same Code name.
Why would I want to enable this option?
- To determine if any actions are misconfigured, are duplicates, or are misspelled
- You would want to enable this option if you have complete control over your site and wish to be able to add actions which are dynamically generated by your site itself, or
- Your sites actions change regularly over time and will allow your developer to define conversion actions directly in the JavaScript code (simplify management of conversion actions), or
- You are first setting up your site and wish to avoid having to come to ConversionRuler to add new actions to your site's configuration
In short, what this means is that any conversion action submitted to your site will be automatically added to the Conversion action list the first time it is encountered. The distinguishing factor for a conversion action is its Code name which must be unique within your site.
Why would I want to disable this option?
A few reasons you would want to disable this option:
- Your site conversion actions are correctly configured and there is no need for it
- Your site is generating a lot of unique conversion actions due to a misconfiguration or other problem with the site setup
- Someone is attempting to corrupt your data by submitting a lot of unique, junk actions to ConversionRuler
- Your site generates more than 500 unique conversion actions at any time