To troubleshoot your Jet codes, please follow the Audit steps below. Further troubleshooting information is at the bottom of this article.

Getting Started

To conduct a code audit, you will need to use Google Chrome to view the webpage.

Before you start:

Install Google Tag Assistant extension into Chrome.
Tag Assistant helps to troubleshoot installation of various Google tags including Google Analytics, Google Tag Manager and more.

When installed correctly, it should appear in the top right of your Chrome window, next to your profile picture.
 

Make sure you have the details of your Web Tracker configuration handy.

This means knowing your number replacement method (class, ID or text), and your target (class name, ID or target text). You will also need to know if you have any filters applied to your session tracking pool (eg: cpc traffic only).
These details are usually provided to you along with your Jet Interactive codes by the Jet Support team when you first activate your account, but you can request them again at any time by creating a case.
 

Auditing a Code Implementation

Step 1 - Open an Incognito browser window in Chrome.

Step 2 - Right click anywhere on the screen and click Inspect.

This will load up the diagnostics tab on your screen. Select the 4th tab along, called Network.

Step 3 - Click the icon for the Google Tag Assistant and select Record. Once the recording success screen shows, you can click out of this box.

Step 4 - Type the domain you are conducting the audit on into the search bar and hit Enter.

IMPORTANT: If you are auditing a pool with filters, make sure you have a URL that will trigger them!
eg: for a cpc only filter, your domain would need to be: www.jetinteractive.com.au?utm_source=google&utm_medium=cpc

Lost? Use this handy tool to build your own custom URLs for filters and campaigns
 

Step 5 - In the Network tab, find the search box for filter, and type rest.

What should appear is 4+ records, 2 saying rest and 2 saying activity. If you are loading more that 1 pool of numbers, more records will show up depending on how many pools are being loaded.

Step 6 - Click on the second entry for rest, with the Initiator of (index). A panel should appear with further details.

Click on the arrows next to ‘commands’ and open up the menus until you get to ‘parameters’

Step 7 - Check the parameter details.

Check that the “phoneNumber” field matches the number being displayed on the page.

If using replace by Text, ensure the “text” field contains the correct target as provided to you by Jet.

If using replace by Class, check the “elementClass” contains the correct class name as provided to you by Jet.

Step 8 - Click refresh on your page. You should see the code run and display the same number as your previous page view.

Step 9 - Place a test call through the number displayed, and remain connected for at least 10 seconds.

Step 10 - Once you have terminated the call, check this call is in the Jet portal and has the correct web data associated. If you have a GA integration, check the event has pushed through.

If all the above steps contain the correct information, your code Audit is complete and correct!
 

Troubleshooting your Dynamic Codes

The most common Number Display issues are: 
 

If you are experiencing one of the above issues and your code audit is successful, please contact Jet Support with the following information:

1. Website being visited - and the specific page on the website
2. The browsing path leading to the website visit
3. What number was displayed on the website
4. Please let us know if the numbers are displayed in a click-to-reveal panel

If possible to place a call through a jet number, please also provide:

1. Date & Time of call
2. CLI (the phone number used to make the call)
3. CLD (the number that was dialled)
4. Call duration