Overview

This tutorial will describe the process of troubleshooting your Facebook conversion pixel integration.

The best way to verify that you have the facebook pixel configured properly is to use to use the Chrome browser extension called "Facebook Pixel Helper."

Testing the integration

With the Facebook Pixel Helper extension enabled, we will initiate a checkout. 

In our checkout, we notice that right away it's complaining about two separate facebook pixels:

Open

Cross referencing the pixel ID with the one that is configured in the UltraCart Privacy and Tracking, we verified that the one start 2223 is what we you have configured in our conversion and tracking.

Progressing through the checkout to the finalization of out checkout. On the receipt we find that we have both pixels rendering. We can see that with the second one fired a “purchase event”, ending up with duplicate purchase events being registered:

Open

We know we have two pixels firing off a purchase event, and that’s not appropriate.

So, the hunt is on for where pixel 81258 is coming from? 

Typically, when we can't find where a piece tracking code is, we can make an assumption that it may be injected into the page by another tool, such as Google Tag Manager.   

And in this case, reviewing the google tab in Privacy and Tracking we find that we do have Google Tag Manager enabled on our website, and inspecting it we can see the container is GTM-CPH5R. 

So, our next step it to temporarily disable that then perform another test checkout to see if we now have a single Facebook pixel during the checkout.

Seeing that we do, in fact, have only a single pixel in our checkout, we will continue to the receipt to confirm that we are now having only the once conversion pixel registering in the receipt page:

We see that we have only the single correct facebook pixel firing off for the receipt!

So, All we need to do now is to go into our Google Tag Manager, container GTM-CPH5R and delete whatever is in there associated with pixel 81258.  Our testing helped us eliminate a extraneous pixel and also confirmed that the correct pixel is firing off. Success!