Meta reports one purchase total and GA4 reports another. Picking whichever number looks better is not measurement. The reports can credit different interactions and observe different subsets of events. This reconciliation keeps operational orders, collected purchase events and attributed purchases as separate layers, then investigates the differences that remain unexplained.
Make this useful for your client. Follow the worksheet, or use the ready-to-copy task with your connected data.
Try this task in 1ClickReport → · See the product workflow →Evidence → Decision → Review
How to run the investigation
Define the three totals
Record completed orders from the operational system, collected GA4 purchase events and purchases credited in Meta. Align dates, time zones, currencies and refund treatment. Do not use one label such as “sales” for all three without defining it.
Document attribution conditions
Record the selected attribution windows and reporting timing in the platform views. Compare click-based and view-based credit where available and relevant. Keep the raw setting visible rather than assuming every account uses the same default.
Check collection and duplication
Ask the implementation owner to inspect purchase identifiers, repeated firing and browser/server deduplication. Reproduce a permitted test journey. Tracking gaps and overlapping attribution can coexist; fixing one does not establish that the other disappeared.
Maintain an explanation ledger
For each gap, write the evidence, known explanation, unresolved amount and next check. Keep attributed channel results for optimization and operational orders for business totals. Never sum overlapping platform-attributed purchases to claim additional customers.
Decision worksheet
Use these rows to turn the investigation into an action. Add the actual account, date range, evidence and owner before sharing it with a client.
| What you find | Interpretation | Next move |
|---|---|---|
| Orders exceed observed GA4 events | Collection may be incomplete | Inspect consent, blockers and implementation. |
| Meta credits more than GA4 | Definitions or credit rules may differ | Compare windows and observation conditions. |
| Duplicate transaction evidence | Counts may be inflated | Have the implementation owner test event handling. |
Download this worksheet (CSV) ↓
Worked example: an illustration, not a customer result
Suppose a store has 50 completed orders, Meta credits 35 purchases and GA4 credits 28 to paid social. That is not 63 social purchases. The two reports may overlap and answer different attribution questions. Reconcile against the same order period and document the remaining uncertainty before deciding that either system is broken.
MAKE THIS YOUR NEXT CLIENT TASK
Run the review on your own data.
Start with one client in 1ClickReport. Connect GA4 and the relevant ad or commerce source, select the correct client and use the task below. The analyst keeps client-specific context as you work.
Read the ready-to-use task
Reconcile this client’s Meta and GA4 purchase reporting with operational order counts I provide. State definitions, time zones, windows and timing. Separate collection gaps, duplication and attribution differences. Return an evidence ledger and unresolved checks. Do not add platform-attributed purchases or claim an exact causal contribution.
3-day free trial · No credit card required.
- Copy the task, then create your account in the new tab.
- Finish setup and connect the relevant client data.
- Return to this page and open the task in AI Analyst ↗. Review the prompt before sending.
Missing order, CRM or application evidence must be provided by its owner. No cross-system match is assumed.
A question worth asking
Which purchase number is the truth?
For business operations, start with the defined order or payment system. For platform optimization, use the relevant platform’s documented conversion view. Neither eliminates the need to explain attribution and collection differences.
References and method
Reviewed November 12, 2026. The decision process and worksheets are 1ClickReport’s editorial recommendations. Examples are hypothetical, not customer results. Platform behavior and access can vary; use the current native account view to verify settings.
- Meta: Insights reporting reference
- Shopify: analytics discrepancies
- Google Analytics: conversions and key events