← Back to blog
Tracking & Attribution· 10 min read

GA4 for Shopify Stores: The Reports Worth Checking Every Week

A focused weekly GA4 routine for Shopify merchants — which reports matter, which to ignore, and how to read them without getting lost.

Written by Mantas JurgutisFounder, Adsify — builds the Google & Meta automation merchants use daily

Editorially reviewed by Adsify Editorial on February 10, 2026Reviewed against Shopify, Google Ads and Meta official documentation.

GA4 has too many reports, most of which you should ignore

GA4's default interface presents dozens of reports across Life Cycle, User, and Advertising sections, and the temptation is to feel like you should be checking all of them. In practice, a Shopify merchant running paid ads needs a tight weekly routine of five or six reports, checked in a consistent order, rather than an open-ended exploration of the whole interface. This gets the review down to 15-20 minutes a week instead of an hour of aimless clicking that produces no decisions.

1. Realtime and Acquisition overview — the sanity check

Start with Reports > Acquisition > Traffic acquisition, filtered to the last 7 days, grouped by Session default channel group. This is your fastest sanity check: is Organic Search still your largest channel, or did Paid Social suddenly disappear because a pixel broke? A sudden channel dropping to zero sessions week over week is almost always a tracking or campaign-pause issue, not a real demand shift, and it's the single fastest thing to catch before it costs you a week of misread performance data.

Confirm session counts are in a sane range relative to last week and the same week last month. GA4 shows week-over-week percentage change directly in the comparison view (use the compare feature under the date picker, set to 'Previous period'). If total sessions swing more than 20-30% without a clear campaign or seasonal reason, check Shopify's theme editor to confirm the Google tag or Shopify's built-in Google & YouTube channel integration is still firing, since a theme update or app conflict can silently break tracking.

2. Ecommerce purchases report — is revenue where you expect it

Go to Reports > Monetization > Ecommerce purchases, which shows items viewed, added to cart, checked out, and purchased in a funnel-adjacent view. Compare item revenue and purchase count against Shopify's own analytics (Analytics > Reports > Sales) for the same date range. Small discrepancies of a few percent are normal due to timezone settings and how GA4 attributes purchase events versus Shopify's order timestamp, but a large gap — GA4 showing half of Shopify's actual order count — signals a broken or duplicated purchase event that needs fixing before any GA4 revenue number can be trusted.

3. Traffic acquisition by campaign, not just channel

Add a secondary dimension of 'Session campaign' to the Traffic acquisition report to see performance below the channel level. This is where you catch a specific ad set or campaign quietly underperforming even while the overall channel looks fine — for example, Paid Social overall looks healthy, but one prospecting campaign is generating sessions with a near-zero conversion rate, dragging down blended efficiency without being obvious at the channel-summary level. Sort by sessions descending and scan the top 10 campaigns for conversion rate outliers weekly.

4. Landing page report for paid traffic specifically

Under Reports > Engagement > Landing page, add a filter for Session default channel group equals Paid Social or Paid Search, then review engagement rate and conversion rate by landing page. A common finding: a product page landing from a paid ad has a much lower engagement rate than the same page's organic traffic, which usually points to ad-to-page message mismatch rather than a tracking problem — the ad promises something the landing page doesn't immediately deliver. This report answers a question platform ad managers can't: how does traffic behave after the click, on your own site.

5. Retention and returning customer rate

Under Reports > Retention, check the 'User retention by cohort' table weekly for stores with recurring or repeat-purchase products. For a Shopify store, pairing this with Shopify's own Customers > Customer cohort analysis report tends to be more reliable for purchase-specific retention since it's tied directly to order data rather than GA4's session-based user model, which can undercount returning users across devices without strong sign-in signals. Use GA4's version mainly to spot broad engagement trend changes, and use Shopify's native report for actual repeat-purchase decisions.

6. The Advertising snapshot — cross-checking Enhanced Conversions

