51黑料不打烊

Profile entrance management entry-management

Understanding how profiles enter a journey is essential for configuring 51黑料不打烊 Journey Optimizer. Profile entrance management depends on the journey type, with each type designed for specific use cases.

Types of journeys types-of-journeys

51黑料不打烊 Journey Optimizer supports the following journey types, each tailored to distinct purposes:

  • Unitary Event journeys: These journeys trigger when a single event occurs. After the event is received, the associated profile enters the journey. For example, a customer clicking a promotional email enters a journey designed to deliver targeted offers. Read more.

  • Business Event journeys: These journeys begin with a business event and include a Read Audience activity. Profiles in the targeted audience enter the journey after the event triggers. For example, profiles in a 鈥渓oyal customers鈥 segment enter a journey when a store launches a special VIP sale. Read more.

  • Read Audience journeys: These journeys start with a Read Audience activity, targeting specific audience segments. Profiles enter the journey during execution. These journeys can run once (鈥渙ne-shot鈥) or recur at defined intervals. For example, a recurring journey sends weekly updates to newsletter subscribers. Read more.

  • Audience Qualification journeys: These journeys respond to changes in audience membership, such as profiles entering or exiting an audience. For example, profiles added to a 鈥渉igh-value customers鈥 segment automatically enter a journey offering personalized rewards. Read more.

In all journey types, a profile cannot exist multiple times in the same journey simultaneously. The system uses profile identity as a key to enforce this rule. For example, if a profile is identified by CRMID=3224, the same key cannot occupy different positions within the same journey.

Unitary event and audience qualification journeys entry-unitary

In Unitary Event and Audience Qualification journeys, reentrance behavior can be configured based on journey requirements:

  • When reentrance is enabled, a profile enters the journey multiple times but only after fully exiting the previous instance. This is useful for scenarios like re-engagement campaigns, where profiles reenter after completing a cycle.

  • When reentrance is disabled, profiles cannot reenter the journey within the global timeout period. This prevents repeated triggers caused by the same event. For more details, refer to this section.

By default, journeys allow reentrance. When the Allow Reentrance option is activated, the Reentrance Wait Period field becomes available. This field specifies the minimum wait time before a profile can reenter the journey. For example, setting this field to 5 minutes prevents rapid, repetitive triggers from overlapping events. The maximum duration for this field is 91 days (global timeout).

After the reentrance wait period, profiles reenter the journey. To completely block reentrance, add a condition that checks whether the profile previously entered using profile or audience data.

Business journeys entry-business

In Business Journeys, reentrance rules operate similarly to those in unitary event journeys. To allow multiple executions of a business event within a journey, activate the relevant option in the Execution section of the journey properties.

For business events, profiles enter the journey multiple times simultaneously, with each instance corresponding to a separate business event. For example, if a profile belongs to a 鈥渇requent shopper鈥 segment and triggers two distinct business events, such as purchases at different times, they occupy different positions within the journey.

Audience data retrieved during the first execution is reused for up to one hour. This ensures consistent data while optimizing performance. For additional information, refer to this section.

Read audience journeys entry-read-audience

Read Audience journeys can be configured as recurring or 鈥渙ne-shot鈥:

  • Non-recurring/鈥淥ne-shot鈥 journeys: Profiles enter the journey once and cannot reenter. For example, a one-time campaign to onboard new customers uses this type.

  • Recurring Journeys: Profiles in the audience enter the journey during each recurrence. They must complete the journey before reentering during subsequent occurrences. For example, a recurring journey sends monthly reminders to members of a subscription audience.

Recurring Read Audience journeys offer two configuration options:

  • Incremental Read: During the first execution, all profiles in the audience enter the journey. Subsequent executions target only profiles added to the audience since the last run. For example, new subscribers joining a newsletter audience are added to the journey during later recurrences.

    note note
    NOTE
    When targeting a custom upload audience, profiles are retrieved only during the first recurrence if this option is enabled. This is because custom upload audiences are static.
  • Force Reentrance on Recurrence: This option forces profiles still present in the journey to exit automatically at the next recurrence. Avoid enabling this option for journeys requiring longer cycles, such as those involving wait activities, to ensure profiles complete their journey.

For more details, refer to this section

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