Should we use dynamic number insertion or a static tracking number per channel?
Both, for different jobs. Static numbers are one number per source: cheap, durable, and enough to separate channels. Dynamic number insertion swaps the number per visitor session, which is what you need for campaign and keyword detail. Use static numbers on placements you do not control, such as print, vehicles and directories. Use dynamic insertion on the website, and size the pool for concurrent sessions rather than monthly visits.
What each one can and cannot resolve
A static number resolves to whatever you assigned it: the yard sign, the mailer, the truck wrap, the directory listing. It never expires and it never collides. Its limit is granularity. One number equals one bucket, forever.
Dynamic insertion resolves to a session, which means it can carry campaign, keyword, landing page and referrer. Its limit is supply. Numbers are borrowed from a pool and returned after a hold period, so the same number can represent different sessions on different days.
Sizing the pool is the part people get wrong
The pool needs to cover concurrent sessions during your busiest hour, held for the length of your attribution window, not average traffic. If a number is held for a week after the visit and you get a heavy Monday morning, a small pool runs out and sessions start sharing numbers.
The failure is silent. Nothing errors. You simply get calls attributed to the wrong session, and the error concentrates in your highest-traffic periods, which are exactly the periods you are trying to analyze. If your call platform reports pool utilization, watch the peak rather than the average.
A related detail: decide how long a number stays assigned after the visit. A short hold recycles numbers quickly and stretches a small pool, but it cuts off calls placed a day later. A long hold captures delayed calls and consumes far more numbers. Choose the hold from your own distribution of time between visit and call, which call data can show you directly.
Number swapping and your local listings
Contractors reasonably worry about consistency between the phone number on the website and the number in local listings. The usual practice is to keep the real business number as the canonical one in structured markup and in your local listings, and let the swap apply to the visible number for tracked sessions only. Discuss the specifics with whoever manages your listings, because implementations differ.
The second consideration is call routing. Every tracking number is a forwarding hop, so verify caller ID passthrough, voicemail behavior and after-hours routing before you roll it out. Attribution that breaks call handling is a net loss.
A reasonable default configuration
- One static number per offline placement. Print, direct mail, vehicles, sponsorships, yard signs.
- One static number per uncontrolled online listing. Directories and aggregators that will not honor a swap.
- Dynamic pool for the website. Sized on peak concurrency, covering paid, organic and referral sessions.
- Your real number stays reachable. Long-time customers dial it, and those calls should be visibly bucketed as unattributed rather than assigned to a channel.
Topics: dynamic number insertion · call tracking · number pools · local SEO
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.