Skip to content
AnyTrack AnyTrack Knowledge Base

Troubleshooting Facebook Ads

Troubleshoot your Facebook Ads integration with AnyTrack. Learn which Meta deduplication warnings you can safely ignore, how to reconnect a disconnected Meta Pixel, fix overreporting of attributed results, and resolve campaigns that do not appear in the Campaign Report.

Meta Pixels send warning notifications. While some are false positives, many indicate setup issues requiring attention.

See Ad Platforms Attribution for the timing details on Meta Events Manager and Ads Manager delays.

Deduplication Warnings You Can Ignore

Section titled “Deduplication Warnings You Can Ignore”

Meta deduplication warnings apply when the same event reaches Facebook from both the browser pixel and the server. AnyTrack sends conversions to Facebook exclusively server-side through the Conversion API, so no duplication occurs within your account and no deduplication key is needed. You can safely ignore the warning variants below unless other systems also send data to your Meta Pixel.

  • Event missing deduplication parameters
  • Values previously set
  • PageView event missing deduplication parameter
  • Make sure identical events share a matching deduplication key

Values Previously Set

Section titled “Values Previously Set”

Ignore this warning. It appears when you update your UTM Tracking Template.

Values previously set warning in Meta Events Manager

PageView Event Missing Deduplication Parameter

Section titled “PageView Event Missing Deduplication Parameter”

The PageView event is fired by the base Tracking Tag and is not sent via the Conversion API. It doesn’t need a deduplication key.

PageView event missing deduplication parameter warning in Meta Events Manager

Matching Deduplication Keys for Identical Events

Section titled “Matching Deduplication Keys for Identical Events”

Disregard these warnings unless other systems send data to Facebook.

Matching deduplication keys warning for identical events in Meta Events Manager

Disconnected Meta Pixel

Section titled “Disconnected Meta Pixel”

AnyTrack sends an email notification if your Meta Pixel disconnects. This stops AnyTrack from sending conversion data to Facebook.

Common causes:

  • Password change (invalidates token)
  • Manual token revocation in Facebook Business Manager
  • API permission changes
  • API updates
  • Token expiration

How to fix:

  1. Go to Tracking Pixels in your AnyTrack dashboard
  2. Look for a yellow warning indicator on your Meta Pixel
  3. Click Reconnect and authorize the connection
  4. Verify that the Conversion API slider is enabled
If this issue becomes recurrent, please contact support

Overreporting Attributed Results

Section titled “Overreporting Attributed Results”

If the Campaign Report shows significantly more Attributed Results than Purchase or Lead events, another system is likely sending events. It could be another tracking software or Meta Pixel code installed directly or through an integration.

This campaign has 2 sales, but Facebook has registered 8.
This campaign has 2 sales, but Facebook has registered 8.

When you install the AnyTrack Tracking Tag and connect your Facebook Ads account, AnyTrack automatically loads the Meta Pixel. Remove any Meta Pixel installed directly on your website to prevent duplicates.

To quickly identify if conversion events are reported by systems other than AnyTrack, navigate to Meta Events Manager and ensure that Integration is not Multiple.

Multiple Integration means the conversion is received from more than one source.
Multiple Integration means the conversion is received from more than one source.

How to fix:

  1. Check Meta Events Manager for “Multiple” integration status
  2. Remove any other Meta Pixel installations from your website
  3. Disable other tracking plugins or integrations sending to Facebook
  4. Follow this guide to identify systems sending events to Facebook

Campaigns Not Found for Awareness and Traffic Objectives

Section titled “Campaigns Not Found for Awareness and Traffic Objectives”

Awareness and Traffic campaigns don’t optimize for a conversion event, so their ad sets carry no conversion pixel. Before July 2026, the Campaign Report and the Verify Your Ads tool did not display these campaigns at all.

