Products Automation

Automate journeys, not just messages

Edit it while it’s running. Run parallel instances for the same user. Trigger it from a price drop instead of a click. The journey moves with the user, not around them.

One canvas. Five things most tools can't do.

Tap any pin to open

One canvas. Five things you couldn't do before.

Tap any pin to open

Three things only WebEngage does

Every automation tool triggers, branches, waits, and sends. These three go further.

Contextual Journey

Let a user be in the same journey several times simultaneously, once for each order.

Read on

Live Journey Editing

Add or remove nodes, rebuild paths and change logic while a journey is still running.

Read on

Relays

Trigger automated workflows off business-side events rather than user actions.

Read on

Three things only WebEngage Automation does

Three journeys. One user. In parallel.

Emma orders three times in one afternoon. Most tools can only track one. Contextual Journeys runs all three in parallel.

 
 

Edit live journeys: no pause, no versioning, no sunset

Most tools make you stop a journey to change it, or they quietly spin up a new version. Only WebEngage allows you to edit a journey while it’s running. Every user, old and new, follows the updated
flow the moment you publish.

Back in stock at 2am. Messaged user by 2:01.

Trigger journeys from any business event, system update, or API call, not just user actions. Relays automatically match events to the right users, like linking a price drop directly to its wishlisters, without needing segment lookups.

What can WebEngage Automation unlock for your role?

Find what converts, fix what doesn't

  • Build multi-step, cross-channel journeys on a drag-and-drop canvas, without engineering help.
  • Edit a running journey live so users already in the flow get the improved logic immediately
  • Trigger a fresh journey for every order or cart with Contextual Journeys, not just once per user.

Find what converts, fix what doesn't

  • Measure true incremental lift with Universal Control Groups that hold out a slice of users across every channel automatically.
  • Add any API-based system as a step in your journey and not just native channel, whether it's direct mail, CPaaS, or your own CRM.
  • A/B test different messages, or entire branches inside a journey, then send the rest of your audience down the winning path.

Find what converts, fix what doesn't

  • Enforce frequency caps and quiet hours across all channels at once, not per-channel.
  • Stop duplicate sends before they leave the queue with intelligent deduplication on the unified profile.
  • Govern every team's journeys from one orchestration layer instead of stitching together separate channel tools.

Additional Resources

Product Updates

WebEngage Is Now Salla Platform Native – Asia’s #1 CEP Joins Hands With GCC’s Largest E-commerce Platform

Salla is one of the largest commerce platforms in the GCC region, built specifically for merchants in the Middle East…

Read the announcement

Product Updates

Analytics Digest – Introducing Multi-splits in Event Analytics, Choose Between Uniques/Occurrences In Funnels, Hold Property Constant In Funnels & Compare Funnels Across Time Periods

WebEngage is rapidly becoming the de-facto Analytics toolkit for its customers across product and growth teams. As our usage grows…

Read the announcement

Product Updates

Introducing Entity Relationship Visualizer – Manage Relationships Between Your CDPx Data Objects In A Visual Interface

Last year, we launched a composable version of our Customer Data Platform; CDPx, and introduced Entities – a simple way…

Read the announcement

See All Releases

Stop sending campaigns. Start running journeys.​

Back to Products

platform

Platform

Zero PII

No personal data stored.

AI-Powered

Atlas AI

AI-powered customer engagement suite.

Back to Products

Capabilities

Customer Data Platform

Your schema, your engagement rules

Automation

Automate workflows, orchestrate growth

Segmentation

Precise user segmentation, simplified

Personalization

Smarter web and app personalization

Analytics

Deeper analytics, sharper decisions

Recommendations

Context-aware recommendations that sell

Back to Products

channels

IVR, Chatbot, & more

Back to Products

Solutions

Travel & Hospitality

Healthcare

Automotive

Insurance

E-commerce and Retail

Back to Products

Resources

Product Releases

Ebooks

Blogs

Newsroom

Webinars

EngageMint

Impact Stories

Glossary

FEATURED

Featured Release

Introducing Entity Relationship Visualizer – Manage Relationships Between Your CDPx Data Objects In A Visual Interface

Read more

Upcoming Webinar

Winning Back Users: Proven Retargeting & Deep Linking Strategies.

Register now

Products

Platform

Zero PII, Black, Composable CDP

Capabilities

CDP, Segmentation, Analytics & more

Channels

