# Troubleshooting Before going live, test that each traffic source shows the right number. If a number does not swap, work through the checks below in order, then the sections on caching and Google Tag Manager if your site uses them. ## Test each traffic source Before going live, it's worth testing that your swap groups behave correctly for each traffic source you're tracking. Because Nimbata only swaps a number when the session matches the source assigned to a swap group, you need to simulate each source type to verify it independently. ### Test a Google Ads visit Nimbata detects paid search sessions by reading the `gclid` parameter that Google appends to ad click URLs when auto-tagging is enabled. To simulate this without clicking a real ad: - Open a new browser tab. - Navigate to your website URL and append `?gclid=test`. For example: [`https://www.yoursite.com/?gclid=test`](https://www.yoursite.com/?gclid=test) - The number assigned to your Google Ads swap group should replace your regular number on the page. > **Tip:** If this works but real Google Ads clicks don't swap, the issue is likely that `gclid` is being stripped by a redirect. See [the troubleshooting checklist](https://help.nimbata.com/tracking/troubleshooting#numbers-not-swapping) for details. If auto-tagging is disabled in Google Ads, `gclid` will never be appended to real ad clicks: - Go to **Google Ads > Admin > Account settings > Auto-tagging**. - Make sure the checkbox is enabled. ### Test a direct visit A direct session is one with no referrer and no UTM parameters: a visitor who typed your URL or used a bookmark. - Open a **new incognito or private window** (this clears any existing session cookies). - Navigate directly to your website URL with no parameters. - The number assigned to your **Direct** swap group should appear. > **Tip:** Use incognito to avoid your own existing session cookie being picked up, which could cause Nimbata to show a number from a previous visit rather than a fresh direct session. ### Test an organic visit An organic session arrives from a search engine with a referrer header but no paid click identifier. - Open a **new incognito or private window**. - Go to Google (or another search engine) and search for your business by name. - Click through to your site from the organic search results. - The number assigned to your **Organic** swap group should appear. Alternatively, you can simulate the referrer manually by navigating from [`https://www.google.com`](https://www.google.com) to your site in the same browser tab, which passes Google as the referrer. ### Test a custom UTM source If you have a swap group assigned to a custom parameter source (for example, a specific campaign): - Open a new incognito window. - Navigate to your website URL with the UTM parameters that match your swap group configuration, for example: [`https://www.yoursite.com/?utm_source=facebook_ads&utm_medium=ppc&utm_campaign=spring-promo`](https://www.yoursite.com/?utm_source=facebook_ads\&utm_medium=ppc\&utm_campaign=spring-promo) - The number assigned to that swap group should appear. ### Confirm visits in Nimbata After each test visit, check [Dashboards > Visit Stats](https://app.nimbata.com/dashboard/visit-stats) to confirm Nimbata recorded the session under the correct channel. The **Visitors** row should increment for the channel you just tested. Troubleshooting: [Numbers not swapping](https://help.nimbata.com/tracking/troubleshooting#numbers-not-swapping)\ Detailed guide: [Set up DNI step by step](https://help.nimbata.com/tracking/dni-setup#set-up-dni-step-by-step)\ Detailed guide: [Set up swap groups](https://help.nimbata.com/tracking/swap-groups#set-up-swap-groups) ## Numbers not swapping Your Nimbata DNI script is installed but the phone number on your website isn't changing. This section covers every known cause, from the most common to the most obscure, in the order you should check them. **Start here:** visit your website and add `?gclid=test` to the end of the URL. For example: [`https://www.yourwebsite.com/?gclid=test`](https://www.yourwebsite.com/?gclid=test) - **Number swaps:** the script is working. The issue is with your real traffic conditions. Jump to check 4. - **Number does not swap:** the script itself is the problem. Start at check 1. ### 1. The script is not installed or not loading The most common reason numbers don't swap is that the script hasn't been placed on the page, or it's loading on some pages but not others. - Open your browser's developer console (**F12 > Console**) and type `nimbata`. - If you see `nimbata is not defined` or an error, the script is not loading on that page. - Check that the script appears in the page source (**Ctrl+U**) on the page you're testing. - Use Nimbata's built-in **Website URL checker** under [Tracking > Tracking Code](https://app.nimbata.com/tracking/tracking-code) to confirm detection. - If deployed via GTM, confirm your tag's trigger is set to **All pages** (or your intended scope) and fires on **DOM Ready**. **Common causes:** 1. The script was added to the homepage only. 2. The GTM tag has a scoped trigger. 3. The WordPress plugin was deactivated during a theme or plugin update. ### 2. There is no phone number in the page for the script to replace Nimbata's DNI script works by replacing a number that already exists in your page HTML. It cannot inject a number into a blank space. If the number is rendered dynamically after load (via JavaScript, a page builder, or a CRM widget), or is simply absent from the DOM when the script runs, nothing will swap. - Right-click the phone number on your page and select **Inspect**. - Is the number visible as plain text in the DOM, or does the element appear empty? - If the number is injected dynamically, enable **SPA mode** in [Tracking > Tracking Code](https://app.nimbata.com/tracking/tracking-code) so the swap logic re-runs after DOM changes. - If the number is inside an `