Since the July 2026 update, AnyTrack also recognizes ads that use the connected pixel in the ad’s Tracking → Website events setting. Awareness and Traffic campaigns whose ads select the connected pixel there now appear in the Campaign Report with their spend, and conversions from those campaigns are attributed normally.

If an Awareness or Traffic campaign doesn’t appear, verify its ads select the connected pixel under Tracking → Website events. See Ads Ignored Under Other Pixels in Verify Ads for the steps.

Selection of Campaigns Objectives during Campaign creation in Meta Ads.
Campaign objectives selected during campaign creation in Meta Ads.

Ads Ignored Under Other Pixels in Verify Ads

Section titled “Ads Ignored Under Other Pixels in Verify Ads”

When you run Verify Ads Settings, the results may include a message such as “Ignoring 4 ads found under other pixels.” Meta reports those ads as associated with a different Pixel (dataset) than the one connected to your AnyTrack property. AnyTrack only manages ads associated with the connected pixel, so it skips them during verification, and their campaigns don’t appear in the Campaign Report.

This can look confusing because tracking still works: the AnyTrack Tag records visits from those ads, and events show the ad set and ad names under the content and term attributes when the UTM template is installed. The missing piece is the ad-to-pixel association on Meta’s side, not your tracking setup.

Meta associates an ad with a pixel in two places, and they can disagree. The ad set’s Conversion section sets the pixel Meta optimizes for, locked in when you create the ad set. The ad’s Tracking → Website events setting selects the pixel that records the ad’s traffic. AnyTrack recognizes an ad when either place matches the connected pixel, so Verify Ads ignores an ad only when the pixel is different in both. An ad set duplicated from an older campaign, or created with a different default dataset, commonly points to the wrong pixel this way.

Check which pixel the ads use, in both places:

  1. In Meta Ads Manager, open the Ads tab and click Edit on one of the ignored ads.
  2. Scroll to the Tracking section and note the Pixel (dataset) selected under Website events.
  3. Open the Ad sets tab and click Edit on the ad set of the same ad.
  4. Find the Conversion section and note the Pixel (dataset) selected for the conversion event.
  5. Compare both with the Pixel ID connected in AnyTrack under Tracking Pixels.

Fix the mismatch:

  • The ad’s Website events dataset is different: switch it to the pixel connected in AnyTrack and publish. Meta accepts the change while the ad runs. One match is enough for AnyTrack to recognize the ad.
  • The ad set optimizes for a different dataset, and you want Meta to optimize for the connected pixel: Meta locks the ad set’s pixel at creation on most objectives. If Ads Manager lets you edit the pixel in the ad set’s Conversion section, switch it and publish. If Ads Manager blocks the edit, duplicate the ad set with the connected pixel selected in its Conversion section, and publish the duplicate.
  • You want to keep using the other pixel: connect it to AnyTrack as an additional Meta Pixel and install the UTM Tracking Template on its campaigns. You can connect multiple Meta Pixels to the same property, each configured individually.
  • The ads are Advantage+ Catalog (dynamic product) ads: confirm the catalog is linked to the connected pixel. See Dynamic Catalog Campaigns Not Recognized as Active.

After the fix, run Verify Ads Settings again to verify the ads are no longer ignored. If the connected pixel already appears in the ad’s Tracking section or the ad set’s Conversion section and Verify Ads still ignores the ads, contact support with a screenshot of both screens and the Verify Ads results.

Dynamic Catalog Campaigns Not Recognized as Active

Section titled “Dynamic Catalog Campaigns Not Recognized as Active”

A Facebook dynamic catalog campaign (Advantage+ Catalog Ads, also called Dynamic Product Ads) can appear in AnyTrack as Meta but never register as active: no impressions, link clicks, ROAS, or attribution results, even though AnyTrack detects the campaign ID and name and the correct pixel and ad account are connected.

This happens when the product Catalog is not linked to the connected Pixel in Meta. Dynamic ads serve from a catalog, and if that catalog isn’t associated with the same Pixel/Dataset you connected to AnyTrack, the campaign’s events aren’t tied to your pixel, so AnyTrack can’t recognize the campaign as active or attribute its conversions.

