Call attribution
Dynamic number insertion, explained without the jargon
What DNI changes on a website, how attribution survives the call and when a number pool is worth using.
One website, different numbers, one clear reason
Dynamic number insertion changes the phone number a visitor sees based on how that visitor reached the website. Someone arriving from paid search can see a different number from someone arriving through organic search.
Both calls can still reach the same business. The difference is that the tracking platform can preserve the source behind the call instead of grouping every phone lead into one anonymous bucket.
Static numbers versus a visitor pool
A static source number is simple: one number represents one campaign or channel. A visitor pool temporarily assigns numbers to website sessions, which supports more granular attribution when multiple visitors are active at the same time.
- Use static source numbers when channel-level reporting is enough.
- Use a pool when session or keyword context materially changes decisions.
- Size a pool for realistic concurrent traffic, not total monthly visitors.
- Keep a fallback number in the page so the business remains reachable if the script cannot load.
The installation should fail safely
A DNI snippet should only replace numbers you explicitly mark, should never block the page and should leave the original business number visible when attribution is unavailable. Test the website on mobile, with tracking protection enabled and after the visitor session expires.
Attribution is only useful when it reaches the outcome
The source should remain attached to the call while the team qualifies the lead. Otherwise the business ends up with detailed traffic data on one side and disconnected sales outcomes on the other.