Call Tracking & Dynamic Number Insertion Setup Guide

What is dynamic number insertion in call tracking?

Dynamic number insertion displays a tracking number associated with a website visitor's session and updates the click-to-call link. When the visitor calls, the number connects the call to that session's attribution data. In Chirply, number pools belong to call-tracking campaigns; the campaign controls routing and the definition of a conversion.

Separate attribution, routing and conversion

Attribution identifies the source associated with a call. Routing decides who receives it. Conversion records whether the call met a defined rule. Treat these as three checks: a correctly attributed call still needs a reachable destination, and a routed call may not meet your business qualification criteria.

A dedicated campaign number identifies its campaign. A pooled number can connect the call with a website session and its available UTM tags, keyword and referrer. Record what the incoming visit actually provides; a missing keyword should remain missing rather than becoming an invented attribution.

Plan the pool around simultaneous visitors and the session allocation duration. Number availability, rental and call usage depend on the connected service and configuration. Review the actual inventory and costs before expanding the pool.

Configure a campaign and website pool

Prepare the routing and test destination before making a campaign active. Keep the provider and account ownership clear.

1. Open Phone → Call Tracking and choose New campaign. Give the campaign a name identifying the traffic source you want to measure.
2. Review its status: Draft does not route, Active routes live calls, and Paused suspends the campaign. Select status deliberately.
3. Configure the routing waterfall with labelled destination numbers and ring durations. Add an overflow destination when your process needs a final fallback.
4. Choose the conversion signal: a configured connected-call duration, a manual mark or an external confirmation. Record the selected rule in the worksheet.
5. Use New number pool, attach it to the campaign and review target size, allocation duration and allowed websites. Use the snippet provided by the pool page.
6. Install the snippet before the website's closing body tag and mark each phone-number element with data-ct-number. Test both the visible number and its tel link from a controlled visit and call.

Trace one controlled visit through to a call

For an illustrative test, visit the allowed website using a clearly labelled test campaign parameter. Record the displayed number and check that the call link uses the same destination. Place the controlled call, answer it at the intended route and inspect the resulting campaign and session association.

Test the fallback path with your team aware of the exercise. Verify the destination sequence and the final overflow behavior. If recording is configured, review the disclosure and applicable requirements for the real operating context before using it with customers.

Repeat-caller rules can route normally, use the same destination, flag a duplicate or prevent another route within the configured window. Test the option you actually select. A repeated call can be legitimate follow-up, so report the configured treatment clearly.

Fix the specific link in the chain

If the number does not change, inspect the installed snippet, allowed website and marked phone elements. If it changes but routes unexpectedly, inspect campaign status and waterfall destinations. If the call is present but the source is unclear, compare its session assignment and the original visit parameters.

Check converted calls against the chosen definition. A duration threshold is an operational signal, not proof of a purchase. Report tracked, answered, qualified and sold outcomes separately when your business maintains those records.

Common questions