DocumentationJourney OptimizerJourney Optimizer Guide

Use supplemental identifiers in journeys supplemental-id

Last update: Thu Sep 18 2025 00:00:00 GMT+0000 (Coordinated Universal Time)
  • Applies to:
  • Journey Orchestration

By default, journeys are executed in the context of a profile ID. This means that, as long as the profile is active in a given journey, it won't be able to re-enter another journey. To prevent this, Journey Optimizer allows you to capture a supplemental identifier, such as an order ID, subscription ID, prescription ID, in addition to the profile ID.

In this example, we have added a booking ID as a supplemental identifier.

By doing so, journeys are executed in the context of the profile ID associated to the supplemental identifier (here, the booking ID). One instance of the journey is executed for each iteration of the supplemental identifier. This allows multiple entrances of the same profile ID in journeys if they have made different bookings.

In addition, Journey Optimizer allows you to leverage attributes of the supplemental identifier (e.g., booking number, prescription renewal date, product type) for message customization, ensuring highly relevant communications.

Supplemental identifier example

➡️ Discover this feature in video

Guardrails & limitations guardrails

  • Supported journeys: Supplemental identifiers are supported for event-triggered and Read audience journeys. They are not supported for Audience qualification journeys (i.e., journeys starting with an Audience qualification activity).

  • Concurrent instance limits: Profiles cannot have more than 10 concurrent journey instances.

  • Frequency rules: Each journey instance created from supplemental identifier usage counts towards frequency capping, even if the use of supplement identifiers results in multiple journey instances.

  • Data type and schema structure: The supplemental identifier must be of type string. It can be an independent string attribute or it can be a string attribute within an array of objects. The independent string attribute will result in a single journey instance, whereas the string attribute within an array of objects will result in a unique journey instance per iteration of the object array. String arrays and maps are not supported.

  • Journey reentrance

    Journey reentrance behavior with supplemental identifiers follows the existing reentrance policy:

    • If the journey is non-reentrant, the same profile ID + supplemental ID combination cannot reenter the journey.
    • If the journey is reentrant with a time window, the same profile ID + supplemental ID combination can reenter after the defined time window.

  • Data Use Labelling and Enforcement (DULE) - No DULE validation checks are performed on the supplemental ID. This means that this attribute will not be considered when the journey is looking for data governance policy violations.

  • Downstream events configuration

    If you are using another event downstream in the journey, it must use the same supplemental ID and have the same ID namespace.

  • Read audience journeys

    • Supplemental ID is disabled if you use a business event.
    • Supplemental ID must be a field from the profile (i.e., not an event/context field).
    • For read audience journeys using supplemental IDs, the reading rate of the read audience activity for each journey instance is limited to a maximum of 500 profiles per second.

Exit criteria behavior with supplemental IDs exit-criteria

Precondition: Journey enabled for supplemental ID (via unitary event or read audience activities)

The table below explains the behavior of profiles in a supplemental ID-enabled journey when exit criteria is configured:

Exit criteria configuration
Behavior when exit criteria is met
Based on a non-supplemental ID event
All instances of the corresponding profile in that journey are exited.
Based on a supplemental ID event
Note: Supplemental ID namespace must match that of the initial node.
Only the matching profile + supplemental ID instance is exited.
Based on an audience
All instances of the corresponding profile in that journey are exited.

Add a supplemental identifier and leverage it in a journey add

Event-triggered journey

To use a supplemental identifier in an event-triggered journey, follow these steps:

  1. Mark the attribute as an identifier in the event schema

    1. Access the event schema and locate the attribute you want to use as a supplemental identifier (e.g., booking ID, subscription ID) and mark it as an ID. Learn how to work with schemas

    2. Mark the identifier as an Identity.

      note important
      IMPORTANT
      Make sure you do not mark the attribute as Primary identity.

    3. Select the namespace to associate with the supplemental ID. This must be a non-person identifier namespace.

      After applying the non-person identity namespace to a schema, you must create a new event in order to use the supplemental identifier. Existing entities cannot be refreshed to recognize the new identifier.

  2. Add the supplemental ID to the event

    1. Create or edit the desired event. Learn how to configure a unitary event

    2. In the event configuration screen, check the Use supplemental identifier option.

    3. Use the expression editor to select the attribute you marked as the supplemental ID.

      note note
      NOTE
      Make sure you are using the expression editor in Advanced mode to select the attribute.

    4. After selecting the supplemental ID, the associated namespace is displayed in the event configuration screen as read-only.

  3. Add the event to the journey

    Drag the configured event onto the journey canvas. It will trigger journey entry based on both the profile ID and the supplemental ID.