Mobile, Email, WhatsApp, SMS & More

Solutions

BLACK

Resources

Request a Demo
Login

Nudge them when it matters, not on a schedule

A wait doesn’t have to mean two hours for everyone. Hold until they open the app. Hold until Friday. Hold until they’re awake in their timezone. The journey aligns to the user’s rhythm, not the calendar.

Four wait blocks

By duration, until a date, until a specific time window, or until the user does something.

See docs

Send Intelligently (STO)

Your 9am is someone’s dead zone. Switch this on and each person gets the message at the hour they’ve historically opened, read, or tapped. Worked out per person, per channel, from their own history.

Read More

DND hours

Suppress sends during a user’s quiet hours, applied per user in their own timezone.

See docs

Frequency capping

Cap total messages per day, week, or month, and maintain a minimum gap between consecutive sends across channels.

See docs

Queueing

When DND or frequency caps block an immediate send, hold the message for up to the configured duration and deliver as soon as constraints clear.

See docs

02/05

Previous

Next

Reach users everywhere they engage.

Drop a WhatsApp next to it. Branch to SMS for the unreachable users. Every node sees the same profile, the same events, the same merge tags. The channel becomes a setting, not a silo.

Nine channels on one canvas

Email, SMS, Push, In-app, On-site, Web Push, WhatsApp, Web In-line, App In-line, every channel is a draggable node. No separate builder, no separate audience.

See docs

Branch on what happened after the send

Delivered, opened, clicked, bounced, dismissed, or never seen. Every send block offers the outcomes its channel can actually report, and any of them can start its own branch.

Read More

Is user reachable

A condition block that splits the journey based on whether the user is reachable on a specific channel right now, so you can fall back gracefully.

See docs

Check best channel

Some of your users open every email. Some haven’t in a year but read WhatsApp within the minute. Instead of picking one channel for everyone, let the journey read each person’s history and send down the one they respond to.

See docs

01/05

Previous

Next

A journey can start from anything.

Five different entry triggers: pick one, or layer them. An event the user performed, a segment they entered or exited, a change in a user attribute, a CSV list you upload, or a geofence they crossed. Different users can enter through different doors and share the rest of the flow.

Occurrence of Event

Start the journey when a user performs a specific event, filtered further by event attributes combined with AND/OR logic.

See docs

Enters / Exits / Is In Segment

Four modes: Enters, Enters or Is Already In, Is Already In, or Exits, applied to any Live Segment or static List.

Read More

Change in User Attribute

Trigger on any change to an attribute value, or specifically when the Old Value or New Value matches a condition you define.

See docs

For Specific Users

Curate the audience manually via CSV upload (up to 50 MB) or by pasting a list of User IDs. Add more users to a live journey anytime.

See docs

Enter / Exit Geofence

Draw a virtual fence around any location on a map and start the journey when a user enters or exits.

See docs

03/05

Previous

Next

Ask a question mid-journey, then split

At any point you can check something about the person, such as, are they in this segment, have they done this yet, what’s their plan worth, can we even reach them here, and send yes down one path, no down another. The journey stops being one line and starts being a decision tree.

Is In Segment / List

Branch the journey based on whether the user is currently inside a Live Segment or a static List. Useful for ending the journey for some users, or sending a different path.

See docs

Has Done Event

Branch based on whether the user has performed a specific event or not. Further filterable by event attributes with AND/OR logic.

Read More

Check User Attribute

Branch on the value of a User Attribute: equal to, greater than, less than, contains, and so on. Compare against literal values or other attributes.

See docs

04/05

Previous

Next

Where the journey is measured.

You can see who opened and who clicked. Neither answers the question you actually get asked: did this make us money? Pick the action that counts as success: a purchase, a renewal, a signup, and the journey reports how many people did it. One number for the whole flow, not nine numbers for nine messages.

One Conversion Event per journey

Pick the action that defines success, for instance, checkout_completed, subscription_purchased, course_started. Filter further by Event Attributes if you only want a specific kind of conversion to count.

See docs

Conversion Deadline

Someone who buys an hour after your message probably bought because of it. Someone who buys three weeks later probably didn’t. Set the window in hours or days, and anything outside it doesn’t count toward the journey.

Read More

Revenue tracking, automatic

If the Conversion Event is mapped as a Revenue Event, monetary value rolls up into the journey’s total Revenue alongside the conversion count.

See docs

05/05

Previous

Next