Testing Your Conversion Tracking Code

Conversion tracking codes allow you to track what happens on your website after a user has clicked your campaign item. It can let you know, for example, if users are purchasing your product or viewing multiple pages of your website after they click. Learn more about conversion tracking codes here.

Once you’ve generated and implemented your conversion tracking code on your website, you can test that the code is implemented properly and working. This will work for any type of conversion you track, including website conversions, website actions, pageviews and video views.

Below are the options for verifying that your conversion tracking code is setup correctly.

Using TFA Scope

TFA Scope is a free Google Chrome extension that helps you check if your conversion tracking code is working properly. To use this free tool, click here and install the extension in your Google Chrome browser.

Once installed, here’s how you can use TFA Scope to test your conversion tracking code:

Open your Chrome web browser.

Open the developer console by going to View → Developer → Developer Tools.

You will see a message in the Developer Tools console. Here are the most common messages you will see and what they mean:

• If you see the message below after the page has loaded, the tracking code is working properly and the test is complete.

• If you see the message below, a non-fatal error occurred. Conversions will still be recorded, but ideally you should correct the issue detailed in the message.

• If you see the message below, it means you are using the Javascript Snippet version of the code, and the Javascript loaded but the push command (what makes the code record a conversion) was never sent. If this happens, make sure you have copied and pasted the entire code correctly. Also, if you are tracking a Website Action, make sure you have completed the conversion you are hoping to track (a link click or button click, for example). Until this is fixed no conversions will be recorded.

• If you see the message below, it means the tracking code did not work correctly. You will also see an explanation of what went wrong and what you can do to fix it.

If you are still experiencing issues, you can learn more about troubleshooting conversion tracking issues here.

Using Network Developer Tools

By using a debugging tool, you can see the information sent between your web browser and the server. This will help you examine the conversion tracking request sent by your browser, and identify whether or not the correct information is sent through your conversion tracking code.

To test your conversion tracking code using developer tools, do the following:

Open your Chrome web browser.

Open the developer console by going to View → Developer → Developer Tools.

When the page has loaded, look at the network traffic in the console. Use the filter icon to filter for “action?”. You should see a reference to trc.taboola.com and the Status Code of 204 (No Content). If you see this, the code is working correctly.

Important Note!

You won’t register a conversion in Backstage by performing this test.

If you do not use Google Chrome, there a number of other developer tools for other browsers:

Wait For a Conversion to Occur

If your campaign is already up and running, and the conversion tracking code has been implemented, you can wait to see actions (conversions) appear in Backstage. This way, you will know the conversion tracking code is tracking conversions. You can learn more about campaign reports here.

Completing a Test Conversion

In order to confirm that your conversion tracking code is working, you can also complete a test conversion and wait for the conversion to appear in Backstage.

If you see your campaign item in a Taboola widget while browsing the internet, you can click on the campaign item and complete a conversion. Then, wait for for the conversion to register in your Backstage reporting. It will most likely take a few hours for the conversion to show up.