“Redtail already tracks our prospects and clients.”
It does. The fees are in billing, and nothing puts the source on the fee.
For Redtail CRM
Export prospects from Redtail, match them against new households and fees, and rank sources on the assets and revenue they actually produced.
Redtail sits on the lead side in CloseRev for an advisory firm: it records the prospect, how they arrived and the household they belong to, while the revenue is a fee on assets that is billed elsewhere, often a quarter in arrears. CloseRev joins Redtail's contacts to the firm's billing or new-asset records on the contact detail and reports new households and fee revenue by source. Revenue with no traceable source is reported as Direct / Unknown.
Page updated September 25, 2026.
The gap
The CRM knows who became a client. The billing system knows what they pay. Nobody has put the source on the fee.
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 contact in Redtail, and on the client record in billing. The contact detail joins them.
How the prospect arrived. The household is the client, not the individual: give every household member's row the same source, so either contact detail joins.
From the custodian or the billing system: what actually arrived, and when.
What the household has paid. One amount is read per row, so run fees as their own import if you also upload assets. It lags the assets, and it is the revenue.
Step by step
Written for somebody with Redtail CRM open in the next tab. Report names vary by edition, so each step says what to look for.
One row per contact with a contact detail, source and the date they first appeared — one row for each household member.
From billing or the custodian: contact detail, amount, date.
A spouse may have been the inquiry and the other partner the account holder. List both in the lead file with the same source, so either contact detail joins.
Assets arrive weeks after signing, and fees follow a quarter or more after that.
The join runs on the phone and the email, normalized, with the first-seen date in the matched-records export for grouping by when the prospect arrived.
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 Wealth Management page — not from a Redtail CRM account.
| Channel | Share | Sales | Revenue |
|---|---|---|---|
| Google Ads | 24 | $168,000 | |
| Email marketing | 18 | $112,000 | |
| Events | 11 | $96,000 | |
| Direct / Unknown | 61 | $424,000 |
Unmatched sales stay in Direct / Unknown. They are never spread across the paid channels to make the total look better.
The argument
An advisory firm's CRM holds relationships: prospects, households, notes, meetings. The fee — a percentage of assets, billed quarterly — is calculated somewhere else.
That separation is sensible, and it means no report inside the CRM can say which source produced revenue, because the revenue is not there.
Joining the CRM's contacts to the billing records on the contact detail brings the two together without either system knowing about the other.
The result is fee revenue by source, which is the number a firm's marketing should be judged on.
Where only new-asset figures are available, rank on those and say so, since assets are what fees are charged on and they arrive a quarter sooner.
Between a signed agreement and money under management sit the account transfers, which take weeks and sometimes arrive only in part.
Then the first fee is billed, often at the end of the following quarter and in arrears.
A report built on signed agreements counts clients whose assets never fully arrived; a report built on billing alone looks a quarter behind every campaign.
The matched-records export carries the prospect's first-seen date, so revenue can be grouped by when the household arrived, whatever the transfer and billing timetable.
Set beside the signed amounts in the CRM, it also shows how much of what was signed actually arrived, per source, which is a useful number of its own.
Advisers serve households: a couple, sometimes a family, often with several accounts under different names.
The person who inquired is frequently not the account holder, and a match that looks only for the inquirer's details misses the household entirely.
With every household member in the lead file under the same source, any contact detail joins, and the household's assets all credit one channel, which keeps the client whole.
Both partners still count as two leads, so read lead counts with that in mind — in a firm growing through couples' referrals it happens often — but the revenue lands on one channel.
A large share of new assets can arrive as retirement plan rollovers, when somebody changes jobs or retires.
Those clients often arrive through different routes from ordinary referrals — an employer relationship, a workshop, a search at a specific moment in life — and they bring larger balances.
Where the firm marks rollover households, mapped as Product / service, the report cuts revenue by it, and the matched-records export shows whether the sources feeding rollovers are a short and specific list.
Knowing that list lets a firm put its effort where the largest single decisions are made.
It also stops a single large rollover from deciding a source's ranking. Balances vary enormously between households, so the report shows the count and the average beside the total, and the matched-records export lists every household, so a source carried by one exceptional household is visible as exactly that.
Fair questions
It does. The fees are in billing, and nothing puts the source on the fee.
Then recording the referrer lets the report rank them on the assets and fees they produced.
Which is why grouping by when the household first appeared — from the matched-records export — beats grouping by billing date.
No. It reads exported files, so your contacts, notes and activities stay where they are.
The lead side. New-asset or fee records from billing or the custodian are the revenue side.
Contacts with a contact detail, source and first-seen date, every household member included, plus new assets or fees by household.
Because the person who inquired is often not the account holder. List every member under the same source, and the household is the client.
Fees where you have them, since they are the revenue. New assets otherwise; say so when presenting it.
Long enough for transfers and the first quarterly bill — often nine months or more. There is no window to set.
Set beside the signed amounts in the CRM, yes, per source, which shows where transfers stall or arrive only in part.
Yes, mapped as Product / service where the firm marks them, and their sources may be distinctive.
Yes, recorded as a source when the prospect arrives, and named in the campaign column so each referrer can be ranked.
Any new household with no traceable source. Its size is stated rather than distributed.
A contact detail, a source and a date on one side; a contact detail, an amount and a date on the other. No account numbers, no holdings, no notes, no financial plans. Encrypted in transit and at rest and deleted with the import.
New assets or fee revenue per source, households kept whole, first-seen dates in the matched-records export, 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.
Redtail CRM 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
The export is the part of an attribution project that everyone treats as trivial and that determines whether the whole thing works. Here is the field list, the date-range trap, the deduplication rule, and the six columns to leave out on purpose.
Read the articleEvery attribution vendor quotes a match rate and none of them define it the same way. Here is what the number actually measures, what range is honest for a mid-market business, and the three ways the figure gets inflated before it reaches your slide.
Read the articleA big unattributed bucket is not a broken report. It is a measurement — and there are only four things it can be. Here is how to read it, how to shrink it, and why any tool that hides it is lying to you politely.
Read the articleStart today
Nothing to install in Redtail CRM, no API key, and no need to have been tracking anything until now. Last year works as well as this month.