Ask a sales manager which deals keep slipping and you’ll get names before you finish the question. Ask how many times each one slipped and the answer takes longer, because that number usually sits in a history list few people scroll.
Salesforce does keep a count. Every opportunity carries a standard field called Push Count, so you don’t need the custom build the HubSpot version of this paper walks through. The catch is in how Salesforce defines a push. The field counts calendar months crossed, not dates moved. So read Push Count for what it measures, pull the rest from the opportunity’s own history, and put a review rule on top of both.
Does Salesforce track how many times a close date is pushed?
Partly. Salesforce’s Opportunity object reference (Winter ‘27 release) defines Push Count as “the number of times an opportunity’s close date has been pushed out by one calendar month.” Moving a close date from April to May counts as one push. Moving it from April 1 to April 30 doesn’t. And the total doesn’t decrease when the close date moves in, so the count can rise but never fall.
That’s a useful field, and it’s already on every opportunity. The same reference lists Close Date as a required field, so every deal has a date to push from the day it’s created. The question is what the count leaves out.
What Push Count misses
The month rule is the whole story. A move only counts when the date crosses into a later calendar month, which leaves three gaps.
| What happened to the close date | What Push Count shows | Why |
|---|---|---|
| Slipped three weeks inside the same month | No change | The date never left the month |
| Pulled in to an earlier date | No change, and earlier pushes stay on the count | Salesforce doesn’t decrease the total when the date moves in |
| Sat on the last day of a month and slipped one week | One more push | The date crossed into the next month |
The third row matters more than it looks, because it changes how the same slip reads on two different deals.
The month-end case is the common one. Ebsta’s 2023 B2B Sales Benchmarks Report (February 2023) found 89% of close dates were the last day of a calendar month, and 17% of opportunities had their close date changed more than three times by more than a week. When most dates sit on a month end, almost any slip crosses a month boundary and lands on the count. The deals with a mid-month date are the ones whose slips can stay invisible.
One more limit worth knowing: the reference doesn’t say how a jump of several months is counted. Don’t read a Push Count of 1 as one month of slip. Check the history.
Where to see every close date change
Push Count is a summary. The history underneath it lives in two places, and they don’t work the same way.
OpportunityHistory. Per Salesforce’s OpportunityHistory reference (Winter ‘27 release), this object records a change to an opportunity’s Amount, Probability, Stage or Close Date. The system generates a new read-only record whenever one of those fields changes, and its CloseDate field holds the close date from before the update. You don’t have to turn anything on. Two limits: in records created before Winter ‘21, that prior close date is null, so older deals won’t show where the date came from. And if none of those four fields ever changed, there’s nothing to return.
OpportunityFieldHistory. Salesforce’s OpportunityFieldHistory reference (Winter ‘27 release) describes it as the history of changes to an opportunity’s fields, with an OldValue and a NewValue for each change. It only holds fields you track. Salesforce’s Trailhead project on field history tracking says you can track up to 20 standard or custom fields per object, and that tracking logs the date and time of each change, the user who made it, and the old and new values, visible on a record’s History related list or through History reports.
Use the first to see how the close date moved alongside stage and amount. Use the second when you want the person behind every change.
How do you set up close date push tracking in Salesforce?
Put Push Count where people already look, turn on field history tracking for Close Date so each change carries a user and an old and new value, then decide what your team calls a push. Salesforce counts calendar months crossed, per its Opportunity object reference (Winter ‘27 release). If your managers mean any later date, that takes a custom count on top.
- Add Push Count to the opportunity page layout and to the list views reps and managers open in pipeline review. The reference lists the field as filterable and sortable, so a view can rank open deals by it.
- Turn on field history tracking for Close Date. You get up to 20 tracked fields per object, per Salesforce’s Trailhead, so check what’s already using the slots before you add it.
- Put LastStageChangeDate next to Push Count. The Opportunity reference defines LastStageChangeDate as the date of the last change to the Stage field. A deal whose Push Count keeps rising while its stage hasn’t moved in weeks is the one to ask about.
- Pull 20 open deals and compare Push Count with their close date history. Count the slips the month rule missed: same-month moves, and pull-ins that hide behind an old push.
- Decide whether to build a custom count. If step 4 turned up real slips the native field missed, a custom field plus automation your admin builds can count every later date. It adds upkeep, so build it because your sample showed the gap, not by default.
The decision rule is simple. If the history matches Push Count on most of your sample, use the native field and spend the time on the review rule below. If it doesn’t, build the custom count first.
Why does a pushed close date matter for the forecast?
Repeat pushes predict losses. Ebsta and Pavilion’s B2B Sales Benchmark Report 2024, an analysis of 4.2 million opportunities from 530 companies, found opportunities whose close dates moved more than three times saw win rates fall 77%. The same report found 44% of deals slipped, and that when deals slipped, win rates fell 67%, particularly for deals delayed over eight weeks.
Repeat pushes predict losses.
Ebsta and Pavilion’s B2B Sales Benchmark Report 2024
Source: Ebsta x Pavilion, 2024 · 4.2 million opportunities from 530 companies
| Figure | Label |
|---|---|
| 77% | fall in win rate when close dates moved more than three times |
| 67% | fall in win rate when deals slipped |
| 44% | of deals slipped |
Slippage is getting more common, too. Ebsta’s 2023 B2B Sales Benchmarks Report (February 2023), an analysis of 3.2 million opportunities from 364 companies, found 37% of deals slipped in 2022, up 21% year over year. Ebsta and Pavilion’s 2024 report put the share at 44%. Across the two Ebsta reports, the share of deals that slipped rose from 37% to 44%.
Stage tells you what the rep believes. The close date history tells you how often that belief has moved. A forecast built on stage alone treats a deal on its fourth push the same as a deal on its first, and Ebsta and Pavilion’s 2024 report found those two deals don’t close at anything like the same rate. For more on why the forecast drifts from the pipeline, see how to improve sales forecast accuracy, and for where the first optimistic date comes from, why sales reps are bad at forecasting.
The review rule
A count without a rule turns into trivia. The ladder I recommend runs on Push Count plus a quick look at the history (so same-month slips don’t get a free pass):
- First push: the rep adds a note to the opportunity saying what changed on the buyer’s side.
- Second push: the manager asks about it in the next one-to-one.
- Third push: the deal comes out of commit until a buyer-side date replaces the rep’s estimate.
The third rung sits one move before the line in Ebsta and Pavilion’s 2024 report, where close dates moved more than three times saw win rates fall 77%. Acting on the third push gives you one move of warning instead of none. It also takes the judgment out of the room: pulling a deal from commit becomes a rule the whole team knows, not a call the manager has to defend.
Keep Push Count out of compensation and out of public rankings. Once a number like this becomes a scorecard, reps learn to avoid moving the date, and the dates stop meaning anything. We covered that dynamic in your pipeline review is teaching your reps to lie. And when the pipeline in Salesforce and the number in the board deck stop agreeing, slipped dates are one of the places to look, which why your board numbers don’t match your CRM walks through.
Read the count for what it measures
You can keep trusting stage and Push Count as they come, and accept that a three-week slip inside a month reads as zero. Or you can read Push Count as a month counter, check the history for the rest, and put a rule on top that pulls repeat pushers out of commit. The second option costs an afternoon of setup and a few harder one-to-ones. The first one costs you the deals you could have questioned while they were still on their second push.
Close date drift gets harder to see when it sits next to stale stages, missing amounts and fields nobody owns. AeolusGTM is CRM, RevOps and GTM advisory, with Atlas connecting to your CRM to find gaps the CRM can’t show natively. The free CRM Diagnostic works with Salesforce, is read-only, runs 40+ automated checks across data quality, pipeline hygiene and freshness, and returns a scored report within a few hours of connecting.
This week, filter your open opportunities closing this quarter by a Push Count of 2 or more, and count how many sit on a month-end date.