Difference between revisions of "Link domains"
m |
|||
Line 14: | Line 14: | ||
* example.com | * example.com | ||
* example.secure.force.com | * example.secure.force.com | ||
+ | * '''offers.myexample.org''' | ||
+ | * '''subdomain.example.com''' | ||
+ | * '''another.example.secure.force.com''' | ||
Any links on your site which connect to pages on these domains will be automatically updated to pass the [[User ID]] to the target domain. | Any links on your site which connect to pages on these domains will be automatically updated to pass the [[User ID]] to the target domain. |
Revision as of 20:05, 12 September 2018
The Link domains setting is applied to a ConversionRuler Site setting and can be used to improve site visitor tracking and consistency.
Each visitor to your web site is assigned a unique User ID which is used to connect that user to their various Conversion Actions on your site.
By default, the User ID is stored in the browser's cookies, which means it can only be accessed by pages on the same domain or subdomain. To track the same User across domains, you can specify the domains which you would like to track in the Link domains field.
A valid value for this would be something like:
myexample.org,example.com,example.secure.force.com
Which would modify links on all web domains which end with the values:
- myexample.org
- example.com
- example.secure.force.com
- offers.myexample.org
- subdomain.example.com
- another.example.secure.force.com
Any links on your site which connect to pages on these domains will be automatically updated to pass the User ID to the target domain.