On this page: Learn scalable patterns and best practices for using Experience Events in journeys to suppress, qualify, or personalize for profiles based on their behavior and event attributes.
This page outlines common patterns and scalable approaches to help you make the most of Experience Events in Adobe Journey Optimizer. These use cases are designed to help you solve frequent challenges such as managing opt-outs, controlling message frequency, personalizing content based on user behavior, and reacting to real-time signals.
By leveraging these strategies, you can turn behavioral data into meaningful actions—suppressing, qualifying, or excluding profiles based on the events they trigger or the attributes they carry. Whether you’re building logic for purchase thresholds, abandonment triggers, or bounce handling, these examples offer practical guidance you can adapt to your needs.
As you evaluate which approach fits best, consider the latency requirements of your use case to ensure your journeys remain responsive and effective.
Opt-out suppression
To suppress profiles that have opted out of marketing communications, use built-in consent management. Opt-out preferences are automatically captured in the profile’s consent fields; they can be referenced directly in journey conditions and are automatically enforced by Journey Optimizer during message delivery.
Learn more:
Bounce-based suppression
To exclude profiles that have experienced email bounces, leverage Adobe Journey Optimizer’s automatic suppression list for bounced addresses. This built-in mechanism ensures that invalid or unreachable emails are excluded from future sends without requiring custom logic.
Learn more:
Generic suppression
To suppress profiles that have demonstrated certain behaviors, use batch audiences with event-based logic to capture profiles that meet the suppression criteria. Reference this audience in journey conditions.
Learn more:
-
Adobe Experience Platform Segment builder - Events
-
Adobe Experience Platform Segment builder – Time constraints
Communications-received exclusion
To prevent sending messages to profiles who have received any communications within a recent time window:
- Use batch audiences with time-based criteria and reference them in journey conditions.
- Apply frequency capping business rules to enforce daily or weekly message limits.
Learn more using audiences:
-
Adobe Experience Platform Segment builder - Events
-
Adobe Experience Platform Segment builder – Time constraints
See also:
Message-specific inclusion/exclusion
To include or exclude profiles based on whether they received a specific message, create batch audiences that encapsulate this logic and reference them in journey conditions.
Learn more:
-
Adobe Experience Platform Segment builder - Events
-
Adobe Experience Platform Segment builder – Time constraints
Cart or browse abandonment personalization
To personalize communications based on the latest cart or browse events across multiple cart types or product views:
- If you have access to Adobe Experience Platform Data Distiller, configure automated queries to extract the required data from the event, manipulate it to fit the use case, and write it back to a profile-enabled dataset for activation.
- If the abandonment data can be modeled on the profile with scalar attributes, consider using Computed attributes to capture the latest information and then reference these attributes in the journey to construct the communication. Learn more in Adobe Experience Platform documentation
Behavior-based journey exit
To remove profiles from journey when they exhibit a particular behavior, utilize exit criteria to exit the profile from the journey when a particular event is received or the profile qualifies for a specific audience.
Learn more:
Purchase-based qualification with value thresholds
To trigger journeys based on purchases and suppress if value is above/below a threshold, define computed attributes to sum purchases over a specific time period. Create an audience that includes profiles whose spending amount meets certain criteria.
Learn more:
- Adobe Experience Platform Computed attributes overview
Frequently asked questions faq-ee
This FAQ focuses on the timeline for retiring experience event usage in journey expressions and who is impacted. For guidance on alternative approaches, see the use cases and best practices above.
Need more details? Use the feedback options at the bottom of this page to raise your question, or connect with the Adobe Journey Optimizer community.
Only the lookup of experience events in the expression editor is impacted. The following capabilities are not impacted and remain the same:
-
Observing the experience events associated with a specific profile in the profile UI
-
Using experience events in computed attribute rules and accessing the computed attributes in a journey
-
Triggering a journey with a unitary or business event
-
Using journey context data from the events that trigger the journey in the expression and personalization editors
-
Listening to an event within a journey
-
Configuring events to trigger a journey
-
Detecting end user reaction events to marketing communications (e.g., email open)
This section contains structured knowledge intended to support interpretation, retrieval, and question answering related to this topic.
For complete understanding, this information should be combined with the documentation on this page. Neither source is intended to stand alone; the page describes the feature, while this section provides additional context that helps disambiguate terminology, intent, applicability, and constraints.
- TL;DR: This page outlines alternative patterns and best practices for using Experience Event data in Adobe Journey Optimizer journeys, in the context of the deprecation of direct experience event lookup in the journey expression editor.
Intents:
- Suppress opted-out profiles using built-in consent management instead of experience event expressions
- Exclude bounced email addresses using the AJO automatic suppression list
- Build generic suppression logic using batch audiences with event-based criteria
- Prevent over-communication by applying frequency capping rules or time-based audience conditions
- Personalize abandoned cart or browse communications using AEP Data Distiller or Computed attributes
Glossary:
- Experience event: A time-stamped, immutable record of a customer action or behavior stored in Adobe Experience Platform (product-specific)
- Computed attribute: A profile-level attribute derived from aggregating or summarizing experience event data over time, available for use in journey expressions (product-specific)
- Suppression list: AJO’s built-in list of email addresses automatically excluded from future sends due to hard bounces or spam complaints (product-specific)
- Frequency capping: A business rule that limits how many messages a profile can receive within a defined time window (product-specific)
- Data Distiller: An AEP capability that enables SQL-based batch queries to extract and transform event data into profile-enabled datasets (product-specific)
Guardrails:
- Starting July 8, 2025, new customer organizations cannot create expressions using experience event attributes in the journey expression editor.
- Starting April 1, 2026, organizations that have not used experience event attributes in journey expressions in the last 90 days will lose access to this capability.
- Direct experience event lookup in journey conditions is being retired; alternatives include batch audiences, computed attributes, and AEP Data Distiller.
- Capabilities NOT impacted by the retirement include: triggering journeys with events, listening to events within a journey, using journey context data from trigger events, configuring events, and detecting reaction events.
Terminology:
- Canonical name: Experience event lookup — Acronym: EE lookup — variants: experience event expressions, event attribute lookup
- Synonyms: “batch audience with event-based logic” = “event-based segment” as a suppression/inclusion mechanism
- Do not confuse: “experience event lookup in expression editor” ≠ “triggering a journey with an event” — triggering journeys with events is NOT being retired
FAQ:
- Q: Can I still trigger a journey using an experience event? — Yes, triggering journeys with unitary or business events is not impacted by this change.
- Q: What is the recommended replacement for experience event lookup in journey conditions? — Use batch audiences built with AEP Segment Builder event-based logic, computed attributes, or AEP Data Distiller for complex transformations.
- Q: Is my existing organization affected right now? — New organizations are affected from July 8, 2025. Existing organizations are affected from April 1, 2026 only if they have not used the capability in the last 90 days.
- Q: How do I handle cart abandonment personalization without direct event lookup? — Use AEP Data Distiller to extract and write event data to a profile-enabled dataset, or use Computed attributes to capture the latest abandonment state on the profile.
- Q: What capabilities are NOT impacted by this deprecation? — Triggering journeys with events, listening to events inside journeys, using trigger event context data in expressions, configuring events, and detecting reaction events (e.g., email opens) are all unaffected.