Domains

In order to start running Campaigns, domains must be created. Domains are also referenced in Messaging, Insights, and Merchandising.

Domains define the location where a Campaign can run, the default currency (in cases where it is missing in tracking) and how languages are mapped from the domain for use in Offers and Widgets.

Creating Domains

When creating a domain, the only required field is the domain name. This domain name must be a valid root domain. For example, "mysite.com" is valid, but "shop.mysite.com" is not.

Once a domain is created, clicking the domain name in the list will bring up a sheet for editing details. You cannot change the domain once it has been created, but you can edit its options.

Domain Options

Default Currency

If no currency is set when tracking a page view this is the currency that is assumed.

Override Session

If Override Session is set, the system will use the default currency as the domain's currency and ignore any currency on the session. This setting is primarily used in the Session Viewer to format a session's currency values.

Default Language

Sets a default language to use. If no default language is set the user's browser language will be used.

The selectable languages are defined in the account preferences. See Translation Languages.

Language Regex

A regular expression (regex) is a way to define a pattern in a string. We suggest you consult with a developer, or contact Fanplayr if you are not already familiar with how to use them. A great tool to test regular expressions is Regexr.

If the language regex is set, the full URL of the currently tracked page is matched and the first capture group is then used to define a language / locale for use in Offers and Widgets. Note: the string will be lowercased, and hyphens converted to underscores in our system. See Translation Languages for a list of supported languages / locales.

See Language Hierarchy below for more details on how the current Session language is chosen.

Language Hierarchy

The user's language in a Session is determined at runtime, for each tracking event, using the following logic hierarchy. The first valid language found is used.

  1. Language set on the integration

  2. Domain language regex is set and matches the URL

  3. Domain default language (if set)

  4. User's browser language

Last updated