۶Ƶ

[Beta]{class="badge informative"}

Use ۶Ƶ Experience Platform data for personalization aep-data

AVAILABILITY
This feature is currently available to all customers as a public beta.
In order to use this capability, you must first accept beta terms for your organization that display when adding the new “datasetLookup” helper functions in the personalization editor.

Journey Optimizer allows you to leverage data from ۶Ƶ Experience Platform in the personalization editor to personalize your content. To do this, datasets needed for lookup personalization must first be enabled through an API call as described below. Once done, you can use their data to personalize your content into Journey Optimizer.

Beta restrictions and guidelines guidelines

Before you begin, please review the following restrictions and guidelines:

  • Supported channels: For now, this capability is only available for usage within email, SMS and direct mail channels.
  • Fragments: Dataset lookup personalization cannot be placed within expression or visual fragments at this time.

Decisioning decisioning

The ability to leverage ۶Ƶ Experience Platform datasets in Experience Decisioning ranking formulas and rules is coming soon.

In the meantime, please review the current guardrails outlined below:

  • A decision policy is limited to 3 datasets,
  • A decision rule can use 3 datasets,
  • A ranking formula can use 3 datasets,
  • A decision policy is limited to 1000 record queries.
NOTE
Please contact your account representative if you would like access to this capability

Enable a dataset for data lookup enable

In order to leverage data from your dataset for personalization, you need to use an API call to retrieve its status and enable lookup service. Detailed information are available in this section: Leverage ۶Ƶ Experience Platform datasets in Journey Optimizer

Leverage a dataset for personalization leverage

Once a dataset has been enabled for lookup personalization using an API call, you can use its data to personalize your content into Journey Optimizer.

  1. Open the personalization editor, which is available in every context where you can define personalization such as messages. Learn how to work with the personalization editor

  2. Navigate to the helper functions list and add the datasetLookup helper function to the code pane.

  3. This function provides a predefined syntax to allow you to call fields from your ۶Ƶ Experience Platform datasets. The syntax is as follows:

    code language-none
    
    {{datasetLookup datasetId="datasetId" id="key" result="store" required=false}}
    
    • datasetId is the ID of the dataset you are working with.

    • id is the ID of the source column that should be joined with the primary identity of the look up dataset.

      note note
      NOTE
      The value entered for this field can be either a field ID (profile.packages.packageSKU), a field passed in a journey event (context.journey.events.event_ID.productSKU), or a static value (sku007653). In any case, the system will use the value and lookup into the dataset to check if it matches a key.
      If using a literal string value for the key, keep the text in quotes. Eg: {{datasetLookup datasetId="datasetId" id="SKU1234" result="store" required=false}}. If using an attribute value as a dynamic key, remove the quotes. Eg: {{datasetLookup datasetId="datasetId" id=category.product.SKU result="SKU" required=false}}
    • result is an arbitrary name that you need to provide to reference all the field values you are going to retrieve from the dataset. This value will be used in your code to call each field.

    • required=false: If required is set to TRUE, the message will only be delivered if a matching key is found. If set to false, a matching key is not required and the message can still be delivered. Note that, if set to false, it is recommended that you account for fallback or default values in your message content.

    accordion
    Where to retrieve a dataset ID?

    Dataset IDs can be retrieved in ۶Ƶ Experience Platform user interface. Learn how to work with datasets in the ۶Ƶ Experience Platform documentation.

  4. Adapt the syntax to suit your needs. In this example, we want to retrieve data related to passengers’ flights. The syntax is as follows:

    code language-none
    
    {{datasetLookup datasetId="1234567890abcdtId" id=profile.upcomingFlightId result="flight"}}
    
    • We are working in the dataset whose ID is “1234567890abcdtId”,
    • The field we want to use to make a join with the look up dataset is profile.upcomingFlightId,
    • We want to include all the field values under the “flight” reference.
  5. Once that the syntax to call in the ۶Ƶ Experience Platform dataset has been configured, you can specify which fields you want to retrieve. The syntax is as follows:

    code language-none
    
    {{result.fieldId}}
    
    note note
    NOTE
    When referencing a dataset field, make sure that you match the full field path as defined within the schema.
    • result is the value that you have assigned to the result parameter in the MultiEntity helper function. In this example “flight”.

    • fieldID is the ID of the field you want to retrieve. This ID is visible in ۶Ƶ Experience Platform user interface when browsing the record schema related to your dataset:

      accordion
      Where to retrieve a field ID?

      Fields IDs can be retrieved when previewing a dataset in ۶Ƶ Experience Platform user interface. Learn how to preview datasets in the ۶Ƶ Experience Platform documentation.

    In this example, we want to use information related to the passengers’ boarding time and gate. We therefore add these two lines:

    • {{flight._myorg.booking.boardingTime}}
    • {{flight._myorg.booking.gate}}
  6. Now that your code is ready, you can complete your content as usual, and test it using the Simulate content button to check the personalization. Learn how to preview and test content

recommendation-more-help
91a6d90a-6d61-4a62-bbed-ae105e36a860