Facebook Ads Troubleshooting
Changes in Facebook ads might cause warnings sometimes. In this article, we will review common facebook pixel warnings and what the solution is for them.
Facebook Pixels might send you warning notifications. Sometimes these warnings are "false positive". However, in many cases, the warnings should be handled with care as they can indicate a faulty setup.
Before you start troubleshooting:
- Adjust the dates of your Event Manager to reflect the date since you started using Anytrack.
- Check that you are troubleshooting the correct Facebook Pixel.
- Check that your AnyTrack Facebook integration is properly set:
- Facebook Pixel ID.
- Ad Account Connection.
- Conversion API is on.
- UTM tracking template is set on all your ads.
- Conversion display delays: See timing information for expected delays in Event Manager and Ads Manager.
Remember:AnyTrack sends exclusively Server Side Events to Facebook, so if you see both Browser and Server events for the same event (ex:
Purchase), it means that another data source is sending events to Facebook and you should disable it.
Good to know:In most cases, the warnings are caused by a mix of data sources sending data to your Facebook Pixel. AnyTrack follows strict integration and event mapping guidelines which guarantees the most accurate tracking, and a high match rate.
Since we cannot control what other systems might send to Facebook, if an other system sends malformed data, or missing data, the overall match rate will be negatively affected.
📋 Deduplication parameter
Ignore: Since AnyTrack is sending only Server Side Events no duplication should occur within your account.
- PageView event missing deduplication parameter: You can ignore this warning.
- Make sure identical events share a matching deduplication key.
- Event missing deduplication parameters.
ReminderSince AnyTrack sends only server side events, there is no need to pass the deduplication Key to Facebook.
Values Previously set
- You can ignore this warning. It is displayed when you update your UTM Tracking Template.
PageView event missing deduplication parameter
The PageView event is fired by the Facebook Base Tracking Pixel. It is not send via the Conversion API and therefore does not need any deduplication key.
Make sure identical events share a matching deduplication key
Disconnect other plugins and integrations that trigger the facebook pixel or Conversion API
AnyTrack sends only data to the Conversion API. So you can disregard these warnings - unless you have other systems sending data to facebook.
Related Troubleshooting Resources
Depending on your issue, these specialized guides may help:
- Event Match Quality Issues - Low EMQ scores, missing parameters, data quality optimization
- UTM Tracking Template Problems - Red/yellow marks in verification, template errors
- Advanced Configuration Issues - Disconnected pixels, multiple integrations, UID parameters
- Business Manager Permissions - Access issues, missing permissions, asset configuration
🔌 Disconnected Pixel
If your Facebook Pixel becomes disconnected from AnyTrack, you'll receive an email notification. This prevents conversion data from being forwarded to Facebook.
Common causes:
- Facebook password change (invalidates token)
- Manual token revocation in Facebook Business Manager
- API permission changes
- Token expiration
How to fix:
- Go to Tracking Pixels in your AnyTrack dashboard
- Look for a yellow warning indicator on your Facebook Pixel
- Click Reconnect and authorize the connection
- Verify that the Conversion API slider is enabled
Learn more:See Advanced Options - Disconnected Pixel for additional details and troubleshooting steps.
🔢 Overreporting Attributed Results
If the Campaign Report shows significantly more Attributed Results than Purchase (or Lead) events, a system other than AnyTrack is probably sending events to the same pixel. It could be another tracking software or Meta Pixel code installed directly (or through an integration) on your website.

This campaign has 2 sales, but Facebook has registered 8.
When you install the AnyTrack Tag on your website and connect AnyTrack to your Facebook Ads account, AnyTrack automatically loads the Meta Pixel each time the AnyTrack Tag loads. Therefore, you should remove the Meta Pixel installed on the website to prevent duplicates.
To quickly identify if conversion events are reported by systems other than AnyTrack, navigate to the Events Manager in Facebook Ads and ensure that Integration is not Multiple.

Multiple Integration means the conversion is received from more than one source.
How to fix:
- Check Facebook Event Manager for "Multiple" integration status
- Remove any other Meta Pixel installations from your website
- Disable other tracking plugins or integrations sending to Facebook
- Follow this guide to identify systems sending events to Facebook CAPI
Frequently Asked Questions
Updated 3 days ago
