One record for the call and the campaign
Because we are the carrier as well as the tracking platform, the call record and the attribution record are the same record — no reconciliation, no second vendor, no gaps.
Most tracking vendors sit on top of somebody else's carrier
That architecture creates a seam: two contracts, two bills, two support paths, and a reconciliation problem whenever the call record and the tracking record disagree.
NexDial removes the seam. The number is ours, the call is carried on our network, the CDR is written by our platform, and the attribution is attached to that same CDR. There is one source of truth, one invoice and one number to call when something looks wrong.
Dynamic number insertion assigns a number per visitor session, so the campaign, keyword, landing page and referrer travel with the caller through to the call record. Offline sources — print, radio, direct mail, vehicle livery — use static numbers and need no code at all.
Recording and transcription are optional and off by default. When you enable them, announcements are configurable per number so you can meet all-party-consent requirements in the states where you operate, encryption is applied at rest, and retention follows the schedule you set.
- One record. Attribution attached to the same CDR that bills the call.
- Dynamic number insertion. Per-session numbers carrying keyword and campaign through to the call.
- Offline sources too. Static numbers for print, radio and direct mail — no code required.
- Consent-aware recording. Off by default, announcement-configurable, encrypted, retention yours.
- Pushes where you work. Conversions into your CRM and ad platforms via API and webhooks.
What you get
Technical summary
| Number types | Local DID in any US rate centre, or toll-free 8XX |
| Attribution | Session-level, visitor-level and offline source attribution |
| Number pooling | Dynamic pools sized to concurrent sessions, configurable session timeout |
| Recording | Encrypted audio with transcription, retention configurable (default 90 days) |
| Attribution retention | Configurable, default 13 months |
| Routing | Round robin, geographic, time-of-day, skills-based and failover destinations |
| Data role | We act as your processor — see Privacy Policy, Section 5 |
What customers ask
Not when it is configured correctly, and we configure it correctly. Your verified business number stays in your structured data, Google Business Profile and citations. Dynamic numbers are swapped client-side for campaign traffic only, so the canonical number is what search engines index.
Fewer than most people assume. Pools are sized against concurrent sessions, not monthly visits — a site with 50,000 sessions a month rarely needs more than a couple of dozen numbers. We size the pool with you rather than selling you inventory you will not use.
Recording law varies by state and several require all-party consent. The platform supports per-number announcements so you can satisfy each jurisdiction you operate in, and we will help you configure them. Responsibility for consent and announcements remains yours, as set out in our Terms and Privacy Policy.
For call tracking data we act as your processor, not as a controller. We do not use it for our own marketing, we do not sell it, and we do not build advertising profiles from it. Retention is whatever you configure. Section 5 of the Privacy Policy sets this out in full.
You can buy tracking numbers from us and forward them anywhere, so yes. But the main advantage — one CDR carrying both the call and its attribution — only exists when we carry the call too. Most customers start with tracking and migrate the rest once they have compared quality.
Track one campaign and see what it is worth
Buy a handful of numbers, drop in the script and watch the attribution land against real calls. No commitment, no migration required to try it.