“Birdeye already reports conversations and reviews.”
It does, thoroughly. It has no view of what was sold, because it never sees the ledger.
For Birdeye
Export Birdeye conversations as your lead file, match them against closed revenue, and find out what the widget and the listings are worth.
Birdeye handles reviews, listings and messaging, so in CloseRev it sits on the lead side rather than the revenue side. Its webchat and text conversations export as a lead file with a contact detail and a date, which can then be matched against closed sales from whatever system holds them. What it cannot do — and no honest tool can — is trace an individual customer back to a review somebody else wrote. Revenue with no traceable lead is reported as Direct / Unknown.
Page updated September 24, 2026.
The gap
Reputation software reports conversations, review volume and response times. None of those are revenue.
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 record. Webchat and text conversations usually capture a mobile number, which is the better key.
Webchat, SMS, Google Business Profile messaging, Facebook. Each becomes its own source rather than being pooled as one.
When the conversation started; it decides which of a customer's leads came first.
Not read on the lead side. Put the location in the source name if you want it there, or map a location column in the sales file as Location.
Step by step
Written for somebody with Birdeye open in the next tab. Report names vary by edition, so each step says what to look for.
One row per conversation with a contact detail, the channel and the date it started.
Webchat on your own site and a message from a map listing are different sources with different intent. Pooling them hides the answer.
From whichever system holds it — practice management, field service, point of sale. Contact detail, amount, date.
Days past the conversation for a repair, months for anything considered. There is no window to set: the earliest matching lead is credited however long before the sale it arrived.
The join runs on the phone and the email, 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 Multi-Location Retail page — not from a Birdeye account.
| Channel | Share | Sales | Revenue |
|---|---|---|---|
| Google Ads | 4120 | $1,470,000 | |
| Meta Ads | 3140 | $1,120,000 | |
| Email marketing | 2551 | $910,000 | |
| Direct / Unknown | 9812 | $3,500,000 |
Unmatched sales stay in Direct / Unknown. They are never spread across the paid channels to make the total look better.
The argument
A chat widget collects a name and a number from somebody already on your site, which makes it one of the cleanest lead files a business has.
It is also routinely excluded from attribution because it is not a form and not a call, so it appears in neither the web analytics funnel nor the call tracking report.
Exporting conversations and matching them against closed revenue puts the widget in the same comparison as every paid channel.
The widget may turn out to be doing real work. Where a visitor's ad click is in the file too, the earlier of the two is credited, so the widget is not handed customers the paid channels already bought.
Somebody messaging from a map result is choosing between you and the two businesses beside you. Somebody chatting on your site has already arrived.
Pooled into one messaging number, those two intents cancel each other out and the report says nothing useful.
Kept apart, the map channel becomes measurable on revenue, which matters because it is usually the one nobody has ever costed.
It is also the channel most affected by review volume and listing accuracy, which is where the rest of the product earns its keep.
A strong rating changes how many people choose you from a map result, and that effect is real, large and slow.
It is also untraceable at the individual level: no customer in your file can be linked to the review that influenced them, because they never interacted with it in a way anything recorded.
The honest treatment is to measure the map and directory channel accurately on revenue, and read it against review activity over months rather than manufacturing a per-customer link.
Any tool claiming to attribute revenue to a specific review is guessing, and a guess presented as attribution is worse than a stated gap because nothing warns you when it is wrong.
Review counts, response times and conversation volume are reported per location because that is how the software is organized, but revenue rarely is.
Without the revenue side, a location with excellent engagement metrics and poor conversion looks like a success, and the group average hides both.
Where the sales export carries a location, mapped as Location, the report splits revenue on it, and the locations separate on the only measure that matters.
It can also point at the operational problem this category often has — conversations nobody answered quickly enough at one site while the group average looked fine — which Birdeye's own response times will confirm. That is a staffing decision rather than a marketing one, and it is invisible in every report that stops at the conversation.
Fair questions
It does, thoroughly. It has no view of what was sold, because it never sees the ledger.
No, and nothing honestly can. The report measures the map and directory channel on revenue and reads review activity against it over months.
Then the conversation export is still the lead file, and it is the only way to judge what that service is producing.
No. It reads a file you exported, so your inbox, review responses and message history are not reachable from here.
The lead side. Closed revenue from your own system is the other side.
Conversations with a contact detail, the channel and the date the conversation started.
No. A map-listing message and a webchat on your own site are different intents and should rank separately.
Not per customer, by anyone. The map channel is measured on revenue and read against review activity over months.
There is no window to set. Let the revenue file run past the conversations by as long as your sale takes — days for a repair, months for anything considered.
Yes, where the sales export carries one, mapped as Location — and for a group that split is usually the reason to do this.
They stay in the file. A channel's cost includes the conversations that produced nothing.
Yes. The earliest of their leads takes the credit.
It cannot be matched, and it is reported as unmatched rather than assumed to have produced nothing.
A contact detail, 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, no notes. Encrypted in transit and at rest and deleted with the import.
Revenue per messaging channel and per location, the map and directory channel measured on money, 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.
Birdeye 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
For 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 articleText 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 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 Birdeye, no API key, and no need to have been tracking anything until now. Last year works as well as this month.