Meta pixel tracking checks, beside your GA4 and Google Ads numbers
Tracking Whisper connects to Meta with read access. It reads the Meta pixel's details and the events it received, the ad account's custom conversions and results, and, if you allow it, the Facebook Page and Instagram account's posts and insights. It changes nothing in Meta.
The Meta pixel
Which events the pixel received, how many, and whether they match what the container sends. The agent also reads when the pixel last fired and how automatic matching and the first-party cookie are set.
- Event counts by name, for up to the last 28 days
- When the pixel last fired
- Automatic matching and first-party cookie settings
The pixel on the site
The GTM audit and the site check look at the pixel from the site's side. They find the mistakes that make Meta count events twice or count the wrong pixel.
- The pixel base code loaded by two tags
- PageView sent more than once on a page
- A pixel on the site that is not the one linked to the client
- Events sent without an event ID
Conversions API
Tracking Whisper does not set up the Conversions API and sends no events to Meta. What it checks is the browser side that deduplication depends on: Meta needs the same event ID from the pixel and from the server to count an event once.
The ad account
Spend, impressions, clicks and the conversions Meta credits to the ads, read for a period and set beside GA4 and Google Ads. The custom conversions are read too, with what each one is based on.
Pixel events under watch
Where a watched site has its pixel linked, monitoring reads the pixel's events every morning and judges them by the same rules as the GA4 numbers. A container version can break the pixel while GA4 goes on counting, and this is how that gets noticed.
- PageView, ViewContent and AddToCart
- InitiateCheckout and Purchase
- Lead and CompleteRegistration
In the performance report
Meta ads sit in the performance report beside GA4, Google Ads and Search Console: spend, impressions, clicks, link clicks, purchases, purchase value and leads. They are set beside the sessions GA4 recorded from paid Meta, so you see how much of what Meta claims reached the site.
Pages and Instagram
Organic posts and their insights, when the Page permissions are granted. The agent reads the latest posts of the Facebook Page and of the Instagram account linked to it, with their reactions, comments and, where Meta gives them, views and reach.
Questions
Does it change anything in Meta?
No. Meta is read only in Tracking Whisper.
Does it set up the Conversions API?
It checks what the pixel receives. The Conversions API itself runs on your server or your server-side tagging setup.
Which Meta permissions does it ask for?
Read permissions only. For ads and the pixel it asks for ads_read and business_management. Page and Instagram permissions are asked for only when the organic side is turned on.
How long does the Meta connection last?
About 60 days. After that the Connections page asks for a new Meta login.
Why do Meta and GA4 report different conversions?
Meta credits conversions to the ads it showed, with its own attribution, while GA4 credits sessions by their source. The performance report sets the two side by side and says where they part.
Can it check the pixel without a Meta login?
Partly. The site check sees every pixel hit the site sends, with no Meta connection at all. Event counts, pixel settings and ad results need the Meta login.
Which plans include Meta?
The pixel and the ad account are read on Tag Manager and platforms, GA4 and ad platforms, and All data. Pages and Instagram are read on GA4 and ad platforms and All data.