Conversion record vs path goal: measure success vs teleport the contact

What is the difference between recording a conversion and setting a path goal?

A conversion record logs that a success event happened for reporting. A path goal (teleporter) immediately moves the contact to a later node when conditions match, skipping intervening waits and emails. Measurement ≠ path control.

One-line for eCRM teams: conversion = metric; path goal = control flow. One event can fire both — in two separate handlers.

Teams often turn on a “purchase goal” only in the dashboard and expect later messages to stop. Without an exit node or path jump, the buyer still gets three nurture emails. See path framing in Adaptive journey vs rule-based and Marketing journey vs campaign.

How does each one work?

Conversion record (measurement)

A success event (order_completed, demo_booked) links to the automation so path conversion rate appears in reports. The person’s place on the canvas does not necessarily change unless you also define an exit.

Path goal (path control)

A goal node or exit rule: when the condition matches, jump from anywhere in scope to that node or leave the flow. In-between touches do not send.

Iran example: abandoned-cart journey

Path: enter cart_updated → wait 2h → email 1 → wait 1 day → email 2 → SMS. Customer buys after email 1. With only a conversion record, you get a conversion in the report but email 2 and SMS still fire. With a path goal on order_completed, the contact jumps to exit and later touches stay dark. Use both: metric + control.

Diagnosis

Practical fix

1. Define a business success for every revenue journey (purchase, demo, activation).
2. Wire that event to a conversion record.
3. Wire the same event as path goal / exit so later touches stop.
4. Do not use open/click as path goals unless it is a conscious experiment.
5. For realtime shots apart from multi-day paths, review Journey vs realtime event campaign.

When which?

1. Only need to know conversion %? → At least a conversion record.
2. Must not email after purchase? → Path goal / exit is mandatory.
3. Want to jump into post-purchase after buy? → Goal as teleporter into another branch.
4. A/B mid-path creatives? → Put the goal on final business success, not on opening variant A.
5. Does the success event fire once and cleanly in the Leadara catalog?

Leadara mapping: events, segments, journeys, email/SMS

1. Event order_completed (or equivalent): fuel for both handlers.
2. Journey: exit node / “if purchased → exit” condition in addition to the report counter.
3. Suppress segment: recent buyers out of “you still have not bought” blasts — third defense layer.
4. Email/SMS: no post-goal marketing touches; transactional receipts stay separate.
5. Reporting: path goal-exit rate and time-to-convert apart from campaign CTR.

Common mistakes

• Assuming “conversion is on, so messages stop”
• Path goal on weak signals (opens)
• No parallel campaign suppress after purchase
• Mashing analytics and control into one vague setting
• Paths with no defined success at all

FAQ

What is the difference between a conversion record and a path goal?

One measures; the other moves or exits the contact on the path.

Can I use only one?

For revenue flows, use both. Metric without exit = messages after success.

What does teleporter mean?

An immediate jump to the goal node when the condition matches, without walking intermediate waits — a control-flow metaphor, not magic.

Is a HubSpot workflow goal the same as an ActiveCampaign conversion?

It is closer to exit + measurement combined; what matters is knowing which setting in your tool changes the path and which only counts.

Should the goal be a click?

Usually not for purchase paths. Clicks are mid signals; aim at downstream business success.

How in Leadara?

Success event + journey exit condition + optional suppress segment; name conversion reporting apart from path control.

If the purchase event arrives late?

One extra touch may slip through; before every expensive touch (SMS), re-check “still has not purchased.”

Bottom line and next step

Do not mash measurement with path jumps. This week, put both a conversion record and a purchase exit on one cart journey — drive post-purchase messages near zero and report path conversion separately.

14-day test pattern

Days 1–2: lock the purchase event in the catalog.
Days 3–5: conversion + exit on the same journey.
Days 6–10: 10% holdout with conversion only (to see post-purchase damage).
Days 11–14: compare post-purchase messages and time-to-convert.

If B zeroes the damage, make it standard.

Team language: did we count or did we jump?

If someone says “goal hit,” ask: logged in the report only, or also exited the path?

Go-live checklist

1. Business success defined?
2. Conversion record wired?
3. Path goal / exit on the same event?
4. Re-check before SMS?
5. Parallel blast suppress?
6. Dashboard: path conversion rate, messages after success, STOP?

Boundary with if/else branches

A “bought / not” branch decides at one point; a path goal can jump from anywhere on the path. Both are control flow; conversion is neither until you also build an exit.

Healthy measure/control separation signals

30-minute whiteboard drill

For every live journey, draw two columns: “what we count” and “what we do to the path when it happens.” If column two is empty, build the exit this sprint.

Related reading

• Adaptive journey vs rule-based
• Marketing journey vs campaign
• Journey vs realtime event campaign

Operator runbook: two ticks on every revenue journey

Put two mandatory checkboxes on every revenue journey card:

1. Do we count it? Success event wired to a conversion record.
2. Does the path change? Same event has an exit or teleporter.

If only box 1 is checked, the card is red and cannot ship. If both are checked, write one QA line: “after purchase, next marketing email/SMS = 0; transactional receipt separate.” Prove that line with one real test purchase in staging before go-live.