Daniel Najda0490 135 271Discuss a project

Business guide

Dynamic number insertion: how website call tracking links calls to visits

Understand website number replacement, forwarding and attribution limitations before choosing call tracking for a small business.

By Daniel Najda

Illustration of a browser phone-link button and pointer beside a separate desk phone and speech bubbles

A tracking number can replace the number shown to a visitor

Dynamic number insertion means showing a tracking phone number according to a configured rule, such as the visitor’s source or session. The call is forwarded to the business’s receiving number. A call-tracking system then uses the number assignment to help associate telephone activity with the marketing visit. It does not mean the business’s normal staff phone must become the public number everywhere.

Matching rules depend on the provider. For example, CallRail documents a website script that replaces numbers according to the visitor’s marketing source. Other configurations use number pools for session-level reporting. Confirm local availability and the configured scope: a source-level number shared by visitors cannot identify every individual visit. This is an implementation example, not a recommendation of a particular supplier.

Understand display, dialling and forwarding as separate steps

The website needs to display the intended number and update clickable telephone links consistently. The tracking service needs to forward calls to the correct destination. Reports need to associate the call with the relevant assignment. A failure at any one of those points can leave the page looking correct while callers reach an old handset or activity is attributed incorrectly.

Google’s website call-conversion setup covers eligible ad-driven visits, not every source. Separately, Google’s ad call reporting replaces the number on supported ads with a Google forwarding number. To display your own number or a third-party tracking number on those ads, Google says you can turn that reporting off. This concerns ad-number display; do not disable it merely because another tool measures website calls.

The number replacement path
  1. Website visit

    An eligible visit meets the configured assignment rule.

  2. Displayed number

    The page and telephone link use the assigned tracking number.

  3. Forwarded call

    The tracking service routes the caller to the business.

  4. Recorded outcome

    Call data is reviewed and linked to a lead where appropriate.

Ask what the service can and cannot attribute

Discuss number-pool sizing, the assignment window and what happens when a visitor returns later. A saved tracking number may be called after the original visit. Different people can share a device, and the same person can move between devices. These behaviours mean attribution is a measured approximation with defined rules, rather than perfect knowledge of every customer’s journey.

Decide how the system should behave if the script is blocked, consent prevents it loading or a tracking number cannot be supplied. The business should still have a usable contact route. Keep a stable business number where a platform or long-lived printed reference requires it, and check the provider’s guidance before distributing temporary tracking numbers outside their intended use.

Plan routing, ownership and ongoing costs

Write down who owns or controls the tracking numbers, whether they can be ported, and what happens when the subscription ends. Confirm included usage, routing fees and any charges relevant to the proposed arrangement. The number a customer saves is part of the business’s contact journey, so cancellation and provider changes should be considered before rollout rather than after the account is closed.

Decide who can access call details and whether recording is needed at all. Recording and storing conversations introduces separate requirements that depend on the circumstances; forwarding does not require you to record every conversation. Keep only the operational information needed for the agreed purpose, and use the appropriate notices and consent arrangements for the tools selected.

  • Define source-level or session-level reporting needs.
  • Test number display, telephone links, routing and fallback.
  • Document number control and cancellation arrangements.
  • Agree access, retention and any recording requirements.

Validate with a known journey before trusting reports

Use a planned test visit and a test call to check the full chain. Record the source conditions, number displayed, destination reached and report entry. Also test the ordinary contact path without replacement so an unavailable script does not prevent customers calling. Repeat relevant tests after changing a site header, page template or telephone component.

My software integration service can help assess whether number replacement is worthwhile and connect the selected call data to an operational lead workflow. It is an implementation project with defined tools and limitations, not a guarantee that every customer can be traced. For some businesses, honest click tracking and a reliable call log are a sensible first step.

Sources and further reading

Need help with this?

Software integrations

Connect your website, apps and existing business tools so information moves between them with less manual copying and double entry.

See the service and scope
Browse all guides

Start a conversation

Good projects start with
a great connection.