PipelineSignals

Guides / Call attribution

Phone-call attribution

Med spas, dentists, home services — the best leads often ring instead of typing. Those calls normally leave zero trace for your ad platforms. Now they do.

⏱ About 2 minutes to set up
1

What you need probably already done

  • Our capture script on the website visitors browse before calling
  • Inbound calls landing in your CRM (a phone number in the sub-account, so calls create contacts and call records)
2

Tell us the website's domain the one setting

Open the location in Pipeline Signals → Call attribution → enter the site's domain (e.g. clinic.example.com) → save. This scopes matching strictly to that client's own traffic.

3

How the matching works and when it declines

When someone clicks an ad and browses the site, we note the visit (no personal data — just click IDs and timestamps). If a call comes in while they're on the site or within 15 minutes of their last page view, and theirs is the only ad-visit in that window, the caller inherits the full click attribution — as if they'd filled a form.

If two ad visitors are on the site at once, we decline to guess. The call still reports to Meta matched by the caller's (hashed) phone number — a genuine match key, just a weaker one. A wrong click ID would poison your ad account's learning; a declined match never does.

📈

Why this is rarely ambiguous in practice: local-service businesses seldom have two simultaneous ad-click visitors — the unique-visitor condition holds for the vast majority of calls. High-traffic national sites are a different story; talk to us about dedicated tracking numbers if that's you.

Pipeline Signals · dedup, retries, expiry windows and consent flags handled automatically