Track every call back to
the click that earned it.
Dynamic Number Insertion stitches the right number to every visitor. Every inbound call resolves to ad source, keyword, creative and landing page — in 14 ms, before the agent picks up.
Dynamic Number Insertion · live attribution
LiveFrom caller to closed-loop in milliseconds.
Place tracking pool
Drop our DNI script on your landing pages. We swap the displayed number per visitor session, drawing from local-area pools.
Visitor calls
When the call lands, our system matches caller ID and DID back to the originating session in real time.
Attribution stitched
Source, campaign, ad-set, keyword, creative, UTM and visitor session are bound to the call record before it routes.
Signal flows back
Closed-loop conversions push to Google, Meta, Bing, TikTok and your CRM via server-side APIs.
Every moving part.
Dynamic Number Insertion
Per-visitor number swaps from local-area DID pools, with TTL and reuse rules.
Visitor session stitching
First-party identity tied to call within 14 ms — works without third-party cookies.
Multi-channel attribution
Native connectors for Google, Meta, Bing, TikTok plus a programmable webhook for everything else.
Keyword & creative resolution
Drill down to the exact keyword, ad-set and creative variant that drove the call.
UTM & custom params
Capture any URL parameter or session variable and bind it to the call record.
CRM & webhook routing
Route call events to Salesforce, HubSpot, Zoho, Slack or any HTTPS endpoint with retries.
The teams that live by inbound calls.
Insurance lead-gen
Bind every quote call to the keyword and creative that earned it.
Mortgage marketers
Track refi calls down to the lender campaign and ad creative.
Home services
See which Google Local Service ads are actually generating booked jobs.
Legal intake
Mass-tort intake firms tracing every call to the campaign that drove it.
What teams always ask.
Pool size scales with your peak concurrent visitor count, not total traffic. Most US lead-gen teams run with 50–500 numbers per campaign group, with TTLs that recycle the pool every 10–30 minutes.
Yes. The call event is hashed and pushed via Google Ads server-side enhanced conversions, including gclid, click_id, hashed phone and email. Same pattern works for Meta CAPI, Bing UET and TikTok Events.
Identity is captured first-party on your domain — no third-party cookies, no client-side beacons that ad blockers strip. Stitching happens server-side once the call lands.
Yes. Bring your own toll-free or local DIDs via SIP registration or porting. Pulse handles the DNI logic on top of any number you already own.
p50 stitching is 14 ms, p95 under 40 ms — measured end-to-end from call ingress to attribution write. Server-side fan-out to ad platforms typically clears within 500 ms.
Related Pulse capabilities.
Your next revenue conversation
is already ringing.
Spin up tracking, telephony and AI in a single platform — the way modern US revenue teams do it.
7-day free trial · No credit card · Cancel any time