Top 7 Most Popular Errors With Facebook Pixel Conversion API & Solutions To Fix Them
Setting up Facebook Pixel Conversion API for Shopify requires precision and attention to detail. Advertisers often encounter a myriad of errors and issues during this process, which may hinder the accurate tracking of conversions, leading to less effective ad targeting and decision-making.
In this article, we aim to shed light on the top 7 most common issues encountered when setting up the Facebook Pixel Conversion API and provide practical solutions to overcome them. We will also highlight useful debugging tools available to facilitate the identification and resolution of potential obstacles.
Let’s dive right in!
Let’s figure out the most common issues when setting up Facebook Pixel Conversion API on Shopify websites and how to deal with these errors:
#1. The Facebook pixel activated multiple times on the web page (Event duplicated)
Facebook Pixel activated multiple times means that a Pixel with the same ID and event name has been sent to your Facebook for many times. This can happen when the tracking code for the Facebook Pixel may have been mistakenly inserted multiple times by the developer or website owner in the website’s source code.
Additionally, if the site uses different plugins, extensions or tools for tracking purposes, it is likely that many of these integrations already include the Facebook Pixel tracking code.
To resolve this issue, it is necessary to identify and remove the duplicate instances of the Facebook Pixel code. Reviewing the web page’s source code and checking for any instances of the pixel code being inserted more than once should help in identifying the duplicate code.
After identifying the duplicate instances, simply remove the redundant tracking code to ensure that the Facebook Pixel is properly activated only once on the web page.
#2. New domains sending data
This error is detected when you may see pixel events sent to your Facebook from unknown website domains. This error can happen for the following reasons:
- Customers running Facebook Pixel on Preview Theme will see domains like shopifypreview.com. This case happens when the customer is editing the theme, Pixel still collects data and sends it to Facebook. If you fall into this situation, you can ignore this issue because the error is not too significant.
- When you add a pixel to your website, you make your pixel ID public. This means that other people can find your pixel ID, add it to the pixel base code, and place it on their website (This case rarely happens)
- Some websites use affiliate marketing programs where a pixel can be embedded on the website to track user activity and attribute any sales (This case rarely happens)
To work around this, you need to set pixel traffic permissions for your domain. To do this, let’s follow our steps:
- Go to Events Manager.
- Select Data sources.
- Click Settings.
- Select Create Allow List or if you want to block certain domains that copied your Pixel ID, you can choose Create Block List in the drop-down menu
Next, enter the domain you want to add (or block) to your list:
Additionally, you should regularly monitor your website logs and analytics to identify any unusual or suspicious activity related to pixel events. This will help you detect and resolve any ongoing issues.
If you continue to receive pixel events from strange or suspicious domains, contact email firstname.lastname@example.org for Facebook Pixel support
#3. Facebook Pixel Event Missing Some Deduplication Parameters or Facebook Pixel Missing Purchase Value Parameter
This is one of the most common Facebook CAPI errors. This error means that you are not sending some deduplication keys (including event name, event ID, _fbp, and external ID) for your server events. These deduplication parameters are used to identify and prevent duplication of events in a system. Without these parameters, it can be difficult to accurately track and manage events.
To address this issue, you’ll need to check the Event ID to check for missing deduplication parameters and determine the appropriate parameters to include. To do that, open the Facebook event testing tool. If everything is correct, you will see something similar to the screenshot below:
#4. Server Sending Invalid Match Key Parameters for PageView Or Other Events
Here are several screenshots displaying the error:
Server sending invalid IP address parameter, in events like page view, view content & add to cart
For this error, Facebook wants to notify you that the values you are sending from the server are not unique or are formatted incorrectly. Besides, it could be a problem with the server-side code or configuration, an issue with the data being sent from the client side, or a misalignment between the expected format of the match key parameters and the actual data being received.
To troubleshoot this issue, you can consider the following steps:
- Check the server-side code or configuration responsible for sending the pageview event. Ensure that it is properly handling and sending the match key parameters
- Review the client-side code where the data is being captured and sent to the server. Verify that the relevant match key parameters are correctly captured and included in the data payload.
- Compare the expected format of the match key parameters with the actual data being received on the server to ensure that they align and match the expected format. For example, if the match key parameter is expected to be a string, make sure that the data being sent is indeed a string.
If you’re not familiar with coding, the steps mentioned above may be difficult to follow. Don’t worry, we at email@example.com are here to help you. Just send us an email with screenshots of the issue and our technical team will assist you in resolving it.
In the case that your store is a Shopify store, please give our a try Orichi Multi Facebook Pixels app. We are confident that this will ensure accurate tracking.
#5. Potentially Violating Personal Data Sent to Facebook
This error is usually related to browser events. It happens when Facebook has detected user data in the URL. Some CMSs and other tools like PayPal send user details in the URL after they register or make a purchase.
To work around this, you can disable the software or plugin feature that passes the user’s data as a URL query parameter to the thank-you page (signup/signup/purchase). Alternatively, you can switch to only server-side Facebook tracking. This way you can modify the URL before sending it to Facebook.
In addition, this error can also come from the “You may also like” feature on your website. Facebook has recently made some updates and including these parameters is unacceptable. Try turning this feature off!
#6. Same Event ID Received for Many Event Instances
This error occurs when multiple event instances with the same event ID are sent to the API. For example, a user visited your product page. At this point, two events will fire on this page: PageView and ViewContent. Instead of each event having a unique event ID, both events share the same ID.
Event IDs are unique identifiers assigned to each event that is sent to the Facebook Pixel Conversion API. It helps Facebook track and analyze events accurately. When multiple event instances with the same event ID are detected, it creates a conflict because Facebook assumes that each event ID should represent a unique event.
Here are some steps you can take to fix the issue:
- Double-check your event setup: Review your event setup to ensure that you are correctly implementing the Facebook Pixel’s Conversion API. Make sure you are using the unique event ID for each event instance.
- Check your server-side code: If you are using server-side code or an API for sending events to Facebook Pixel’s Conversion API, review your code to ensure that the correct event ID is being generated for each event instance. Make sure you are using a unique event ID for each event.
- Clean up duplicate event IDs: If duplicate event IDs have already been sent to Facebook Pixel’s Conversion API, you will need to clean them up. This can be done by either removing the duplicate event IDs from your system or by sending separate events with unique event IDs for each subsequent occurrence.
- Test and validate your events: After making any changes, it’s crucial to thoroughly test and validate your events. Use Facebook’s event testing tools or the Pixel Helper Chrome extension to ensure that event IDs are unique and sent correctly to Facebook Pixel’s Conversion API.
#7. Pixel and catalog not paired
This error means that the pixel is not associated with Shopify products, and as a result, the pixel will not track the store events your Facebook ads are generating.
To resolve this issue, you need to make sure that you have properly set up your Facebook Pixel and connected it to your product catalog.
- Check if the correct Facebook Pixel ID is implemented on your website. You can find the Pixel ID in your Facebook Business Manager under the “Pixels” section.
- Review the event setup for any mistakes or missing details. Ensure that the events you want to track are configured correctly and associated with the appropriate product catalog properties.
- Use the Facebook Pixel Helper tool to test if your Pixel is firing events correctly and is properly connected to your website.
Additionally, you need to connect the pixels you’ve added to the catalog, by following these instructions:
- Go to www.facebook.com/products
- Select the Shopify Product Catalog.
- Go to Catalog and choose Events.
- Select Connect To Tracking.
- Select the pixel you want to use and select Save
How To Check Facebook Pixel Conversion API Errors?
A great way to check for errors in your Pixel is to use Facebook’s Events Testing Tool – a tool that allows you to detect and resolve issues with your FB pixel or server events. If there are errors, they will be displayed in the Diagnostics tab in the toolbar so you can take a closer look.
Errors marked in red often require quick response and should be fixed immediately. The yellow errors are warnings you should heed and consider. Additionally, make sure to review your server logs for any error messages related to the Conversion API.
Moreover, it is recommended to regularly monitor your Conversion API events to identify and fix any errors promptly, ensuring the accuracy of your data and the effectiveness of your campaigns.
The Facebook Pixel Conversion API is a powerful tool that allows businesses to track and measure user interactions beyond the limitations of traditional pixel tracking.
However, as with any technology, issues can arise, potentially hindering successful tracking and accurate reporting. For that, you need to thoroughly test and troubleshoot, along with ensuring the correct implementation of the API and regular updates.
Our article provides insights into some of the most common Facebook Pixel Conversion API errors encountered by advertisers and marketers, and practical solutions to fix them. Hope this article will bring a lot of useful knowledge and perspective to you. Contact us if you have further questions!
420 total views, 1 views today