adlaneSign in Practical guide
Meta Ads purchase actions: pick one action, avoid double counts
Meta action reports contain several categories that describe related behaviour, and purchase-related actions can appear under more than one name. Choose the action that matches the business question, understand its attribution context, and resist adding rows together. A broad action total is not a count of unique purchases.
By Adlane · Updated
Meta Ads purchase actions are categories, not a ledger of orders
An action row in a Meta report pairs an action type with a count under a given attribution setting. Several rows can describe the same underlying event seen through different lenses: a pixel event, an app event, an on-platform event, or a broader category that rolls several of these together. Each row is a valid answer to its own question.
None of them is the order book. A credited purchase is a purchase that met the attribution rule, counted the way the event implementation reported it. If the event fires twice, the count rises twice; if consent blocks the pixel, the count falls. Reading the row as a sales figure skips both facts.
Inspect the action types returned and document the one you use
List the action types actually present in your report, then pick one and write it into the report definition with its attribution setting. The table separates the families that are easy to confuse. Names vary by tool and version, so match on what your report returns rather than on the labels here.
| Action family | What it describes | Use it for | Do not |
|---|---|---|---|
| Landing page views | Arrivals where the destination started to load | Checking that clicks become visits | Count them as leads or sales |
| Leads | Form or lead events, on platform or on site | Enquiry-driven businesses | Add on-platform and on-site leads without checking overlap |
| Purchase (specific source) | A purchase event from one source such as the pixel | A precise, repeatable purchase definition | Add it to a broader purchase category |
| Purchase (broad category) | A roll-up that may include several sources | A single headline number when sources are understood | Add it to its own components |
| Purchase value | Reported value under the same rule and currency | Value-based questions with the currency stated | Compare across currencies or settings |
Parent and child categories overlap
A broad purchase category can already include the specific purchase action beneath it. Adding the parent to the child counts the same credited purchase twice. The same trap exists for leads, where an on-site lead and a broader lead category may describe one submission. Before adding any two rows, ask whether one contains the other.
When a report tool presents every row with a number, it is tempting to total the column. Do not. Pick the single row that answers the question, or confirm from the documentation that two rows are disjoint before combining them.
Illustrative example: one order, two rows
Illustrative example: a fictional report shows a broad purchase category with 52 credited purchases and a specific pixel purchase action with 48. Someone totals the column and reports 100 purchases. The documentation shows the broad category includes the pixel action, so the 48 are part of the 52. The report has roughly doubled the credited outcomes.
The correct reading is one row with its setting attached: 52 credited purchases under the broad category, or 48 under the pixel action, depending on which definition the report uses. Neither is a sales figure; the shop’s order system records its own count. The numbers are invented to show the overlap and are not benchmarks.
Check currency, value and implementation separately
Compare reported purchase values with the account’s currency and with the business definition of order value. A value that includes tax, shipping or refunds in one system and excludes them in another will never reconcile. State which definition the report uses.
An action name proves nothing about how the event was implemented or whether orders were deduplicated. Reporting analysis cannot replace a measurement audit when those details are uncertain. When the relationship between the Meta count and the order count changes abruptly, escalate to whoever owns the tracking with a reproducible example: one date range, one action, one setting, and both counts.
Keep one action definition in Adlane
In Adlane, connect Meta and select the ad account. Ask a bounded question that names the action and the setting, such as “Show credited purchases for this campaign over the last complete month under the account’s attribution setting, list every purchase-related action type returned, and tell me which rows overlap.” Review the evidence and confirm which single row the report should use.
Any change that follows is prepared as a proposal you review and approve; nothing is applied from the conversation, and new campaigns start paused. Adlane does not add overlapping action categories or combine credited conversions across providers, and it cannot audit your event implementation. It is not affiliated with Meta.