Short answer
If dynamic phone-number insertion fails, check script loading, the target number, the tel: link and session or consent rules. Change one condition per test and verify the full journey before altering the entire installation.
Key verification: Save the page, browser, expected source and substitution result in a reproducible worksheet.
Sources and limitationsIf the call tracking number remains fixed on your website, check in this order: if it loads the code, if it identifies the number that should be replaced and if the visit complies with the tracking rules. Change only one condition at a time and keep the result. This way you can locate the fault without modifying the entire installation.
The goal of this guide is to recover a replacement that should already work. That a different phone number appears is a first check: you will still have to verify the destination of the call and its record. It is not equivalent to having validated an advertising conversion.
Prepare an investigation worksheet before changing settings
Note the exact page, browser, device, time and source you expected to measure. Also describe where the phone appears: header, button, footer, or content that loads later. "It doesn't work on the website" provides less information than "the usual number continues to appear on the button on the quote page."
| Diagnostic field | What to register |
|---|---|
| URL and version | Affected page and last known modification |
| Visible number and destination of the button | Displayed text and address of the tel link: |
| Visit Conditions | Intended Source, Test Session, and Consent Status |
| Expected result | Number or group that should be assigned according to your rules |
| Change and result | An intervention, responsible person and subsequent observation |
It is an original adaptable worksheet. Save screenshots without real visitor data. If multiple people review the installation, agree on who makes the changes to avoid two simultaneous fixes that make it impossible to know which one resolved the problem.
Check that the code reaches the affected page
Open the published page and look for the code or identifier of your project. Then check its load in the browser tools. Code present in the source may not be executed due to an error or crash; a label visible in the manager preview may not be published.
Nimbata lists missing code, loading errors and traffic conditions among the common causes. Your test with ?gclid=test is to test the substitution in that environment. It is a diagnostic parameter, without a valid advertising click behind it. Replacement Diagnostics on Nimbata .
Perform the check on an affected page and another that works. If only one template fails, compare how it incorporates the phone and the code. If it started after an update, record that fact before reinstalling components.
Check the target number and call link
In Nimbata, target matching must respect HTML text, including spaces and signs. The documentation proposes the method using span tags when it is convenient to expressly identify the element. Target Number Rules .
Check your tool's rules before copying a format from another. WhatConverts documents its own Swap Number field and visit tests with ?gclid=test&wc_clear=true to clear your tracking cookies in the test browser. WhatConverts Checks .
Check text and link separately tel: . Fictitious example: the header shows the assigned number, but the button retains the usual telephone number. The visitor who presses the button takes a different route than the one who marks what he sees. Record both results and correct the failing element.
Isolate session, late loading and consent
Use a controlled test session to avoid dragging a previous source. Note what parameters you used and how the visit was classified. If your rules cover only certain channels, a direct visit can correctly preserve the usual number.
Observe if the phone appears after opening a dropdown or changing a view. Repeat the check after that action. If the replacement occurs before the element exists, check your provider's options for dynamic content.
If the consent tool prevents code from being loaded under a certain condition, record that behavior and compare it to the approved privacy settings. The test must respect that configuration. Don't assume that a category is "necessary" just because it makes it easier to track.
Validate the correction from start to finish
- Repeat the affected visit and confirm the displayed telephone number and link.
- Make a controlled call to the assigned number and check the destination.
- Locate the record by time and identifier and review the observed source.
- Repeat on mobile and on a second page with the same template.
- Flag the trial to exclude it from business results.
If the replacement works but fails only with traffic spikes, check the capacity of the pool. For support, provide the file, the result of each test and the last known change. This evidence allows us to work on a specific failure.
Sources and limitations
Documentary review: . Content type: Documentation-based procedure.
Sources describe terms and capabilities stated by their owners. Proposed protocols and fictional examples do not establish product tests performed by CallsIQ.
- Replacement Diagnostics on Nimbatahelp.nimbata.com
- Target Number Ruleshelp.nimbata.com
- WhatConverts Checkswww.whatconverts.com
Check current terms
Consider these options if they solve the problem described. Confirm features, limits and availability in your country.
NimbataOfficial pricing for SpainWhatConvertsAffiliate linkThe labelled commercial links may earn CallsIQ a commission or referral reward. Our commercial policy.
Official sources, explained calculations and clearly labelled examples. Read about our methodology and use of AI in writing.