What is dynamic number insertion?

Dynamic number insertion for gyms

Your website normally shows one phone number to everyone. With dynamic number insertion, a small script swaps that number depending on how the visitor arrived: one number for people who came from a Google ad, another for people from Meta, another for organic search, sometimes a unique number held for that visitor’s session. When a call comes in on one of those numbers, it is logged against the source that was shown it. The caller never knows; they dialed what they saw.

For a gym, that answers a question the pixel cannot. A lot of gym enquiries are phone calls, especially from search ads, and a call leaves nothing on a thank-you page for a tag to record. Without some form of call tracking, every one of those enquiries shows up as direct or unknown and the campaign that produced them gets no credit. Number swapping is the most common way of fixing that first step: which ad made the phone ring.

It is also where the answer stops. The swapped number identifies the source of the call. It does not know whether the caller booked a consult, whether they showed up, or whether they paid for a membership, because all of that happens at the front desk and in your billing system, and a phone number has no view of either. A campaign judged on calls is judged on volume, and the campaign that makes the phone ring with people asking about parking is not the campaign that fills the gym.

One practical caveat: keep your main number as the default and swap only for tracked visitors, so the number on your website stays consistent with your business listings for everyone else. Then treat the call the way you would treat a click: capture the source, capture the person, and follow them through booked, showed and paid.

Where this sits in Adsu

Adsu is not a phone system; it does not provide or swap numbers. What Adsu does is follow inbound calls and your business profiles to the paying member, so a campaign whose members all came by phone is credited with those members rather than with a call count. Adsu counts verified stages only: if a stage cannot be verified, it is not counted. Every report is one line per campaign per location.

If you already run a call tracking product, it keeps doing what it does. Adsu reports on which calls became members, which is the part a number swap cannot see. Adsu credits the last eligible touch inside the 30 days before the payment. Booked, showed and paid go back to Google as offline conversions and to Meta through the Conversions API. For how the two approaches differ on that question, read Adsu vs CallRail.

Related