“Denticon already reports new patients by office.”
It reports patients first seen at each office. It cannot tell an acquired patient from a won one, or say which campaign produced either.
For Denticon
Export collections from Denticon, upload the leads behind them, and rank sources on the patients the group actually won — office by office.
CloseRev reads a Denticon export of collected payments — the patient's phone or email, the amount, the date and the office — and matches it against the campaigns, calls and bookings that produced the first appointment. Dental groups on a shared database grow two ways, by winning new patients and by acquiring practices that bring patients with them, and an honest report has to tell those apart before it credits any marketing. Collections with no traceable lead are reported as Direct / Unknown.
Page updated September 25, 2026.
The gap
The group's new-patient number jumps every time it buys a practice, and the marketing report takes the credit.
What was sold, to whom, and for how much.
The click, the keyword, the call, and what each one cost.
The file
Three things carry the match: who, how much, and when. Anything else is optional and only changes how the report can be sliced.
On the patient record in the shared database, which is what lets one patient be recognized across offices.
Payments received from patients and insurers together.
When money arrived, and the office, mapped as Location. CloseRev does not read the first-visit date, so use it yourself to tell a new patient from an inherited one before uploading.
Not read by CloseRev. Use it before uploading: patients first seen before that date came with the practice, and can be left out or marked as Product / service.
Step by step
Written for somebody with Denticon open in the next tab. Report names vary by edition, so each step says what to look for.
One row per payment with a contact detail, the amount, the date and the office.
It is how you mark an acquired practice's existing patients before uploading, so they never pass as new.
Brand campaigns run for the whole group, local campaigns per office, and the central call center's booking records.
Treatment plans complete over months, and recall is where the second year's revenue sits.
The join runs on the phone and the email, normalized, with revenue cut by office, mapped as Location, and reported for the group.
What comes back
Revenue by channel, the count of sales behind each figure, and an honest bucket for the ones nobody could trace. Sample figures, from the worked example on the Dentists page — not from a Denticon account.
| Channel | Share | Sales | Revenue |
|---|---|---|---|
| Google Ads | 38 | $124,800 | |
| Meta Ads | 31 | $54,800 | |
| Email marketing | 14 | $27,400 | |
| Direct / Unknown | 46 | $97,400 |
Unmatched sales stay in Direct / Unknown. They are never spread across the paid channels to make the total look better.
The argument
When a group buys a practice, the practice's existing patients move into the group's database. In a naive report they appear as new patients in the month the practice joined.
Every campaign running that month then looks extraordinary, and the group's marketing is credited with growth it bought rather than won.
The fix is to record when each office joined and mark patients first seen before that date as inherited, whatever their record's created date says, before uploading — CloseRev reads neither date.
Marked as Product / service, inherited and won patients become two honest revenue lines: how much marketing won, and how much came with acquisitions.
For a group growing by acquisition, the first number is the one that shows whether the marketing works at all.
A group often runs some marketing centrally for all its offices and lets offices, or regions, run their own.
Credited together, a brand campaign's patients get attributed to whichever office they happened to book at, and a local campaign's results get blended into the group's.
Putting the campaign's level in the campaign value lets the drill-down show central campaigns against the revenue they produced across every office, and local ones against their own.
That is the split a group's budget is actually set on, so it is the one worth setting up.
It also settles a recurring argument inside groups: whether the central marketing team is producing patients for the offices or taking credit for what the offices would have won locally. With both levels on the lead file, the answer is a number rather than a debate.
Many groups book appointments through a central team rather than each office's front desk, and that team's records hold the caller, the date and often how they heard about the group.
Those records are the most complete lead file a group has, and they are often never joined to the collections that followed.
Exporting them alongside collections gives revenue per booking by source, across every office the call center serves.
Set beside the center's own booking counts per office, it also shows which offices convert the bookings it sends, which is an operations finding rather than a marketing one.
A patient who moves house or switches to an office nearer work is still one patient, and a shared database recognizes them as one.
A report that counts patients per office without that recognition would count the move as a new patient at the second office.
Matching on the patient, not the office, keeps them attached to the source that first produced them, and each payment still carries the office it was made at.
It is one of the practical advantages of a group on a single database, and it makes the group's attribution cleaner than a collection of separate practices could produce.
Fair questions
It reports patients first seen at each office. It cannot tell an acquired patient from a won one, or say which campaign produced either.
Then separating inherited patients is what makes the marketing figure honest, and it may be much smaller than it looks.
It tracks bookings. Joining them to collections is what says which sources produced revenue.
No. It reads a file you exported, so your charts, schedules and database stay where they are.
Collected payments with a patient contact detail, the amount, the date and the office.
Mark patients first seen before the office joined the group before uploading — as Product / service, or by leaving them out. Without a lead in the file, their collections land in Direct / Unknown rather than crediting marketing.
Because a record's created date is the day it entered the database, which for an acquired practice is the day of the acquisition. CloseRev reads neither date; the marking happens in the file.
Yes, with the level in the campaign value of the lead file.
Yes, and they can be the most complete lead file a group has.
Yes, mapped as Location — by office, or by region where the export carries one.
They stay one patient, credited to the source that first produced them, with each payment carrying its office.
A year or more, so treatment plans complete and recall appears. There is no window to set.
Any collection with no traceable source, inherited patients included.
CloseRev does not sign HIPAA Business Associate Agreements and is not built for protected health information. Export only non-clinical fields from Denticon — a phone or email, the amount and the date — never diagnoses, treatments or notes. If those contact fields count as PHI under your obligations, talk to your compliance lead first.
Collections by source, cut by office, inherited patients apart where marked, central and local campaigns apart where labeled, and everything unmatched kept visible.
By trade
What the report looks like once the export is in, written for each one.
Other systems
Running more than one system, or comparing? The method is the same and the columns are not.
Denticon and the other product names and logos on this page belong to their owners and are shown to identify the software a file comes from. CloseRev is not affiliated with or endorsed by them, and connects to none of them: it reads a file you export.
From the blog
Multi-site healthcare groups usually conclude that attribution is off limits because the data is clinical. It is not, because attribution does not need clinical data. What it needs is a phone number, an amount and a date, and there is a way to handle even those properly.
Read the articleA multi-location business that reports one national attribution number is hiding its most important finding. The same campaign performs differently in every market, and the aggregate is an average of things that should never have been averaged.
Read the articleBefore you blame the matching algorithm, look at how phone numbers are stored on each side. Extensions, country codes, leading zeros and a spreadsheet that decided a number was maths — this is where most attribution quietly fails.
Read the articleStart today
Nothing to install in Denticon, no API key, and no need to have been tracking anything until now. Last year works as well as this month.