Track revenue targets and sales quotas
Goals help your team stay focused on targets and measure progress toward key objectives.
The Goals module lets you define measurable targets for individuals, teams, and the whole organization. Every goal tracks one metric over one period, and progress is computed automatically from your CRM data. Goals also feed the Sales Leaderboard, so the same numbers that drive a rep's progress bar also drive their standing on the board.
Every goal measures one metric drawn from a single shared catalog.
Goals and the leaderboard read the same metric catalog, so a metric always means the same thing wherever it appears. Ten metrics are available — eight are simple counts and two are currency amounts:
The goals page displays each goal with its target, progress, and pace.
Each goal appears as a row with its key details visible at a glance. Use this view to monitor progress across your team and quickly spot goals that are ahead, on track, behind, or at risk.
Every goal is scored against where it should be for the time elapsed in its period.
Progress alone doesn't tell you whether a goal is healthy — being 40% of the way to target is great on day two of a month and worrying on day 28. Every goal is therefore scored by comparing how far along its progress is against how much of its period has elapsed. That comparison produces one of five pace states:
A subject can hold only one active goal for a given metric and period type at a time.
Each person, team, or organization can have only one active goal for a given metric and period type — for example, one active monthly Revenue Won goal per rep. This keeps progress and leaderboard attainment unambiguous. If you try to create a second active goal that collides with an existing one, the create is refused with a message like “An active Revenue Won goal for this monthly period already exists for this user.” You can still keep goals for other metrics or other period types alongside it.
Goal visibility follows your role's data scope.
The goals list is filtered to what your role is allowed to see. Which goals appear depends on your goals view scope:
Goals feed the leaderboard's attainment ranking.
The Sales Leaderboard can rank your team three ways — by a raw metric total, by most-improved, or by attainment. Attainment mode is the one wired directly to goals: it ranks each rep by how far they are toward their own goalfor the metric you pick with the board's metric selector. So the board never shows an unqualified “goal attainment” number — it always reads as attainment against your chosen metric, for example “attainment vs your Revenue Won goal.”
Goal crossings notify the goal owner.
When a goal you own reaches its target, you get a Goal Achieved notification — an awareness update in your notifications, folded into your email digest rather than sent immediately. When a goal you own falls behind and is trending to miss its target, you get a Goal at Risknotification — an actionable alert delivered both in-app and as an immediate email. A separate batched pace digest can also summarize your at-pace and off-pace goals once a day, respecting your quiet hours; it never pings you per goal. Manage which goal updates reach you, and how, from your Notification settings.
Two goal triggers let you build rules off goal outcomes.
Goals expose two triggers to the Automations Hub: Goal achieved and Goal at risk. Both fire from the periodic goal evaluation, so you can build a rule that reacts the moment a goal crosses its target or slips behind pace — for example, notify a manager, create a follow-up task, or post an update.
Celebrate a hit goal in a shared channel.
The recommended way to celebrate wins is a single automation: a Goal achieved rule that posts to a team chat channel. Celebrations go to a shared channel, never as a direct message, so the whole team sees the moment a goal is hit.
Closed periods roll into a per-period history, with a short window to catch late data.
As each period closes, the goal's result is recorded into its period history so past performance and streaks are preserved. Because data sometimes arrives late — a deal backdated to last week, an activity logged after the fact — the most recent closed period is re-checked on each evaluation and can still flip to achieved if late data pushes it over target. Once a newer period closes behind it, that period freezes: older history no longer changes.