Event-triggered messaging
This guide describes the event-triggered messaging use case pattern, which uses Adobe Journey Optimizer (AJO), Real-Time Customer Data Platform (RT-CDP), and Adobe Experience Platform (AEP) to deliver contextual, real-time messages in response to behavioral or system events. It is designed for solution architects, marketing technologists, and implementation engineers who need to understand what this pattern does, the business objectives it supports, the tactical use cases it enables, and the Adobe applications involved.
This pattern covers the full lifecycle from event ingestion and journey creation through message delivery and performance reporting.
Use case pattern
This section describes the core pattern and the execution plan that drives event-triggered messaging.
Event-Triggered Messaging
Listen for a real-time behavioral or system event, then deliver a contextual message to the triggering profile.
Execution plan: Event Ingestion > Journey Entry > Condition Evaluation > Message Delivery > Reporting
Use case overview
Event-triggered messaging delivers a contextual message in response to a real-time behavioral or system event. Unlike batch outbound message activation, which sends to a pre-evaluated audience on a schedule, this pattern listens for a qualifying event – such as a cart abandonment, a browse session, a form submission, or a system status change – and immediately enters the triggering profile into a journey that evaluates conditions and delivers a message.
The pattern relies on real-time event streaming into AEP (via Web SDK, Mobile SDK, or server-side API), a journey with a unitary event entry in AJO, and condition evaluation logic that determines whether and what to send. The message is typically sent within minutes of the triggering event, making this pattern ideal for time-sensitive, contextually relevant communications.
Organizations use this pattern to respond to customer actions in real time, increasing relevance and driving higher engagement and conversion rates compared to scheduled batch communications. Common scenarios include abandoned cart recovery, post-purchase follow-up, welcome messages after registration, and time-sensitive notifications like payment failures or price drop alerts.
Key business objectives
The following business objectives are supported by this use case pattern.
Recover abandoned carts & journeys
Re-engage users who dropped off during purchase, application, or enrollment flows with timely, personalized follow-ups.
Improve the percentage of visitors and prospects who complete desired actions such as purchases, sign-ups, or form submissions.
Deliver personalized customer experiences
Tailor content, offers, and messaging to individual preferences, behaviors, and lifecycle stage.
Accelerate time-to-value for new customers with streamlined, personalized welcome experiences and activation journeys.
Example tactical use cases
The following scenarios illustrate how event-triggered messaging can be applied across different business contexts.
- Cart abandonment email or SMS – Send a reminder message when a customer adds items to their cart but does not complete the purchase within a defined time window
- Browse abandonment follow-up – Re-engage visitors who viewed products or content but did not take a conversion action
- Post-purchase thank-you or cross-sell – Deliver a confirmation and cross-sell recommendation immediately after a purchase event
- Trial expiry reminder – Notify users approaching the end of a free trial with renewal or conversion messaging
- Welcome message after registration – Send an immediate onboarding message when a new user registers or creates an account
- Form submission confirmation – Acknowledge form submissions (contact requests, applications, enrollments) with a contextual confirmation
- Payment failure notification – Alert customers when a recurring payment fails, prompting them to update payment information
- App uninstall win-back push notification – Trigger a win-back message when a user uninstalls a mobile application
- Booking or appointment confirmation – Send immediate confirmation after a booking, reservation, or appointment is scheduled
- Price drop alert for wishlisted items – Notify customers when a product on their wishlist drops in price
Key performance indicators
The following KPIs help measure the effectiveness of event-triggered messaging implementations.
Applications
The following Adobe applications are used in this use case pattern.
- Adobe Journey Optimizer (AJO) – Journey orchestration with unitary event entry, condition evaluation, wait steps, message authoring, channel configuration, frequency governance, and delivery reporting
- Adobe Real-Time Customer Data Platform (RT-CDP) – Audience evaluation for condition-based filtering within journeys, consent and governance enforcement, profile enrichment
- Adobe Experience Platform (AEP) – Real-time event ingestion via Web SDK, Mobile SDK, or server-side API; data modeling; identity resolution; Edge Network
Related documentation
The following resources provide additional detail on the capabilities used in this implementation.