Skip to main content

Call Tracking Setup Guide

How to set up your tracking numbers for the cleanest attribution data. Provider agnostic: CallRail, CallTrackingMetrics, WhatConverts, Invoca, CallCap, ServiceTitan Calls, or anything else.


Every inbound call should hold accurate attribution​

Best practice: Dynamic Number Insertion (DNI) on your website, plus a unique static number on every placement that lives off your website.

Least recommended: one static number shared across your site, your Facebook page, your Google Business Profile and everything else. A shared number tells SearchLight nothing about where the caller came from.

Two rules sit underneath everything below:

  • A unique number on every call campaign. No number, no first lead event, no attribution.
  • Every number forwards one-to-one into its own call campaign in your CRM. The detail then survives a CRM change, and SearchLight can read the campaign from the number dialed.

Dynamic Number Insertion: anywhere the caller is looking at a web page you control​

A script swaps the displayed number per visitor session, so the call inherits the channel, campaign, keyword and click ID of the visit.

  • Main website: one website pool covering paid, organic, direct, referral and social.
  • Paid landing pages and microsites: the DNI script plus the Photon tag on every page your ads point to, with a separate PPC pool.
  • Each brand's site: its own pool, so brands are never conflated.
  • Visitor attribution window: set it to 90 days to match SearchLight's window. CallRail's default is 365 days, which keeps a returning visitor on the number of their first visit for a year.

Without DNI, forms still carry click IDs. It is the call that loses the campaign.

Static numbers: anywhere there is no web page to swap, or the platform requires a fixed number​

One fixed number, one placement. It tells us the source.

  • Google Business Profile: a unique number set as the primary number on each listing, one per location, not the website number. Keep the legacy main line as an additional number. Name it GBP. A tracking number merely listed alongside the main line does not capture the profile's calls.
  • Google Ads call assets: one unique number, only for Google Ads.
  • Microsoft Ads call assets: separate from Google's. Never shared.
  • Performance Max, Smart and Demand Gen: each campaign type gets its own number.
  • Meta / Facebook: a dedicated click-to-call number.
  • Directories: Yelp, Angi, Thumbtack, Nextdoor. One each.
  • Offline: direct mail (per piece), print, radio, TV, billboards, truck wraps, yard signs.

Local Services Ads needs no tracking number. SearchLight takes LSA data directly from Google.

Naming rules​

  • Pools stay neutral. "Website Pool", not a channel name.
  • Static numbers carry the source. GBP, Google Ads Call Ext, Yelp, Direct Mail Spring 2026, Legacy Main Line.
  • No paid keywords on non-paid lines. A legacy line named "PPC" inflates your paid channel.
  • Shared CRM tenant? Put the brand acronym at the end of every call campaign name.

Own your numbers​

  • Port anything sitting in an agency's account.
  • Keep legacy numbers and label them "Legacy". They still book real jobs.
  • Provider not integrated with SearchLight? Forward into ServiceTitan call campaigns and we pull from there.

Minimum vs comprehensive​

Minimum (campaign-level reporting):

  • one website DNI pool
  • one Google Ads call-asset number
  • one unique GBP number per location, set as primary

Comprehensive (full channels and RevSync): everything above, plus

  • a separate PPC landing-page pool
  • PMax, Smart and Demand Gen numbers
  • a Bing call-asset number
  • a Meta ads number
  • Yelp and directory numbers
  • a number per direct-mail piece and offline placement
  • the after-hours or call-center number

Post-launch QA: check it yourself​

  • DNI swap. In an incognito window: click your ad, search organically, type the URL. The number changes each time.
  • GBP. Google your business. The listing shows the GBP tracking number, not the main line.
  • Call assets. A test call from the ad lands in the right CRM campaign. Repeat for Bing.
  • Number inventory. Every number that rings is tracked or forwards to a named CRM campaign.
  • Conversions to spend. Google Ads conversions with zero spend behind them. Over about 20% is a flag.
  • Channel sanity. GBP shows conversions, and "Other" is not one big legacy line.
  • Landing pages. Every ad domain is in the SearchLight configuration with the Photon tag.

Then we take it from there. SearchLight's post-launch QA tells you which number, which campaign, and the fix.

Questions about your own setup? Contact support.