Goal Tracking
Stop writing to somebody who already bought. The step asks whether their deal reached the state you were after and sends them one way if it did and the other way if it did not. Deals are the only thing it can ask about.
Whether the thing you were after has happened yet
met- Fleet renewalwon£48,000
- mettaken
- not_met
Product figures from the platform’s own defaults - not customer averages
How it works.
The question is about a deal, and only a deal
It looks for a deal linked to that person whose state matches the one you picked: won, open or lost. There is nothing available to point it at a reply, a booked meeting, a field value or a tag.
Met does not mean stopped unless you wire it that way
Met and not met are two ports and the walk follows whichever applies. A yes stamps goal met as the run's exit reason and files the answer as an event, but somebody only stops being written to if the met port leads somewhere that ends.
Nothing watches the deal in the background
Nothing polls in the background for the deal. The check happens on the pass that arrives at the box, so where you place it, and which pauses sit in front of it, is what decides when it counts.
Won is not the only way to mean done
As well as the state, the box can name a pipeline stage the deal has to have reached, and the engine honors both together. So a goal can mean a deal sitting in Negotiating rather than any open deal at all.
Two moments in every run.
Every run passes through the same seven. Goal Tracking is the lit ones, and everything either side of it is a different page in this category.
- 01Trigger
the thing that happened first
- 02Enrol
how somebody gets onto it
- 03Wait
the pause, and what governs its length
- 04Branch
the fork, and which side is taken
- 05Act
the mail, the text, the task that goes out
- 06Measure
what counts as it having worked
- 07Exit
how somebody comes off it
The specifics.
8 facts- What counts
- A deal linked to that person sitting in the state you chose. Won unless you change it
- States selectable
- Won, open or lost. The deal table carries a fourth, abandoned, that the picker does not offer
- Ports
- Met and not met, both yours to wire, including straight into an end box
- Marked on the run
- The exit reason is written as goal met, and the answer is filed as an event against the box
- Pipeline stage
- The question may also name the stage the deal must have reached, tested alongside the state you chose
- When asked
- Only as the walk arrives. No background watcher and no retrospective sweep
- Not available as a goal
- A reply, a booked meeting, a field value or a tag. Deals are the only test there is
- Not the same as
- This is one cadence's own definition of done. Quotas and attainment across a team live elsewhere in the product
What starts this, and what it starts.
Automation is only ever a middle. These are the things that set it running and the things that run because of it.
More in Automation & Flows
13 capabilitiesSequences, dispositions and outside triggers that act without being asked.
What you draw is the thing that runs, not a picture somebody then has to build. Thirteen kinds of step, and publishing never moves a lead off their own place.
One address per source, sitting outside the login. The same delivery is never counted twice, every exchange is filed, and a new address cuts that source off.
Park a lead for minutes or days between steps. The delay you type is a floor rather than an appointment, so the sending hours can push it later, not earlier.
Nobody gets a message at ten past three in the morning. A pause coming due outside the hours you set is pushed forward before the time is ever written down.
One do-not-contact list per workspace, read on enrollment and read again inside the send, so an address added mid-cadence still stops the next message.
Nobody builds the list by hand. New leads enroll themselves as they are created, and the four checks that can refuse one run on every route into a cadence.
The phone, in the middle of a mail cadence. A rep gets a call task with their name on it, and whatever they log at hang-up decides where that lead goes next.
The do-not-call mark, the callback and the task happen because a rep picked the code, not because they remembered. Twenty-six behaviors, twenty codes shipped.
Six things set a CRM rule off: stage change, field update, new record, reassignment, schedule, inactivity. A filter stops it waking for everything that moves.
Send the mail, assign the owner, raise the task, set the field, move the stage, call a webhook. Six actions, none a placeholder, run in the order you set.
The check between a rule firing and an action actually running. Eight comparisons, every one an AND, so a rule covering either of two things gets built twice.
A text step on the same canvas as the mail and the call. It lands in the thread the SMS inbox reads, so the cadence and whoever answers see one conversation.
A key on a versioned path, seen exactly once, held to the same role and profile a person on your floor is, so it never reaches further than they would.
The rest of the platform.
Five more categories, all on the same record and the same bill. Each card names three of its capabilities, so you can tell from here whether it is worth opening.
Automation & Flows
See goal tracking on your own floor.
Thirty minutes, your numbers and your data. We will set goal tracking up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included