Before you start: mark your won and lost stages
The report can only count wins and losses if it knows which stages mean them. On the pipeline board, open a stage’s settings (the cog on its column) and set Counts as to Won or Lost. Leave every other stage on In progress.1
Open the pipeline
Go to Contacts and switch to Pipeline View.
2
Open a stage's settings
Select the cog at the top of the column you close deals in, for example Customer.
3
Choose what it counts as
Set Counts as to Won, then Save. Do the same with Lost for a stage such as Not interested, if you keep one. The column header then shows a small Won or Lost label.
Open the report
1
Open Reports
In the sidebar, under Configurations, select Reports, then the Pipeline tab. It sits between Finance and Ads. You can also select Pipeline report at the top of the pipeline board.
2
Pick your dates
Set From and To. Leave both blank and the report covers the last 30 days. Days follow your business’s timezone, not UTC.
3
Filter by teammate
Assigned to narrows the report to the contacts one teammate held, or to Unassigned contacts. It uses whoever the contact was assigned to when they entered each stage, so reassigning a contact later does not rewrite who held the earlier stages.
The cards
The stage table
One row per stage, in the same left-to-right order as your board.Entered, Moved on, Won and Lost follow the same people. The report takes the contacts who entered a stage in your dates and follows them up to today. Someone who entered on the last day of your dates and moved on the next morning still counts as moved on.Times only count finished stays. A contact still sitting in a stage has no finished time yet, so they count under In stage now and Avg time so far instead of pulling the average down. The median is the middle stay, which is often a better guide than the average when one deal sat for months.
When the history starts
DMLY records a contact’s stage moves from the day this report was added to your workspace. Earlier moves were never recorded, so they cannot be reported. The report says, at the top, the date its history starts. Contacts who were already in a stage on that day count under In stage now, but nobody knows how long they had already been there, so they are left out of every time figure and are not counted as entering that stage. The report says this too, with the date. Once such a contact moves to another stage, that move is recorded and counted normally.What counts as a move
Every way a contact changes stage is recorded: dragging a card on the board, the Pipeline stage picker on a contact, the contact form, bulk Set stage, the Update Contact Stage automation step, the A.I. Move CRM stage tool, the API, a CSV import that sets a stage, and creating a contact with a stage. Three things end a stay without counting as a move, a loss or a finished time:- Removing the stage. Clearing a contact’s stage counts as removed (in the hover breakdown), and the stay counts as finished.
- Deleting a stage. Its contacts move to No Stage. Their stays end, but the deleted stage no longer appears in the report.
- Merging two contacts. The merged contact keeps both people’s history. If they were in different stages, the duplicate’s stay ends and is not counted as a finished time.
Export
CSV downloadspipeline-report.csv: one row per stage with Stage, Outcome, Entered, Moved on, Moved back, Removed, Still in stage, Reached won, Lost, Conversion %, Completed stays, Avg days in stage, Median days in stage, In stage now and Avg days so far. Times are in days, to two decimals. PDF gives you the same report as a document. See Export your data.
Exporting needs the Export reports permission; viewing the tab needs any Reports permission. See Roles and permissions.
Related
Pipeline stages
Set up your stages and mark which ones mean won or lost.
Export your data
CSV, PDF and the combined workspace report.

