Choose the right Meta action metric for purchase reporting
Avoid summing overlapping action categories or treating every Meta action as a sale.
Meta action reports can contain several categories describing related behaviour. Choose the action that matches the business question and understand its attribution context. A broad action total is not automatically a count of unique purchases.
Work through it, step by step.
Inspect the action types returned and document the one used in the report. Distinguish landing-page views, leads and purchase-related measures.
Check whether related categories overlap. Avoid adding parent and child action categories merely because each row contains a number.
Compare reported purchase values with the intended currency and business definition. Use aggregate order records separately to investigate discrepancies.
Make it concrete.
A report contains both a broad purchase category and a more specific purchase action. Adding them without checking their relationship can count the same attributed outcome more than once.
What to keep in mind.
An action name does not prove correct event implementation or order deduplication. Reporting analysis cannot replace a measurement audit when those details are uncertain.
Your next useful step.
Keep one explicit action definition in recurring reports and attach the attribution settings. Escalate unexpected changes to the measurement owner with a reproducible example.
Working with this in Liftaven
Record the ad account, reporting level and attribution settings before comparing results. Delivery and conversion reports can be revised as events arrive. Liftaven reads Meta advertising data; changes to campaigns, creatives, audiences and tracking are made in Meta tools.
Explore the workspaceSources & context
This note combines original practical guidance with the reporting references below. Follow provider documentation for current definitions and availability; suggested investigations are not guarantees of a particular result.