Meta Pixel not tracking purchases? Find where it broke.

First, confirm that sales are actually happening

A drop in purchases inside Meta can mean two very different things: your campaigns may actually be generating fewer sales, or sales may still be happening while Meta receives incomplete conversion data.

Start with your source of truth. For a business using Stripe, check completed Stripe transactions. For another ecommerce platform, use the system that records completed orders or payments.

If your backend also shows no purchases, you may have a conversion problem rather than a tracking problem.

If real purchases are happening but Meta is not receiving or reporting them correctly, continue through the tracking path.

There are three different problems that look similar

Before troubleshooting, determine which layer is actually failing.

1. The Purchase event never fires

The website completes a transaction, but the tracking implementation never generates the expected Purchase event.

2. The event fires, but Meta does not receive it correctly

Your browser or tracking tool may appear to generate the event, while the event is missing, rejected, delayed, or otherwise absent from the expected Events Manager data.

3. Meta receives the event, but Ads Manager looks different

If the Purchase event exists in Events Manager but your Ads Manager purchase count is lower, the issue may involve attribution, reporting, timing, or another platform-level difference rather than a broken event trigger.

These problems require different fixes, so identifying the failing layer first can save hours of unnecessary changes.

Step 1: Test a real purchase

Run a controlled test through the same checkout flow a real customer would use.

Confirm that the transaction completes successfully in your payment or order system. Record the transaction or order ID, value, currency, and approximate completion time.

That gives you a specific real conversion to follow through the tracking path instead of troubleshooting aggregate numbers.

Step 2: Check Meta Events Manager

Use Events Manager and its testing tools to inspect whether the Purchase event appears when the test transaction completes.

If other events such as PageView, ViewContent, AddToCart, or InitiateCheckout appear but Purchase does not, your base Pixel may still be functioning while the purchase-specific trigger or checkout integration is failing.

Step 3: Check whether Purchase fires in the browser

A browser debugging tool such as Meta Pixel Helper can help confirm whether a browser-side Purchase event is generated during the checkout flow.

If the Purchase event does not fire at all, inspect the website's event trigger before changing anything in your campaigns.

Common causes include:

• a checkout or confirmation page changed
• a tag manager trigger stopped matching
• tracking code was removed during a deployment
• a JavaScript error prevents the event from running
• the event is attached to the wrong checkout action
• a consent configuration prevents the event from firing
• an ecommerce or tracking integration was changed

Step 4: Check the Purchase event data

Seeing the word Purchase is not enough. Inspect the data sent with the event.

At minimum, verify that the event represents the correct transaction and that important commerce information such as value and currency is correct.

Step 5: Check for consent-related blocking

Consent and privacy configuration can affect whether browser-side tracking is allowed to run.

If the problem started after installing or changing a cookie banner or consent platform, test the purchase flow both before and after the appropriate consent state is granted.

The goal is to determine whether your consent implementation is preventing the Purchase event from being sent when it should be permitted.

Step 6: Check Pixel and Conversions API together

Some businesses send purchase events through both browser-side Meta Pixel tracking and server-side Conversions API.

This can make the tracking setup more resilient, but the browser and server events representing the same transaction need to be recognized as the same conversion.

If identifiers are inconsistent, you can end up with duplicate events. If one side of the implementation stops working, you can also end up with missing or incomplete tracking.

When debugging, identify whether the Purchase event arrived from the browser, server, both, or neither.

Step 7: Compare individual purchases, not just totals

Aggregate numbers can be misleading.

Imagine your store completes 100 purchases. Your tracking misses five purchases but accidentally duplicates five others. You could still see 100 Purchase events.

The total appears perfect even though ten transactions are represented incorrectly.

A stronger diagnostic method is to compare individual real transactions against the events that should represent them.

What if Purchase appears in Events Manager but not Ads Manager?

That is different from a Purchase event that never arrived.

Ads Manager reports conversions according to Meta's attribution and reporting systems. Not every purchase recorded by your store will necessarily be attributed to a Meta ad.

Reporting delays, attribution settings, time zones, and traffic from other channels can also create differences.

If Events Manager shows that the underlying Purchase event is arriving correctly, investigate attribution and reporting separately from the website's event implementation.

We explain this distinction in more detail in why Meta conversions may not match Stripe.

What if Meta is tracking too many purchases?

If Meta or your underlying event stream contains more Purchase events than real transactions, investigate duplicate tracking.

A confirmation page may fire twice, multiple integrations may send the same purchase, or browser and server events may not be deduplicated correctly.

Read our guide to detecting duplicate purchase events for the transaction-level diagnostic process.

Why this problem is easy to miss

Broken conversion tracking often does not break the website.

Customers can still visit the store, complete checkout, and pay successfully. Ads can continue spending normally. The visible product experience may look completely healthy.

The failure happens in the measurement layer, which means the first obvious symptom may simply be a number in Meta that no longer makes sense.

That is why checking tracking only when someone notices a reporting discrepancy leaves a potentially large detection gap.

How SignalLeak monitors for missing purchases

SignalLeak approaches this from the transaction side.

It compares actual conversions with the tracking events your website produces. When a real conversion exists without the expected matching event, that discrepancy can be surfaced as a tracking incident.

SignalLeak also watches for duplicate events, value mismatches, currency problems, and transaction ID issues.

The goal is to discover tracking problems from the mismatch between reality and your tracking data rather than waiting for someone to notice strange campaign numbers.

Frequently asked questions

Why is my Meta Pixel not tracking purchases?

Common causes include a broken Purchase trigger, checkout or website changes, tracking code changes, consent configuration, incorrect event data, integration problems, or issues in a browser and server-side tracking setup. Start with one real transaction and determine exactly where its Purchase event disappears.

Why does Meta track AddToCart but not Purchase?

The base tracking implementation may still be working while the purchase-specific part of the checkout flow is not. Inspect the Purchase trigger, checkout integration, confirmation flow, and Events Manager test data.

Why does Pixel Helper show Purchase but Events Manager does not?

A browser tool showing that code generated an event does not by itself prove that the event was successfully processed and represented as expected downstream. Check Events Manager, diagnostics, the event payload, and any browser/server integration involved.

Why are Meta purchases lower than my actual store orders?

The difference may come from attribution rather than broken tracking, because not every customer is attributable to Meta. However, missing Purchase events can also contribute. Compare individual real transactions with your underlying tracking events before drawing a conclusion.

How often should I test my Meta purchase tracking?

Tracking should ideally be monitored continuously. A manual test confirms that the setup worked at one moment, but a later deployment, checkout change, integration update, or configuration change can break it again.

Related conversion tracking guides

Start with our broader guide to detecting broken conversion tracking, learn why Meta conversions may not match Stripe, or troubleshoot duplicate purchase events.