This is a list of Facebook pixel errors and warnings you might see in Events Manager under Diagnostics. You can also find information about how to resolve the problems and a list of affected URLs and parameters.
Note: If you don’t see your diagnostic listed here but you’re experiencing problems with your pixel, use these best practices to check your pixel setup.
Invalid currency code: This error appears if the currency code for an event isn’t formatted correctly. The currency code must match the standard 3-letter ISO currency codes, such as USD and GBP.
Click See affected URLs to see which pages and parameters are causing this error and make any necessary updates. Learn more about setting the currency for your event.
Missing event name: This error appears when your event is missing a name. Event code must contain an event name, whether it’s a standard event name or a custom event name. Click See affected URLs to see which pages and parameters are causing this error and make any necessary updates. Learn more about formatting events.
Invalid value parameter, missing value parameter or missing currency parameter: This warning message appears if a value or currency parameter is empty or missing for an event, or if the value or currency parameter isn’t formatted correctly.
- Code snippets need to contain both a value and currency parameter. The default standard event code contains USD 0.00, which you can update to a specific value and currency for your event.
- The value field must contain a decimal number greater than or equal to zero, and may not include letters, special characters, currency symbols or commas.
Click See affected URLs to see which pages and parameters are causing this error and make any necessary updates. Learn more about setting the value and currency for your event.
Event name mismatch: This warning appears if one or more of your standard events is similar but not identical to a standard event. If you’d like to measure this action as a standard event, you’ll need to update the event code snippet on pages of your website to match the standard event formatting.
Click See affected URLs to see which pages on your website may contain incorrect standard event code. Bear in mind that events are case-sensitive. For example, a purchase event must be written as Purchase and not purchase if you’d like to measure and optimise for this event as a standard event. Learn more about how to format standard events.
Multiple events on an action: This error appears if your pixel is sending multiple events in response to a single website visitor action, such as a button click or page load. In most cases, your pixel should only send one event per visitor action. For better reporting and ad optimisation, only add event code to specific pages or inline actions that reflect the action someone takes on your website. For example, a complete registration event should only be added to a page that indicates someone has completed a registration process.
Click See affected URLs to see which pages of your website may contain duplicate or incorrect event code. Remove extra event code snippets from pages where that action doesn’t occur. Check your website’s HTML code and remove any extra event code from your HTML template header. The only Facebook code that belongs in the header of your website is the Facebook pixel base code (which contains the Page view event). Learn more about best practices for setting up standard events on your website.
Redundant purchase events: This error appears if your pixel receives four or more purchase events when someone makes a single purchase on your website. This error can lead to over-reporting of purchases and may negatively affect delivery of any ads using Conversion or Product Catalogue Sales objectives. For better reporting and ad optimisation, only add purchase event code to a specific page on your website that indicates someone has completed a purchase, such as a thank you or confirmation page. Otherwise, you can choose to add the purchase event code to a specific inline action. For example, when someone clicks on a Buy Now button.
Click See affected URLs to see which pages of your website may contain duplicate purchase event code. Remove purchase event code snippets from any page of your website that doesn’t indicate someone has made a purchase. Also check your website’s HTML template header to make sure that it doesn’t contain any purchase event code. The only Facebook code that belongs in the header of your website is the Facebook pixel base code (which contains the Page view event). Learn more about best practices for setting up standard events on your website.
Invalid email provided: This error appears when we receive an invalid customer email address from your pixel. This may affect the performance of advanced matching features. Open your website’s source code and make sure that the pixel advanced matching features are set up to receive the correct information. Learn more about advanced matching on Facebook for Developers.
Duplicate events detected: This error appears if you have an event that’s being logged using your website’s source code, and also as an automatic event. This leads to duplicate events being received and may affect the accuracy of your pixel reporting. Learn how to turn off automatic events. You’ll continue to receive this event if it’s set up through your website’s source code.
- New Domain Sending Data: This appears if your pixel recently started sending events from a new domain. You can create a domain allow list or block list to control if domains are allowed to send Facebook events through your pixel, or edit your existing list. Learn more about pixel traffic permissions.
Potentially violating personal data sent to Facebook: This appears if potentially violating personal data has been detected. This data doesn’t comply with Facebook’s Terms and Policies. To help protect the privacy of your users, this information isn’t stored in our ad systems and you aren’t able to view or use it. This issue may affect the performance of any ads optimising on affected events, including those used in Custom Audiences or custom conversions.
Review the details in the diagnostic and determine if any potentially violating personal data is being sent. You’ll need to remove any personal data being sent to Facebook in order to resolve this problem. Learn more about personally identifiable information.
Potentially violating health data sent to Facebook: This appears if potentially violating health data has been detected. This data doesn’t comply with Facebook’s Terms and Policies. To help protect the privacy of your users, this information isn’t stored in our ad systems and you aren’t able to view or use it. This issue may affect the performance of any ads optimising on affected events, including those used in Custom Audiences or custom conversions.
Review the details in the diagnostic and determine if any potentially violating health data is being sent. You’ll need to remove any health data being sent to Facebook in order to resolve this problem. Learn more about sensitive health information.
Potentially violating financial data: This appears if potentially violating financial data has been detected. This data doesn’t comply with Facebook’s Terms and Policies. To help protect the privacy of your users, this information isn’t stored in our ad systems and you aren’t able to view or use it. This may affect the performance of any ads optimising on the affected ad events, including those in Custom Audiences or custom conversions.
Review the details in the diagnostic and determine if any potentially violating financial data is being sent. If it is, remove it by using the solution provided in the diagnostic. Learn more about sensitive financial information.