Verify the installation¶

Check that the script loads, that the number swaps, and that a call is attributed, before you hand a website over to a client.

Before you begin¶

The script is installed. See Install the tracking script.
The site has a pool with a rule and at least one number, and the site is active.
You have a phone to make a test call from.

1. Confirm the script loads¶

Load a page of the website, then in the Enfonica Console open the tracking site, click Settings, and under Tracking script click Refresh. Installed means the script reported in; see Check that the script is installed. If it still shows Not detected, continue with the browser checks below to find out why.
Open the website in a private browsing window. Add ?utm_source=verify&utm_medium=test to the URL, for example https://www.example.com/?utm_source=verify&utm_medium=test.
Open the browser's developer tools and select the Console tab. Look for the line [EnfonicaTracker] Bootstrapping with tracking code: E-....
Select the Network tab and filter for ctjs.au. The request should return status 200.

If the request succeeds but the number doesn't change, the tracking code is wrong, the site is paused, the hostname isn't in Allowed domains, or no rule applies to this page. See Troubleshoot number swapping.

2. Confirm the number swaps¶

Look at the phone number on the page. It should be one of the pool's numbers. To see the pool's numbers, in the Enfonica Console open the tracking site, click Number pools, open the pool, and view its numbers.
If the number is a link, check that its href is tel: followed by the tracking number.
Open another page of the website. The same tracking number should appear.

3. Confirm a call is attributed¶

Call the tracking number shown on the page. Answer the call at the destination and stay connected for at least 60 seconds before hanging up, so the call also qualifies for integrations.
In the Console, click Tracked calls. The call appears when it starts and shows its outcome once it ends.
Open the call. Under Campaign attribution, Source should be verify and Medium should be test. The attribution panel should show High confidence with the reason Single session match.

If the call shows No attribution, the number was dialled outside the session window, or from a different session than the one that saw the number. Repeat the test and call within a couple of minutes of viewing the page.

Repeat calls

If you call the same tracking number from the same phone again within 7 days, and the first call was attributed, the second call inherits the first call's attribution and shows the reason Repeat call. To test attribution again, use a different phone or a different number from the pool.

4. Confirm integrations (optional)¶

If Google Analytics 4 is connected, the test call appears in Google Analytics Realtime within a few minutes. If Google Ads is connected, conversions require a real ad click and take up to 24 hours. See Integrations overview.

5. Check pool health after launch¶

After the website has had real traffic for a week, open the pool and check its Health. If it shows At risk or Critical, add numbers. See Size a number pool.