# Verify Ads

> The dashboard check that confirms which of your ads are associated with the connected pixel — an ad matches when either its ad set's conversion pixel or its ad-level tracking pixel equals the pixel connected to AnyTrack.

**Verify Ads** is AnyTrack's check that your ads are actually associated with the pixel connected to AnyTrack — the association that determines whether an ad's spend and conversions can meet in the [Campaign Report](/docs/campaign-report).

## Verify Ads and the two-level pixel model

Meta sets the pixel in **two places that can disagree**:

1. the **ad set's Conversion section** — the optimization pixel (`promoted_object`), locked at creation on most objectives and changeable only under conversion objectives;
2. the **ad's Tracking → Website events** — the tracking pixel, editable at any time, including on a running ad.

AnyTrack recognizes an ad when **either** level matches the connected pixel. Traffic and Awareness campaigns that only track the pixel appear in the Campaign Report with their spend. "Ignoring N ads found under other pixels" therefore means the pixel differs at **both** levels — and the fastest fix is switching the ad-level Website events dataset, which Meta allows live.

## Support framing for Verify Ads

When a customer insists "it's the same pixel, I checked," establish **which** Ads Manager screen they checked before diagnosing. Never flatly rebut "you can't switch the pixel on a running ad" — that is correct for the ad set's conversion pixel on most objectives, and wrong for the ad-level tracking pixel. Clarify the two levels instead.