Meta Ads Purchases Not Tracking? A Practical Pixel and CAPI Troubleshooting Guide

1. Why Meta Purchase events go missing

Before changing anything, understand the common failure points. Most tracking problems sit in one of these areas:

• The Purchase event fires on a page customers never reach, such as a thank-you page skipped by an external payment gateway redirect.
• Browser tracking is blocked by ad blockers, privacy settings or consent banners.
• The server-side event is sent without the identifiers Meta needs to match it to a person.
• Browser and server events are duplicated or overwrite each other because event_id values do not match.
• The event is sent to the wrong Pixel or dataset ID, or the access token has expired.
• Values or currency codes are missing or malformed, so the event is received but not usable for value optimisation.

2. Browser Pixel vs server-side Conversions API

The Meta Pixel runs in the visitor's browser. The Conversions API sends events from your server directly to Meta. They are designed to work together, not to replace each other.

Running both, with proper deduplication, gives Meta the most complete and reliable view of each purchase.

3. How to verify Purchase events

1. Open Events Manager, select your dataset and check the Overview for Purchase events from both Browser and Server sources.
2. Use Test Events: enter your store URL, place a real or test order and watch the Purchase event arrive in real time.
3. Install the Meta Pixel Helper browser extension and confirm the Pixel fires once on the order confirmation page.
4. Compare a single day of orders in your store or CRM against the events received for the same day and time zone.

If test events arrive but live events do not, the problem is usually page flow, consent or a condition in your tag manager rather than the Pixel code itself.

4. Diagnosing API requests and payloads

When server events are missing or flagged, inspect what your server actually sends. A healthy Purchase payload includes:

• event_name set to Purchase with consistent capitalisation.
• event_time as a Unix timestamp in seconds, close to the real purchase time.
• action_source set to website for website purchases.
• event_source_url pointing to the page where the purchase happened.
• user_data with hashed identifiers such as email and phone, plus client_ip_address, client_user_agent, fbp and fbc where available.
• custom_data.value and custom_data.currency with a numeric value and an ISO currency code such as INR.
• An event_id that matches the browser event for the same order.

Check your server logs or platform integration for API errors. Common responses point to an invalid access token, a wrong dataset ID, malformed parameters or timestamps that are too old.

5. Configuring event deduplication

When both the Pixel and CAPI send the same purchase, Meta needs a way to recognise them as one event. It does this with the event name and event_id.

Generate the event_id once — the order ID is a reliable choice — and pass the same value to both the browser and the server event.

6. Event Match Quality and matching parameters

Event Match Quality (EMQ) in Events Manager estimates how well your server events can be matched to Meta accounts. Low match quality means fewer events can be attributed to ads.

• Send hashed email and phone number for every purchase where the customer provided them.
• Normalise data before hashing: lowercase emails, trimmed spaces, phone numbers with country code.
• Forward the fbp and fbc cookie values from the browser to your server event.
• Include client_ip_address and client_user_agent from the original request.
• Add external_id when you have a stable customer ID.

Only send customer data you are permitted to share under your privacy policy and applicable consent requirements.

7. Internal sales vs attributed conversions

Even with perfect tracking, Ads Manager will not match your store's order count. That is expected. Meta reports purchases it can attribute to ads within your attribution setting, not every order you receive.

• Orders from organic, direct, email or other paid channels are not credited to Meta.
• Attribution windows such as 7-day click and 1-day view limit which purchases are counted.
• Ads Manager reports by impression or click time, while your store reports by order time.
• Time zone and currency settings may differ between your ad account and your store.

The goal is not identical numbers. It is a stable, explainable gap — and reliable event delivery so campaigns optimise on real signals.

8. A practical tracking diagnostic checklist

9. When a technical tracking audit is useful

Some issues can be fixed in an afternoon. Others need a structured audit across your site, server, tag manager and ad account. An audit is worth considering when:

• Reported purchases dropped suddenly after a website, checkout or platform change.
• Events arrive but value-based bidding or ROAS reporting looks unreliable.
• You run a custom checkout, external payment gateway or app-to-web journey.
• Several agencies or plugins have added tracking over time and nobody owns the full setup.
• You are scaling budgets and need confidence that optimisation signals are accurate.

Conclusion

Missing Meta purchases are a data delivery problem before they are a campaign problem. Verify the event fires, inspect what your server sends, deduplicate with a shared event_id, improve match quality and set realistic expectations for attribution. Fix the signal first — optimisation improves after it.

Frequently asked questions