As with every campaign, the Campaign Report and Verify Ads only display campaigns that generate conversion events tied to the connected pixel.

Find Campaigns Using Campaign ID

Section titled “Find Campaigns Using Campaign ID”

Use Campaign IDs to find and manage your campaigns with greater precision than campaign names.

In Facebook Ads Manager:

  1. Click Customize columns from the Columns dropdown menu
  2. Add the Campaign ID column
Click on Customize columns to add the Campaign ID column
Add the Campaign ID column in Facebook Ads Manager.

In AnyTrack Campaign Report:

  1. Click the Display Adset Names/Ids selector from the Settings menu
  2. Use the search box to find the Campaign ID
Use the Display Adset Names/Ids selector to switch between campaign names and IDs
Switch between campaign names and IDs in the Settings menu.
Section titled “Related Troubleshooting Resources”

Depending on your issue, these specialized guides may help:

Frequently Asked Questions

FAQ was last reviewed on 2026-08-02

Why does my Facebook Ads account get disconnected?
The Ad Account API gets disconnected when the token is no longer valid. It can happen if you invalidate it manually or if you update your Facebook Login password.
Why do I not see test results in Meta Events Manager?
Use Meta CAPI Test Mode. Get the test event code from Meta Events Manager and add it to your Meta Pixel settings in AnyTrack, then trigger a test conversion. See Meta CAPI Test Mode for the full setup.
Why don't I see all my campaigns in the AnyTrack campaign report?
Campaigns appear in AnyTrack only if their ads are associated with the Meta Pixel connected to your property, either through the ad set's conversion pixel or through the ad's Tracking (Website events) selection (learn more). A missing UTM tracking template is never the reason a campaign doesn't appear. The template matters for accuracy instead: without it, visits fall back to the referrer and conversions show under (not set) rather than the campaign (install it).
What does 'Ignoring ads found under other pixels' mean in Verify Ads Settings?
Meta reports those ads as associated with a different pixel (dataset) than the one connected in AnyTrack, so AnyTrack skips them during verification and their campaigns don't appear in the Campaign Report. Meta sets the pixel in two places: the ad's Tracking section (Website events) and the ad set's Conversion section. AnyTrack recognizes the ad when either place matches the connected pixel. The fastest fix is to switch the ad's Website events dataset to the connected pixel and publish, or connect the other pixel in AnyTrack as an additional Meta Pixel (see the full steps).
Can I connect multiple Meta Pixels to the same property?
Yes, you can connect multiple Meta Pixels to the same AnyTrack property. Each one is connected and configured individually.
If I have several pixels in my Meta account, does AnyTrack automatically use all of them?
No. AnyTrack only loads and sends conversions to the pixel(s) explicitly connected to your property as Meta Pixels. Pixels that exist in your Meta account but are not connected in AnyTrack are not used. Connect each pixel individually:
  1. In AnyTrack, navigate to Tracking Pixels and click Connect Tag.
  2. Follow the prompts to authenticate your Facebook account and select the correct ad account and pixel.
  3. Enable the Conversion API (server-to-server tracking) slider and save changes.
  4. Install the UTM Tracking Template on the campaigns using that pixel, then run Verify Ads Settings for that Meta Pixel.
Also make sure each campaign uses and optimizes on a pixel that is actually connected: campaigns only appear in AnyTrack if they are associated with a connected Meta Pixel and generate conversion events (learn more).
I don't see offline conversion events, why?
AnyTrack does not send conversions through the Offline Conversion API. We use exclusively the Conversion API for real-time server-side event tracking.
Can I use AnyTrack's UTM template with another software's parameters?
Yes. Append the other software parameters after the AnyTrack template. Avoid duplicate parameters like utm_source. Example: utm_source=facebook&utm_medium=cpc&tw_id={{ad.id}}.