Connect CallRail to SiteOps

For a dentist, an HVAC company, a dealership or an insurance broker, the sale doesn't happen in a form — it happens on the phone. CallRail sits between your marketing and that phone: it swaps in tracking numbers so every call carries the ad, page or keyword that earned it. Without it, the conversion your business actually lives on is invisible, and your cost-per-lead is a guess.

Connecting CallRail to SiteOps counts those tracked calls as leads, read-only. A call that came from a Google Search ad joins your Leads number the same way a form fill would — so the CPL you see is a real cost-per-call, not a click proxy. When the goal type is set to Leads, this is the number the whole dashboard leans on.

It stays a window, never a hand on the controls. SiteOps reads your call reports; it never places a call, changes a tracking number or touches a recording. If you disconnect, the reads stop the same minute.

Calls flow in, read-only — SiteOps never places a call

Set it up, step by step

0 of 4 done

1. Numbers
2. Tracking numbers
1. Settings
2. Integrations
3. API keys
1. Settings
2. Connections
3. CallRail

If something does not work

Calls aren't showing up as leads: Check three things: the connection reads Connected in Settings; the API key is an account key with read access (not a company-scoped one that can't see this business); and CallRail is actually logging calls on a live tracking number. A brand-new number with no calls yet simply has nothing to read.
My lead count looks too high: By default every tracked call counts once. If repeat callers are inflating things, SiteOps separates first-time from repeat calls — read the first-time number as your new-lead count and the total as overall volume.
Does connecting CallRail place calls or change my numbers?: No — deliberately. The key is read-only; there is no code path that dials out, edits a tracking number or touches a recording. CallRail stays exactly as your team set it up.
The source on a call is blank: CallRail can only attribute a call when its tracking script and number swap are live on the page the caller came from. Calls to a static, un-swapped number arrive with no source — SiteOps still counts them as leads, just without the ad or keyword.

What it unlocks

Tracked phone calls counted as leads — the true cost-per-call for a business the phone closes, next to your ad spend.
First-time versus repeat calls kept apart, so a returning customer doesn't inflate your new-lead count.
The source of each call — ad, page, keyword — carried through, so budget can lean toward what actually rings the phone.
The Leads hero KPI lights on a real conversion source instead of warning that the outcome is unmeasured.

Before you start

A CallRail account with at least one tracking number already collecting calls for this business.
An account-level API key — CallRail issues it under Settings, then Integrations, then API keys. Read access is enough.
Two minutes. There's no consent screen to click: you paste a read-only key and press Save.

Quick links

What SiteOps reads

Calls — count, first-time versus repeat, and the source (ad, page, keyword) that earned each one.
Cost signals — enough to compute a true cost-per-call against your connected ad spend.
SiteOps writes nothing to CallRail: no numbers changed, no calls placed, no recordings touched.
Disconnecting in SiteOps, or revoking the key in CallRail, cuts access instantly.

Connect CallRail to SiteOps

Set it up, step by step

If something does not work

Set up once, see everything every morning