Predictive CDPMarketing Auto & LoyaltyMobile Wallets

Domain and Business Unit management

How are handled projects with several countries, languages, and currencies in Splio Predictive CDP.

Suggest Edits

Definitions

  • Tenant: An instance of SaaS software for a specific client.
  • Domain: A tenant for Splio Predictive CDP platform (handling CDP, Predictive AI, and Copilot offers).
  • Business Unit: A specific and separated part of a Domain, for a specific country, language, or business unit. It is useful to have a Domain with several Business Units when your company's organization implies that you need to separate users, data, audiences, and campaigns from several countries, for security or data protection reasons.
  • Universe: A tenant for Splio Marketing Automation & Loyalty platform
  • Organization: A tenant for Splio Mobile Wallets Platform

CDP + Marketing Automation: standard case

If you are using both Splio CDP and Marketing Automation, if you are operating in one country, with one language and one currency, you only need one Splio CDP domain and one Marketing Automation universe. If this is the case, this article is not relevant to you.

CDP + Marketing Automation: multiple Business Units case

If you need to separate users and data between several CDP Business Units, then the implementation rule is the following: you need to have one Marketing Automation universe for each Business Unit in the CDP.

This way, your users will have access to only the data, filters, designs, and campaigns linked to their activity in Marketing Automation, as well as in Splio CDP.

⚠️ Not following this rule will make your implementation incompatible with the future features of our products.

Multiple Business Units consequences

This part covers only the data aspect of the multiple Business Unit cases. To see what this kind of configuration looks like in the CDP, please take a look at our user-oriented guide:

Data specificities

  • Currency: The same default currency should be applied to all Business Units and all Marketing Automation universes.
  • Dates: All dates need to be in the UTC format because operating in many countries can mean operating over many time zones.
  • Languages: Languages are defined in a contact system field in Marketing Automation, and asset translations need to be defined in custom fields of the corresponding tables. These translations can be relevant for product descriptions, and product categories.

Deduplication

Identity resolution

With a multiple Business Unit setup, identity resolution can be operated for each BU.

If you want to know more about the identity resolution feature, please read our dedicated functional guide:

This means that N contacts belonging to the same BU can end up being deduplicated and merged into a single unique contact.

⚠️ But contacts belonging to different Business Units will never be merged together

In this case, identity resolution can not be operated across Business Units, because it would end up merging contacts of different Business Units, which is incompatible with the constraint that, in this mode, a contact belongs to one Business Unit only.

Unified user profile resolution

The profile resolution configuration is the same as when you have only one Business Unit.

ℹ️ All user profile resolution rules have to be the same for all Business Units.

Pre-computed attributes in Custom Audience Filters

Since the user profile is resolved inside each BU, all pre-computed attributes will be naturally scoped on distinct BUs. For example, the “total revenue” of a customer will sum only the revenue of the BU, even if the contact has a “similar brother” in another Business Unit.

ℹ️ The pre-computed attribute set needs to be the same for all Business Units.

This means that if a specific pre-computed attribute is required for a given Business Unit, it will be calculated for all Business Units.

If you want to see the full list of our pre-computed attributes, please read the dedicated functional guide:

Updated 6 months ago