Read audience journey

To use a supplemental identifier in a Read audience journey, follow these steps:

  1. Mark the attribute as an identifier in the union/profile schema

    1. Access the union/profile schema and locate the attribute you want to use as a supplemental identifier (e.g., booking ID, subscription ID) and mark it as an ID. Learn how to work with schemas

    2. Mark the identifier as an Identity.

      note important
      IMPORTANT
      Make sure you do not mark the attribute as Primary identity.

    3. Select the namespace to associate with the supplemental ID. This must be a non-person identifier namespace.

      After applying the non-person identity namespace to a schema, you must create a new field group in order to use the supplemental identifier. Existing entities cannot be refreshed to recognize the new identifier.

  2. Add and configure a Read audience activity in the journey

    1. Drag a Read audience activity in your journey.

    2. In the activity properties pane, toggle on the Use supplemental identifier option.

    3. In the Supplement identifier field, use the expression editor to select the attribute you marked as the supplemental ID.

      note note
      NOTE
      Make sure you are using the expression editor in Advanced mode to select the attribute.

    4. After selecting the supplemental ID, the associated namespace is displayed in the Supplemental namespace field as read-only.

Leverage supplemental ID attributes

Use the expression editor and personalization editor to reference attributes of the supplemental identifier for personalization or conditional logic. Attributes are accessible from the Contextual attributes menu.

For event-triggered journeys if you are working with arrays (e.g., multiple prescriptions or policies), use a formula to extract specific elements.

See examples

In an object array with the supplemental ID as bookingNum and an attribute at the same level called bookingCountry, the journey will iterate through the array object based on the bookingNum and create a journey instance for each object.

  • The following expression in the condition activity will iterate through the object array and check whether the value of bookingCountry is equal to “FR”:

    code language-none 
    @event{<event_name>.<object_path>.<object_array_name>.all(currentEventField.<attribute_path>.bookingNum==${supplementalId}).at(0).<attribute_path>.bookingCountry}=="FR"

  • The following expression in the email personalization editor will iterate through the object array, pull out the bookingCountry applicable to the current journey instance, and display it in the content:

    code language-none 
    {{#each context.journey.events.<event_ID>.<object_path>.<object_array_name> as |l|}}

{%#if l.<attribute_path>.bookingNum = context.journey.technicalProperties.supplementalId%} {{l.<attribute_path>.bookingCountry}}  {%/if%}

{{/each}}

  • Example of the event used to trigger the journey:

    code language-none 
    "bookingList": [
      {
          "bookingInfo": {
              "bookingNum": "x1",
                    "bookingCountry": "US"
          }
      },
      {
          "bookingInfo": {
              "bookingNum": "x2",
              "bookingCountry": "FR"
          }
      }
  ]

Example use cases

Policy Renewal Notifications

  • Scenario: An insurance provider sends renewal reminders for each active policy held by a customer.

  • Execution:

    • Profile: “John”.
    • Supplemental IDs: "AutoPolicy123", "HomePolicy456".
    • Journey executes separately for each policy, with personalized renewal dates, coverage details, and premium information.

Subscription Management

  • Scenario: A subscription service sends tailored messages for each subscription when an event is triggered for that subscription.

  • Execution:

    • Profile: “Jane”.
    • Supplemental IDs: "Luma Yoga Program ", "Luma Fitness Program".
    • Each event includes a subscription ID and details about that subscription. Journey executes separately for each event/subscription, allowing personalized renewal offers per subscription.

Product Recommendations

  • Scenario: An e-commerce platform sends recommendations based on specific products purchased by a customer.

  • Execution:

    • Profile: “Alex”.
    • Supplemental IDs: "productID1234", "productID5678".
    • Journey executes separately for each product, with personalized upsell opportunities.

How-to video video

Learn how to enable and apply a supplemental identifier in Adobe Journey Optimizer.

https://video.tv.adobe.com/v/3464792?quality=12
recommendation-more-help
b22c9c5d-9208-48f4-b874-1cefb8df4d76