惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

M
MIT News - Artificial intelligence
罗磊的独立博客
Hugging Face - Blog
Hugging Face - Blog
Apple Machine Learning Research
Apple Machine Learning Research
Last Week in AI
Last Week in AI
S
SegmentFault 最新的问题
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
美团技术团队
人人都是产品经理
人人都是产品经理
WordPress大学
WordPress大学
The Cloudflare Blog
IT之家
IT之家
雷峰网
雷峰网
小众软件
小众软件
博客园 - 叶小钗
博客园 - 聂微东
爱范儿
爱范儿
博客园 - 司徒正美
博客园 - 三生石上(FineUI控件)
V
Visual Studio Blog
博客园 - 【当耐特】
V
V2EX
博客园_首页
T
Tailwind CSS Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Goal vs Exit Criteria in Journey Builder: Measure What Ma...
SapotaCorp · 2026-05-24 · via DEV Community

Every Journey Builder setup sooner or later runs into the same question from the client: "How many of the people who entered this Journey actually bought?"

The answer lives in two settings that sit right next to each other on the Journey Settings panel - Goal and Exit Criteria. They do different things. Teams regularly set the wrong one, and the reporting quietly lies for months.

The setup

Our client ran a 3-email nurture sequence trying to convert leads into first-time buyers. The ask was simple: if the lead places an order before the sequence finishes, stop emailing them about the offer. Also, please show us the conversion rate at the end of the quarter.

That's two requirements. Goal handles one, Exit Criteria handles the other, and mixing them up was exactly how we got the reporting bug that triggered this write-up.

Goal — the success condition

Goal is the condition that represents "this Journey worked." Journey Builder evaluates it continuously for every active subscriber. The moment a subscriber meets the Goal, two things happen:

  1. They exit the Journey immediately, even if emails are still queued.
  2. They're counted as a Goal completion in Journey Analytics, which produces the conversion rate.
Example: Goal = subscriber has a record in Purchase_DE within 30 days of entry

Enter fullscreen mode Exit fullscreen mode

Set it when: you care about a conversion KPI you'll report on.

Without a Goal, Journey Analytics only shows open and click rates. You can't answer "what percentage of people converted?" from the Journey Builder UI. You'd have to query data views and DEs manually every time the client asks.

Exit Criteria — the removal condition

Exit Criteria is the condition that says "this subscriber doesn't belong in the Journey anymore." When they meet it, they're removed - but they're not counted as converted.

Example: Exit Criteria = subscriber unsubscribed, subscriber flagged as churned

Enter fullscreen mode Exit fullscreen mode

Set it when: you need to stop emailing certain subscribers under specific conditions, but their leaving isn't a success.

The distinction matters because of how these show up in reporting:

Goal

Exit Criteria

Removes subscriber from Journey

Yes

Yes

Counts as conversion

Yes

No

Shows up in Journey Analytics

Goal completion rate

Exit count (separate column)

Two mistakes we keep seeing

Mistake 1: Shipping without a Goal

We inherited a Journey from an earlier vendor that had been running for a month. The client asked us how many customers placed orders after entering the Journey. No Goal set, no number in Journey Analytics. We ended up running a SQL query against the Purchase DE joined to Journey membership, reconstructing what should have been one dashboard number.

If you have a conversion KPI the client will ever ask about, set the Goal on day one. Adding it later works, but the historical subscribers who already completed still won't count retroactively.

Mistake 2: Using Exit Criteria where Goal belongs

A team we reviewed had set Exit Criteria = "placed an order" instead of Goal = "placed an order." The Journey did remove buyers correctly - good. But the Goal completion rate in Journey Analytics was 0%, because Exit Criteria events don't roll up into goal metrics.

When the CMO asked about the conversion rate in the QBR, the dashboard said zero. Took about two hours of forensics to realize the Journey was actually converting fine, the measurement was broken. Single checkbox flip fixed it, but that's a bad conversation to have with a stakeholder.

Rule of thumb: if the outcome is what the business wants, it's a Goal. If the subscriber just needs to leave for a neutral reason (unsubscribed, became inactive, moved to a different segment), it's Exit Criteria.

When to use both

Most production Journeys we ship end up with both set:

  • Goal: "placed an order" - the win condition, tracked in conversion reporting.
  • Exit Criteria: "unsubscribed OR marked as inactive" - the "doesn't belong here" filter, not counted as a win.

Both evaluate continuously, both remove the subscriber on match, and the numbers at the end of the quarter actually match the business question.

Takeaway

Goal and Exit Criteria are the most important five minutes of any Journey build, and they're the most likely five minutes to get skipped. When a client asks you to "run a nurture campaign for Q4," the first question back should always be: "What does conversion mean, and when do we stop contacting someone?" Those two answers map to Goal and Exit Criteria. Skip them, and the Journey runs fine but your QBR deck has a column full of zeros.


Reviewing a Journey that reports odd numbers? Our Salesforce team ships production-grade Marketing Cloud engagements, including audits of inherited setups. Get in touch ->

See our full platform services for the stack we cover.