Audience Path vs Action Path routing: who they are now vs what they do in a window

Audience Path routes on who the person is right now (attributes/segments at the moment they hit the step); Action Path holds them for an evaluation window and routes on engagement or custom events that fire during that window.

What is the difference between Audience Path and Action Path routing?

In a marketing journey you usually ask one of two questions at a fork:

1. Who are they now? VIP, gold RFM, Tehran city, verified email?
2. What will they do next? Click the SMS, return to cart, purchase, open the app?

Audience Path answers (1): when the person reaches the step, it evaluates current attributes/segment membership and first-matches them into a group—no waiting for a future click.

Action Path answers (2): it parks the person for a window (hours/days), listens for engagement or custom events inside that window, and advances on first-match (or, on some platforms, ranked choice at window end).

This is not the same as trigger split vs conditional split—that contrasts this-entry-event fields vs profile history. Here the fork is when you evaluate and what signal you trust: state-now vs behavior-in-window.

How does each mode work?

Audience Path

Person enters the step. Groups are checked in order. First attribute/segment match wins; otherwise Everyone Else.

• Input: profile fields, segments, derived flags
• Timing: instant at step entry
• Waiting for a future click/purchase: no

Action Path

Person enters; a window timer starts. Events such as email open/click, SMS click, cart update, purchase, app open can match groups. Configuration is usually:

• First-match: first qualifying event advances immediately
• Ranked at window end: wait out the window, then pick the highest-priority match (see action-path first-match vs ranked window)

Concrete Iran ecommerce / SaaS examples

Fashion store — VIP-now vs Kavenegar SMS click

Audience Path: vip_gold → gift + priority shipping creative; vip_silver → mid discount; else → standard. Decision is current membership, not future behavior.

Action Path after a cart SMS: 6-hour window for sms_clicked, cart_updated, or order_completed. Click → size-guide email; cart update without purchase → softer SMS; purchase → post-purchase exit; none → education email.

Clinic — “has appointment” segment vs attendance events

Audience Path when you need has_upcoming_appointment=true or “this week’s appointments” segment now.

Action Path when, after a confirmation message, you wait 24h for appointment_confirmed vs appointment_cancelled.

SaaS — current plan vs feature activation

Audience Path on plan=pro vs plan=free. Action Path on a 7-day window for feature_x_used after onboarding.

When to choose which

1. Stable profile truth (loyalty tier, city, subscription) → Audience / segment-attribute branch.
2. Post-message behavior → Action / wait-for-event window.
3. “Did they click the email I just sent?” → send first, then Action Path—not an immediate Audience check.
4. Often stack them: Audience for tiered creative, then Action for reaction.
5. Always design the “no event in window” path.

Leadara mapping (events, segments, journeys, email/SMS)

Use Leadara primitives only—no invented Canvas product names as features:

• Segments / attribute branches: practical Audience Path—check VIP/RFM/profile when they hit the fork.
• Events + wait / engagement window: practical Action Path—after email/SMS (Kavenegar/Nikaline), wait for purchase, cart, click, open and branch.
• Journeys: order matters: message → behavior window; or segment filter → tailored message.
• Email / SMS: creative must match the branch signal (VIP ≠ quiet non-clicker).
• Live Chat: human support if someone is confused; AI Chat is an internal team assistant, not a customer-facing live-chat bot.
• Popups / web push only when they produce real events you branch on.

Common mistakes

• Audience Path right after send to “detect click” before a click can exist.
• 30-day Action windows with no “none” path.
• Assuming Action Path sees enrollment-event properties like a trigger split unless you stored journey context.
• Ambiguous priority when someone both clicks and purchases.
• Manually editing VIP segments daily instead of stable definitions + Audience fork.
• Confusing this with segment enters vs already-in vs exits—that is entry triggering; this is mid-journey routing.

One-line takeaway

Audience = who are they right now?; Action = what do they do in the next N hours?

Next step

Open one live fork. Ask: loyalty card or behavior timer? If the first, segment/attribute; if the second, event window with a silence branch.

FAQ

Do I need a delay before an Audience Path that checks email clicks?

If you mean clicks after this message, use Action Path / wait-for-event. If you mean historical clickership already on the profile/segment, Audience at step entry is fine.

Can Action Path see Canvas/journey entry event properties?

Only if you persist them as journey/profile context. For fields on the enrollment event, a trigger/enrollment split is usually cleaner.

What happens if someone matches two Action Path groups?

First-match: earlier group wins. Ranked: configured priority at window end. Treat group order like code.

How often does Audience Path re-evaluate?

Typically when the person reaches that step again—not continuously in the background unless you also have segment-entry triggers.

Which is better for RFM?

Current RFM tier → Audience/segment. Reaction to an RFM offer in the next 24h → Action.

Can I stack both?

Yes—and you often should: Audience for message tier, send, then Action for reaction.

When does Everyone Else matter?

Always—especially with incomplete segment coverage.

Step-by-step for growth

1. One sentence: state-now or window-behavior?
2. Name the signal (vip_gold vs sms_clicked).
3. If Action, lock window length to product reality.
4. Write silence-path creative.
5. Build with segment branch or wait-for-event; test VIP, clicker, quiet.
6. After a week, if 90% is Everyone Else, fix definitions/window.

Versus conditional splits and segment triggers

Conditional splits read history; segment triggers start journeys; Audience/Action fork mid-path. Do not mix entry tools with routing tools.

Metrics to watch

• Audience branch share (VIP vs else)
• Action conversion vs silence share
• Median time to first in-window event
• Unsubscribes on aggressive silence-path follow-ups

PM reporting language

Say “6h Action after cart SMS: 28% click, 12% purchase, 60% silence→education email,” not “we have smart routing.”

Programmer-shaped sketch

on_step(profile):
  if mode == audience:
    for group in audience_groups:
      if match_attrs_or_segments(profile, group): advance(group); return
    advance(everyone_else)
  if mode == action:
    window = start_timer(N)
    listen events in window:
      if first_match and event in group: advance(group); return
    at_end_or_rank: advance(best_or_none)

Acceptance tests before publish

1. VIP profile → correct Audience branch, no wait.
2. Normal profile clicks SMS inside window → Action click branch.
3. Quiet until window end → none branch, not purchase path.
4. Two events back-to-back → priority/first-match as documented.
5. Confused customers get human Live Chat; do not put AI Chat in customer live chat.

Channel checklist

• Action SMS: trackable short link?
• Audience VIP email: distinct tone from non-VIP?
• During Action window: intentional silence unless a separate reminder exists?

QA matrix for Audience vs Action

Why Iran SMS makes Action Path vivid

Kavenegar delivery is not the same as a click. Use Action Path on sms_clicked or site return events—not on “we handed the SMS to the provider.” If you need send vs delivery branching, that is a different post (channel On-Send vs On-Delivery).

Related reading

• Action-path first-match vs ranked window: advance on first event or wait and pick the top path
• Trigger split vs conditional split: this event’s data vs the profile’s history
• Segment Enters vs Already-in vs Exits trigger: new joiners only, everyone currently in, or people who just left