You are currently viewing Google Ads Revenue Doesn’t Match Shopify? Reconcile the Gap

Google Ads Revenue Doesn’t Match Shopify? Reconcile the Gap

Why Google Ads revenue and Shopify sales do not match

Your Google Ads report shows one revenue figure. Shopify shows another. Before cutting a campaign or installing another tracking tool, check whether those reports are answering the same question.

Google Ads revenue different from Shopify does not automatically mean tracking is broken. First align the purchase actions, dates, currency, sales definition and attribution rules. Then investigate what remains unexplained. The useful outcome is a reliable decision about spend, rather than two dashboards forced to show an identical number.

Start with a comparison you can explain

Attribution means deciding which marketing interaction receives credit for a sale. Store sales and sales attributed to one advertising platform are different measures. Comparing all Shopify revenue with Google Ads conversion value mixes different scopes before you even begin.

Write down the exact report and column from each system. Include the store or Ads account, date range, reporting time zone, currency, sales channels, purchase action and revenue definition. Save the exports before changing anything. A screenshot of two headline totals rarely contains enough information to diagnose the gap.

Use three questions to guide the review: Did the purchase happen? What value was recorded? Which channel received credit? A discrepancy in one answer does not prove all three are wrong.

Check the date basis before blaming the tag

Google explains that its main conversion columns assign results to the ad-click date. A purchase completed later can therefore appear against an earlier reporting period. Its conversion-time reporting columns, including “Conv. value (by conv. time)”, offer another view for comparison with store purchases.

For example, a shopper could click on Monday and buy on Thursday. A Thursday store report and a Thursday click-date Ads report do not necessarily contain the same purchase. This is an illustration of timing, not a claim about your store.

Compare matching date boundaries and note each account’s time zone. Avoid treating today’s incomplete data as a final result. Record when each export was taken, allow for processing, and revisit recent periods before declaring a measurement failure. Switching to conversion-time columns helps with timing; it does not align attribution rules by itself.

Separate purchase counts from purchase values

If purchase counts are close but values are far apart, inspect the value definition. If counts and values both differ, start with the purchase actions and order coverage as well.

  • Are you comparing product sales after discounts, or a total that also includes shipping and taxes?
  • Is the conversion sending each order’s value, or the same fixed value every time?
  • Are both exports in the same currency, and is the event’s currency correct?
  • Are cancelled, unpaid, test and refunded orders treated consistently?
  • Does the comparison include only the online store, or also other sales channels?

Shopify’s sales discrepancy documentation explains that sales reports and order exports can differ. Returns and refunds have different reporting treatments, and test orders can appear in an order export while being excluded from Sales reports. Choose the report appropriate to your question instead of assuming an order export is an exact copy of a sales report.

For cash on delivery, distinguish an order placed from money collected and an order successfully delivered. A purchase event can be useful for measurement without being evidence of retained revenue. If the next question is whether acquisition is profitable, use the separate contribution-after-ads calculation after you have established a consistent revenue basis.

Audit the purchase actions before adding another tag

List each conversion action, its source, category, counting setting, primary or secondary status, and whether the relevant campaigns use it. Look for a purchase recorded through more than one installation route, such as a native Ads action alongside an imported analytics purchase.

Do not assume that two purchase actions automatically mean the same sale is counted twice in every report. Check which actions are included in the selected column and used by the campaign. A broad all-conversions total can include actions outside the purchase-only comparison.

Google’s counting options distinguish counting every conversion from counting one per ad interaction. For sales, repeat purchases can be legitimate. Changing to “One” is not a substitute for fixing duplicate purchase events.

Google can deduplicate repeated events with the same transaction ID within the same conversion action. Its transaction ID guidance requires a unique ID for each transaction. Reusing one static ID across orders can suppress valid purchases. Do not assume the ID will merge separate conversion actions into one.

Ask whoever maintains tracking to trace an existing order through the implementation and inspect the transmitted ID, value and currency. Keep customer details out of shared screenshots. If an additional test order is needed, agree how it will be identified and excluded from business reporting. Do not install another tracking app while the current event paths are still unclear.

Explain attribution differences without calling them extra revenue

Shopify’s marketing performance guidance notes that platforms use different attribution rules and that more than one platform can credit the same sale. Shopify’s selected attribution model also affects its channel view.

Record the model and window used in each comparison. A window is the period in which an earlier interaction can receive credit. Different windows, identity coverage and consent-related observation limits can leave differences even when an order and its value are recorded correctly.

Keep store orders as the operational reference for whether an order exists. Use attribution reports to understand credited marketing contributions under their stated rules. Do not add the revenue credited by several platforms and describe the sum as unique store revenue. Attribution credit also does not, on its own, prove that a sale would not have happened without the ad.

Build an explanation of the gap, not a forced match

Here is a hypothetical arithmetic example, not a benchmark or client result. Suppose a selected store report contains ₹1,00,000 and the Ads export contains ₹1,18,000. The initial gap is ₹18,000.

If inspection establishes that ₹8,000 of the Ads amount comes from a shipping-and-tax definition difference and ₹6,000 comes from comparing different purchase dates, those two non-overlapping adjustments leave ₹4,000 unexplained: ₹18,000 minus ₹8,000 minus ₹6,000. Those amounts are deliberately invented for the calculation; they are not typical adjustment rates.

Only subtract a difference after checking the underlying records, and ensure adjustments do not overlap. If order-level attribution records are unavailable, label that part of the explanation as uncertain. Do not allocate the remaining gap to “attribution” simply because it makes the totals reconcile.

Maintain a short issue log: observed difference, evidence, affected dates or campaigns, likely cause, owner, proposed change and verification result. Fix a confirmed implementation error first, then compare like-for-like periods. Keep a record of goal changes so a later shift in reported performance is not mistaken for a change in customer demand.

Questions to settle before changing budgets

Should Google Ads and Shopify match exactly?

Not necessarily. Matching definitions and dates removes avoidable differences, but attribution and observation can still differ. A documented, stable explanation is more useful than an arbitrary percentage tolerance.

Does a revenue gap mean I should pause the ads?

A gap alone is insufficient evidence. If confirmed incorrect values are driving bidding, assess the affected campaigns promptly with the account owner. Otherwise, investigate the report definitions before making a broad budget decision. There is no universal pause threshold that fits every store.

Will another tracking tool solve it?

Only if it addresses an established requirement and is implemented correctly. It cannot make two different attribution questions identical. Document the current setup and the unresolved problem before adding another source of purchase events.

Make the measurement useful for your next decision

My Analytics & Growth Measurement service helps clarify the reports and measures a growth decision depends on. Tell me which Google Ads and Shopify figures disagree and what decision you are trying to make. We can discuss the appropriate review scope; any implementation work is agreed separately.

Leave a Reply