Goal Tracking
A step that asks whether a deal has reached the state you were after, and points somebody one way if it has and the other way if it has not. Deals are the only thing it can be asked about, which is the whole shape of it.
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.
It is a fork rather than a full stop
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.
It is asked when reached, not watched for
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.
The question can be narrowed to a stage
As well as the state, the box can name a pipeline stage the deal has to have reached, and the engine honours 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 webhooks that act without being asked.
Thirteen node kinds on a canvas: send, wait, branch on behaviour, split, call task, tag, goal. Publish a version and in-flight leads keep their own place.
A unique URL per integration with HMAC signing, rate limits, payload caps and idempotency - plus a log of every delivery it ever accepted or refused.
Hold a lead for minutes or days between steps, clamped to the sending window you set, so that an overnight wait never lands at four in the morning.
Set the hours a sequence may send inside, as a fixed offset you enter yourself, and every wait is pushed forward into them before it is stored.
One do-not-contact roll per workspace, checked when a lead is enrolled and again inside the send, straight after that send has taken its own claim.
New leads enrol themselves the moment they are created, and the four guards that can refuse an add are read on every single route into a cadence.
Drop a call step into a sequence and it raises an assigned task on the lead's owner, with the outcome the rep logs coming back as a branchable answer.
Twenty-six behaviours attach to wrap-up codes, and twenty codes ship already pointing at one, so ending a call the right way books the follow-up.
Six event types a CRM rule fires from: stage change, field update, new record, reassignment, schedule and inactivity, agreed in four places at once.
Send the email, assign the owner, raise the task, set the field, move the stage or call a webhook. Six modules, run in the order you stored them.
Eight comparison operators guarding each action, combined with AND and only AND, so a rule meaning either of two things is built twice, as two rules.
A text is a step on the same canvas as the email and the call task, written into the real thread and carried out by the number it is going out from.
A versioned path, a key minted once and kept as a hash, and the same role and profile model the interface runs on deciding what that key may touch.
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