Lead Source to Commission Tracking for Insurance Agencies
Cost per lead hides the channels that convert. Here's how to tag lead source at intake, carry it onto the bound policy, and calculate cost per bound policy by source instead.
Tracking a lead from source to paid commission means tagging where every lead came from the moment it enters the CRM, carrying that tag onto the quote and the bound policy, and then matching the commission that policy pays against the source that produced it. Agencies that skip this usually find out their marketing is working, or isn't, only by gut feel, because the lead's source gets stripped away somewhere between the first call and the first commission check. The chain has three links, and most agencies already have the first two without a plan for the third: A lead source tag on the contact record, set the moment the lead enters the CRM. An application source on the policy, set when the agent writes the business. A commission record tied to that same policy once it's paid. This guide walks through building that chain step by step, and how to use it to calculate the one number that matters more than cost per lead: cost per bound policy, by source. Step 1: Tag the lead source the moment it enters the CRM Source tracking fails most often at the very first step. A lead comes in from a Facebook ad, a seminar sign-up sheet, a purchased aggregator list, or a referral, and the agent who answers the phone doesn't record where it came from because there's no required field forcing the question. By the time that lead is a client, the source is a guess. Fix this by making lead source a required field on every new contact, not an optional one, with a short, specific list of options rather than a free-text box. This matters most in the first minutes after a lead comes in — see why speed to lead affects everything downstream , including whether anyone bothers to tag the source correctly before moving on to the next call. A free-text "source" field produces a dozen spellings of the same channel within a month and becomes impossible to report on. A dropdown with your agency's actual lead channels, kept to a dozen or fewer options, is what makes the field reportable six months later. Decide up front which of these categories cover your agency's real lead channels, then stop adding new ones for every campaign: Paid digital (search ads, social ads) Organic / website inquiry Purchased lead list or aggregator Seminar or in-person event Referral (client or partner) Direct mail Warm market / personal network Step 2: Carry the source onto the quote and the application The second failure point is the handoff between "lead" and "policy." A lead's source tag often lives only on the contact record, and nothing forces it to travel onto the quote the agent builds or the application they submit. Once underwriting and enrollment take over, the original source is easy to lose, especially if the quoting tool and the CRM are two different systems that don't share fields. The practical fix is to record a source on the policy itself, separate from (but populated from) the contact's lead source. This matters because a policy can outlive several source changes on the contact. A client's final expense policy might trace back to a seminar from a year ago, while a Medicare Advantage policy written on the same contact this AEP came from a referral they made in between. Tracking source at the policy level, not just the contact level, is what lets you report accurately when one contact has multiple policies from different origins. In AgencyView's CRM, this is built into the policy record as an Application Source field, separate from the contact's own Lead Source field, so each policy keeps its own origin even as a contact's history grows. Step 3: Keep the source attached through to the bound policy and commission Once a policy is bound and starts generating commission, the source tag only pays off if someone can actually pull a report that groups commission by source. That means the commission record needs to be linked to the same policy that carries the application source, not reconstructed later from a carrier statement that has no idea where the lead came from. This is the step most agencies never build, because it means two separate systems, a quoting/enrollment tool and a commission ledger, have to reference the same policy number. If your CRM calculates commission off the policy record directly, rather than importing a disconnected spreadsheet, the source tag is already sitting next to the number you need — the same discipline that makes a monthly commission reconciliation possible in the first place. Step 4: Calculate cost per bound policy by source With the chain in place, the report that actually matters is cost per bound policy by source, not cost per lead. Cost per lead treats a $9 purchased lead and a $90 referral-driven lead as equally cheap right up until one converts at 2% and the other converts at 25%. The formula is simple once the chain is built: Cost per bound policy (by source) = total spend attributed to that source ÷ number of policies bound from that source, in the same period. Example: a five-agent agency spends $1,800 in a month on a mix of a purchased lead list and a local seminar series. The purchased list produces 40 leads and 2 bound policies. The seminar series costs $900 of that total and produces 12 leads and 4 bound policies. Dividing spend by bound policies gives a materially different number for each source, even though the raw lead counts alone would have made the purchased list look like the better deal (this is an illustrative example, not a reported outcome from any real agency). Run this by source every month, not just once a year during a budget review. A channel that looked efficient in August can quietly stop converting by October, and cost-per-lead reporting alone won't show it because the lead count can stay flat while bind rates drop. This report sits alongside the other numbers worth checking weekly — see the lead spend report built for a Friday review and building a full KPI dashboard from CRM data for where cost per bound policy fits alongside conversion and retention. Picking an attribution model that fits a small agency Marketing teams at larger companies argue over first-touch, last-touch, and multi-touch attribution models. Most insurance agencies don't need that level of complexity, because the client journey is usually short and the agent who takes the lead is also the one who writes the business. Last-touch (credit the channel that produced the lead that converted) is the simplest model and the right default for a small agency with one or two lead sources per client. First-touch matters more if you run both brand-awareness content (a blog, a podcast, a seminar series) and a separate paid lead channel, since first-touch gives the awareness channel credit for warming up a prospect who later converts through a different path. Multi-touch only pays off once an agency runs enough simultaneous channels, and enough volume per channel, that a client regularly touches two or three sources before binding. Most agencies under a dozen producers aren't there yet, and building a multi-touch model before the data supports it just produces a report nobody trusts. Pick one model, write down which one, and apply it consistently. Switching models mid-year to make a channel look better is the fastest way to lose the team's trust in the report. Common ways the chain breaks The source field is optional. If it isn't required, it gets skipped under call pressure during a busy week, and that week's data is gone for good. The source field is free text. "FB," "facebook," "social," and "Facebook ad" all show up as different sources in the report, and nobody notices until the totals don't add up. The policy doesn't carry its own source. A contact's lead source gets overwritten by a later interaction, and the policy written earlier silently inherits the wrong origin. Commission data lives in a spreadsheet the CRM never sees. If reconciling commission against source means manually matching a carrier statement to a contact list by hand every month, the report won't…
Where AgencyView fits
Keep reading
Share: Facebook · LinkedIn · X · Email
All articles · AgencyView