Goal Tracking
Stop Selling to People Who Already Bought.Sequence exit conditions that check the deal, so customers stop getting sales emails.
Add a goal step and the sequence checks the lead’s deal before it sends any more. Won? Send them down a different path, or end the sequence there. Not yet? They carry on. You can also require a pipeline stage, so a goal can mean “in negotiation”, not just “won”.
- Won, open or lost
- Optional pipeline stage
- Met and not met paths
How it works
- The sequence runsEmails, texts and calls go out
- A goal step checksIs their deal won yet?
- Deal wonTaken off the sales pathNot yetThe sequence carries on
No Sales Emails After the Sale.
Once their deal is won, the goal step takes them off the sales path, so the next email isn’t a pitch for what they bought.
Point the goal at won, open or lost deals, and optionally a pipeline stage like Negotiating.
Met and not met each lead somewhere you choose, including straight to an end step.
A met goal is saved as the reason the lead left, so you can count how many got there.
Set a Goal in Three Steps.
Add a Goal Step
Drop it where the check should happen, such as before the next sales email.
Pick the Deal State
Choose won, open or lost, and optionally the pipeline stage the deal must have reached.
Wire Both Answers
Send met to an end step or a customer path, and let not met carry on with the sequence.
Three Ways to Define Done.
The deal is closed and won. The default, and the simplest way to stop pitching new customers.
The lead now has an open deal. Pair it with a stage, so the goal can mean they reached Negotiating.
The deal was lost. Send these leads down a different path from everyone else.
How Sequence Exit Conditions Keep Follow-Up Polite.
Sequence exit conditions take a lead off the sales path once the sequence has done its job. In Adoptiv, the exit criteria live on a goal step: it checks whether the lead’s deal has reached the state you chose, and sends them one way if it has and another way if it hasn’t.
A sequence goal is always about a deal, and only a deal. Point it at won, open or lost, with won as the default. Add a deal stage goal too, and the deal must also have reached that pipeline stage, so done can mean a deal sitting in Negotiating, not any open deal at all.
The check happens when a lead reaches the goal step, not in the background, so placement matters. To stop the sequence when a deal is won, put a goal step before the emails you would not send a customer, and wire its met path to an end step. That is how you stop emailing customers who bought.
A met goal is saved as the reason the lead left, and the answer is recorded against the step, so a conversion goal doubles as a count of how many leads got there. Pair it with an A/B split to record which version reached more won deals, or use branch logic to react to replies and calls along the way.
A Clear Finish Line for Every Sequence.
Wire the met path to an end step, and customers stop getting sales emails.
Pick the deal state that means the sequence did its job.
Both answers lead wherever you wire them.
Leads who met the goal are marked that way on their run.
For Teams That Know When to Stop Selling.
Goal Steps vs Removing Customers by Hand.
| What | Remembering to take people out | With Adoptiv |
|---|---|---|
| A deal is won | Remembering to take people out: Someone has to pull them from the sequence | With Adoptiv: The next goal step takes them off the sales path |
| What counts as done | Remembering to take people out: Up to whoever notices | With Adoptiv: Won, open or lost, plus an optional stage |
| Counting conversions | Remembering to take people out: Cross-checked by hand | With Adoptiv: Goal met saved as the exit reason |
| When the check happens | Remembering to take people out: Whenever someone looks | With Adoptiv: When a lead reaches the goal step, not in the background |
Goal Tracking Questions, Answered.
What are sequence exit conditions?
Rules that take someone out of a sequence once it has done its job. In Adoptiv, a goal step checks whether the lead’s deal has reached the state you chose, and sends them a different way if it has.
Can a sequence stop when a deal is won?
Yes. Add a goal step set to won and wire its met path to an end step. The sequence stops for anyone whose deal is won when they reach it.
Can the goal be a reply or a meeting?
No. Goals check deals only: won, open or lost, plus an optional pipeline stage. To react to a reply, use a replied branch instead.
Does the goal watch the deal all the time?
No. It checks when a lead reaches the goal step, so where you place it decides when it counts. Put one before the emails you would not send a customer.
Does meeting the goal stop the sequence by itself?
Only if you wire it that way. Met and not met are two paths, and someone stops only when the met path leads to an end step.
What deal states can a goal check?
Won, open or lost, with won as the default. You can also require a pipeline stage on top.
Can I have more than one goal step?
Yes. Place one wherever a check makes sense, such as before each email you would not send a customer.
What happens if the lead has no deal?
The goal isn’t met, so the lead carries on along the not met path.
Is a sequence goal the same as a sales quota?
No. A goal step is one sequence’s definition of done. Team targets and attainment live in Goals and Leaderboards.
Still have a question? A real person replies in under 60 seconds in US business hours. Talk to our team →
14-day free trial
Stop Emailing People Who Already Said Yes.
Add a goal step to your first sequence in the free trial. Free for 14 days, no credit card.
14-day trial · no card · migration included