If Google Enhanced Conversions is configured, the Reports > Advertising > Advertising snapshot shows Google Ads-attributed conversions inside GA4 pulled from the linked Google Ads account. Weekly, compare this figure against Google Ads' own conversion count reported directly in the Google Ads interface. They should be close but not always identical due to different attribution windows and conversion delay handling; a large and growing gap over several weeks suggests the Google Ads and GA4 property link, set up under Admin > Product links > Google Ads Linking, needs re-authorization.

Setting up the weekly routine efficiently

Rather than navigating GA4's menu fresh every week, save each of these views as an Exploration or bookmark it directly. Under Explore > Blank, build a single exploration with Session default channel group as rows, sessions/conversions/revenue as values, and a date range comparison built in — this collapses steps 1 and 3 above into one screen you can check in under two minutes. Bookmark it and revisit the same exploration weekly rather than rebuilding filters from the standard reports each time.

What NOT to check weekly

Skip GA4's demographic and interest reports weekly — they're based on modeled Google Signals data with wide margins of error at typical Shopify store traffic volumes and rarely change enough week to week to justify the time. Skip the Tech overview report (device/browser breakdown) unless you're actively debugging a specific rendering issue. And skip the default Home dashboard entirely; its auto-generated 'insights' are frequently just restating obvious seasonal patterns rather than surfacing anything actionable for a weekly cadence.

Handling data thresholding and sampling

Small Shopify stores often see 'thresholding applied' warnings on GA4 reports, particularly demographic and geographic breakdowns, when Google Signals is enabled and a segment has too few users to report without risking re-identification. This is normal and by design per Google's privacy documentation, not a tracking failure — it mainly appears on granular breakdowns, not on the core acquisition and ecommerce reports described above, which is another reason to build the weekly routine around those less-thresholded reports.

Monthly additions to the weekly routine

Once a month, extend the routine to include Reports > Life cycle > Monetization > Purchase journey (if available in your property configuration) to check average days-to-purchase and path length, which helps validate whether your attribution windows on Google Ads and Meta campaigns are set appropriately. If most purchases happen 5+ days after first click, a 1-day click attribution window on Meta would be systematically undercounting conversions, a mismatch worth catching monthly even if it's not a weekly check.

Connecting GA4 findings to campaign action

The point of a weekly GA4 review isn't the review itself, it's the decision it produces. Each week, aim to leave the routine with at least one concrete action: pause or fix a campaign with a broken landing page, re-verify a tracking gap, or flag a channel discrepancy to investigate. If a week's review produces no actionable finding, that's fine too, but the discipline of a consistent five-report routine, done every week regardless of how busy the store is, catches tracking breakage far earlier than an ad-hoc 'check GA4 when something feels off' approach.

For merchants running Adsify, this weekly GA4 routine complements rather than duplicates the app's own reporting: Adsify's profit and POAS tracking pulls from order and ad spend data directly rather than GA4's session model, so use GA4 specifically for on-site behavior and cross-channel session attribution questions that ad-spend-level profit tracking doesn't answer, like which landing pages underperform after the click or whether a channel's session volume matches expectations.

Frequently asked questions

How long should a weekly GA4 review take?

With saved explorations and a fixed report list, 15-20 minutes is realistic for most single-store Shopify merchants.

Why don't my GA4 and Shopify order counts match exactly?

Timezone settings, event deduplication differences, and purchase event timing versus Shopify's order timestamp create small, normal discrepancies; large gaps signal a tracking issue.

Is Google Signals necessary for these reports?

It's not required for acquisition or ecommerce purchase reports, but it improves cross-device user matching for retention reporting; enable it under Admin > Data collection if you want that.

What does 'thresholding applied' mean in a GA4 report?

Google withholds data on some breakdowns when the underlying user count is too small to report without privacy risk; it's a documented behavior, not an error.

Sources

Try Adsify free for 7 days

Launch AI-powered Google & Meta ads for your Shopify store in one click. See pricing or the full feature list.

Install from Shopify App Store →

Keep reading on Tracking & Attribution