Call tracking for real estate investors: every seller call tied to the campaign that rang the phone

Why are phone calls your biggest blind spot?

Marketing for sellers is full of channels that end in a call: direct mail, yard and bandit signs, cold-call callbacks, text blasts, a Google Business Profile listing, a pay-per-click ad with a call button. A form submission carries the page and the campaign with it. A call arrives as a phone number and a voice. Without tracking, the source of every call comes from what the seller remembers and what a rep types, which are both unreliable. The cost shows up in your attribution: calls are often the best leads, and they end up filed as "unknown" or "referral". You then cut the channel that was working or fund the one that only looked good on forms. The attribution rules for what to do with the data are in which campaign gets credit.

What are the two kinds of tracking number?

These are the two types call-tracking vendors offer; I'll use CallRail's definitions as one example, and other vendors work the same way.

• Source tracking number: a single, static number that tracks one source, such as one mailer wave, a billboard or a Google ad extension. Every call to it is that source.
• Website pool with dynamic number insertion (DNI): a set of numbers that a small script swaps onto your web pages in place of your normal number, based on how each visitor arrived. It stores the source in a cookie so the same visitor sees the same number on return visits. A pool captures visitor-level detail such as pages visited and paid keywords, which source numbers can't.

One practical caveat on DNI: the script looks for your phone number on the page, so the number must be visible in the page's HTML or an image in a normal format such as (111) 222-3333.

Which number should each channel use?

What should each call write to Salesforce?

• Source and campaign from the number dialed, mapped to a Salesforce campaign. This is what makes cost per contract a normal report.
• Caller's phone number, in the cleaned format your duplicate rule matches on.
• New or returning caller. A call from a known seller should reopen their record and notify the owner, not create a new lead (see duplicate seller leads).
• Call duration, direction and a recording link, for coaching and for settling "I never got a call back" arguments.
• For web pool calls, the keyword or landing page, when your vendor provides it.
• Missed or unanswered flag, which should create a callback task straight away; see missed-call alerts.

How data reaches Salesforce depends on the vendor. CallRail's page for its Salesforce integration says calls are tied to campaigns and recordings can be listened to in Salesforce, and lists a Salesforce Enterprise or Unlimited plan as a requirement. If your edition doesn't qualify, a Zapier or webhook connection that writes the same fields can do the job; see Salesforce integrations and Zapier with Salesforce. Check the vendor's current requirements before you buy.

What is the setup, in order?

1. List your channels and decide how finely you want to split them. One number per mailer wave is plenty; one per envelope color is not.
2. Buy and label numbers in a naming scheme that sorts (channel, market, month).
3. Create a Salesforce campaign for each and store the number on it, so incoming calls can look up their campaign.
4. Route every number to your real line and play a short recording notice if you record (see the note on recording below).
5. Install the website script and check that the number swap works on every page that shows a phone number.
6. Connect to Salesforce, test with five calls from different phones, and check that each lands on the right record with the right campaign.
7. Add the numbers to your SOPs so no one prints a mailer without a tracked number; see SOPs inside your CRM.

What goes wrong?

• Releasing a number too soon. A seller may keep a letter for months. Keep printed numbers live until you're sure the campaign is dead, and forward them to your real line.
• Too many numbers. Split sources only as far as you will report on them.
• Tracking the first touch and ignoring the rest. A seller can see a sign, get a letter and call after a text. Decide your credit rule before you read the report.
• Creating a lead for every call. Repeat callers and wrong numbers inflate counts; match on phone first.
• Recording laws. States differ on consent to record calls, and several require all parties to agree. Add a recording notice at the start of tracked calls, and check the rules for the states you operate in. This is information, not legal advice.
• Treating the call as the lead's start. If the call went unanswered, the clock for speed to lead began when it rang.

What reports should call tracking give you?

1. Calls by source and market, weekly, with answered and missed split.
2. Calls to appointments to contracts by source. The reason to track at all.
3. Cost per call and cost per contract by campaign, using the spend on each campaign; see the cost per deal calculator.
4. Missed calls by hour, which tells you when to staff the phone.
5. Share of "direct" or "unknown" calls. If it creeps up, a channel is missing a number.

Questions

Related guides

Sources

Vendor details were read from the vendors' pages in October 2026 and change; check the linked pages. CallRail is an example, not a recommendation. Compliance notes are information, not legal advice.

1. CallRail Support: Dynamic number insertion overview. How DNI works; source tracking numbers vs website pools; number must be visible on the page
2. CallRail: Salesforce integration. Calls tied to campaigns, recordings in Salesforce; Lightning Enterprise or Unlimited plan listed as a requirement