Two dashboards can show different purchase counts without either being a simple copy of the order ledger. First determine whether the underlying purchase event is correct. Then compare report scope, attribution, conversion settings and timing. The store’s order record remains the reference for actual transactions.
Test the event before explaining attribution
Place a controlled order and record its ID, value, currency and timestamp. Check whether GA4 receives one purchase and whether Google Ads has a conversion action connected to the intended goal. If one real order fires twice, fix the implementation before debating models. Check refunds and cancellations separately.
Align what each report counts
Write down date range, timezone, campaign scope, attribution settings, conversion action and whether the number describes key events or ad conversions. Google’s current guidance distinguishes GA4 key events for behavior analysis from conversions for campaign measurement. A count tied to ads can differ from an all-traffic event view even when both are configured correctly.
Choose a decision basis
Use the order system for actual sales, GA4 for journey analysis and Google Ads for campaign optimization within its defined attribution rules. Keep a reconciliation table for recurring anomalies. If a gap remains unexplained, document the affected order IDs and do not optimize bids from a suspect signal.
Worked decision example
Illustrative comparison: one store order appears once in GA4 but not in Google Ads. Check whether an eligible ad interaction occurred before investigating a missing tag. Another order appears twice in GA4 with the same ID; that is a likely implementation fault requiring event-trigger review. These are different causes and need different fixes.
Practical review checklist
- Does one test order produce one GA4 purchase?
- Are the compared scopes and settings written down?
- Is the bidding conversion action trustworthy?
Where to go next
Google Ads service · GA4 purchase validation guide · Google conversion and key-event guidance