“Podium already reports conversations and reviews.”
Thoroughly, and it has no view of what was sold, because it never sees the invoice.
For Podium
Export your conversations, match them against closed sales, and find out what texting actually produced.
Podium sits on the lead side in CloseRev: its text conversations carry a mobile number, a start date and usually a channel, which makes them a clean lead file. Matched against closed sales from whichever system holds them, they answer what the texting widget and the review program were actually worth. Revenue with no traceable conversation is reported as Direct / Unknown.
Page updated September 24, 2026.
The gap
Response times and conversation counts are reported daily. Revenue from them is reported never.
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 conversation. The customer entered it to receive a text, which makes it verified in a way a form field never is.
Website widget, map listing, missed-call text-back, campaign. Each is a different intent and should rank separately.
When the thread started, which decides which of a customer's leads came first.
Not read from the conversation file; map the location on the sales side, where it turns a group number into a manager's decision.
Step by step
Written for somebody with Podium open in the next tab. Report names vary by edition, so each step says what to look for.
One row per conversation with the mobile number, the channel and the date it began.
A missed-call text-back and a website chat are different events. Pooled, they cancel each other out.
Contact detail, amount, date, from the system that invoices.
Weeks past the conversations for a repair, months for anything considered. There is no window to set.
The join runs on the mobile number, normalized, with unmatched conversations kept visible.
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 Auto Repair Shops page — not from a Podium account.
| Channel | Share | Sales | Revenue |
|---|---|---|---|
| Google Ads | 203 | $101,500 | |
| Local service ads | 142 | $77,000 | |
| Meta Ads | 61 | $24,500 | |
| Direct / Unknown | 289 | $147,000 |
Unmatched sales stay in Direct / Unknown. They are never spread across the paid channels to make the total look better.
The argument
Most lead files hold a number somebody entered into a form, which can be mistyped, deliberately wrong or a work number for a personal purchase.
A texting conversation only exists because the customer entered a number they actually use and then received a message on it.
That makes this one of the highest-yield lead files in the catalog, and worth exporting even when another system is the primary source.
Match rates against a customer record can be correspondingly high, which means less revenue disappears into Direct / Unknown for want of a usable key.
Where the sale system holds an older number, normalization runs on both sides and the matched-records export shows which key joined rather than dropping the row.
When a call goes unanswered and an automatic text follows, the resulting conversation is with somebody another channel already produced.
Counted as a source, it takes credit for revenue that search, the map listing or a referral actually generated.
The honest treatment is to label it as its own source, recovery, combined with the call-tracking or form leads in one lead file: the earliest lead takes the credit, so a customer another channel produced stays with that channel, and the recovery line shows what came through it alone.
That figure can be large enough to justify the tool on its own, and it is a staffing argument rather than a marketing one.
Pooling it into a single messaging channel hides both findings at once.
A review program raises a local rating, and the rating changes how many people choose you from a map result weeks later.
That effect is real and untraceable at the individual level, because no customer in your file interacted with somebody else's review in a way anything recorded.
The defensible reading is to measure the map and directory channel accurately on revenue and watch it against review activity over months.
Any tool claiming to attribute revenue to a specific review is guessing, and a guess presented as a measurement is worse than a stated gap.
The report does the measurable half properly and declines the other half explicitly.
Conversation volume and response times are reported per location because that is how the tool is organized; revenue usually is not.
A site with excellent response times and poor conversion looks like a success, and the group average conceals both it and the site subsidizing it.
Where the sales export carries a location, mapped as Location, the report cuts revenue by it and the sites separate on the only measure that matters.
The finding can be operational — one location answering slowly while the group average looked fine — which is cheaper to fix than any channel change.
Response time is the variable to look at first, because in a texting channel the customer is holding the phone. A reply within minutes and a reply the next morning are not the same business, and the revenue difference between them can be larger than the difference between any two sources in the file.
Fair questions
Thoroughly, and it has no view of what was sold, because it never sees the invoice.
No, and nothing honestly can. The map channel is measured on revenue and read against review activity over months.
It is, and it is also the cleanest lead file most local businesses have. Both things are true.
No. It reads an exported file, so your inbox, message content and review responses stay where they are.
The lead side. Closed sales from your own system are the other half.
Conversations with the mobile number, the channel and the date the thread began.
Because the customer entered a number they actually use and received a message on it, which a form field never verifies.
No. A website chat and a missed-call text-back are different events and should rank separately.
As its own source, labeled recovery, combined with the other leads so the earliest one takes the credit; what remains on the recovery line is revenue from unanswered calls no other channel produced.
Not per customer, by anyone. The map channel is measured on revenue instead.
Yes, mapped as Location from the sales export, and for a group that can be the reason to run it.
They stay in the file. A channel's cost includes the threads that produced nothing.
Both sides are normalized and the email is used as a second key where present; a sale that still does not join stays visible in Direct / Unknown.
A mobile number, a channel and a date on one side; a contact detail, an amount and a date on the other. No message content, no review text. Encrypted in transit and at rest and deleted with the import.
Revenue per conversation channel, cut by location where you map one, recovery as its own labeled source, 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.
Podium 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
Text messaging is two channels wearing one name: inbound texts that are leads, and outbound campaigns to a list of people who already know you. The second is where the reported revenue lives, and most of it is credited on delivery rather than on anything the customer did. Here is how to tell the two apart, what the platforms actually count, and how to measure what a text adds rather than what it arrived before.
Read the articleFor a local business the Google Business Profile is often the busiest front door it has: the call button, the directions, the website link. It reports taps, not customers, and since July 2024 it no longer keeps even a list of who rang. How to find out what the listing is actually worth.
Read the articleCall tracking answers one question well: which campaign produced the ring. It has no view of what happened after the call ended, which is where the money is decided. This is what the gap costs, and how to close it without replacing the call tracker you already have.
Read the articleStart today
Nothing to install in Podium, no API key, and no need to have been tracking anything until now. Last year works as well as this month.