Deploy Preconfigured Personalization Attribution Intelligence Data

Important You can deploy attribution intelligence data in any data space running the Personalization app. The deployment process automatically checks whether you have already deployed attribution data to the selected data space.

Deploying Personalization attribution intelligence data installs and configures preconfigured attribution components and configurations in the data space that you select using the identity resolution ruleset you choose. This data includes necessary data lake and data model objects, and two preconfigured first touch and last touch attribution models.

To ensure unique object naming, Personalization uses these naming conventions when deploying preconfigured components:

• Installed objects use a naming convention of {dataspacePrefix}_{irSuffix}_{objectBaseName} for data lake objects (DLOs), and {dataspacePrefix}_{irSuffix}_{objectBaseName}__dlm for data model objects (DMOs).
• The default dataspace doesn’t have a prefix, so selecting this dataspace doesn’t add a prefix or underscore to the beginning of the object name. Selecting any other dataspace adds a prefix and underscore to the object name.
• When deploying attribution intelligence, you must choose a data space. However, selecting an identity resolution ruleset is optional. If no identity resolution ruleset is selected, no {irSuffix} value is added.
• If you select an identity resolution ruleset with an empty suffix, Personalization prepends the value e_s_ as the {irSuffix} value to indicate the empty suffix.
• API names can’t start with a number. If the identity resolution ruleset starts with a number and the default dataspace is used (meaning that no data space prefix is included), Personalization adds n_s_{irSuffix} as the prefix.

To deploy preconfigured Personalization attribution intelligence data: