Measurement comes before diagnosis
A Shopify migration traffic drop cannot be diagnosed until GA4, Search Console, ecommerce events, consent behaviour and Shopify order data have been checked.
Track the final customer journey
Test product views, collection visits, add-to-cart, checkout entry, purchase, enquiry forms and outbound affiliate clicks where relevant. Do not stop after confirming that page_view fires.
Keep a launch annotation log
Record DNS changes, theme changes, redirect imports, tracking updates, consent changes and app installs so post-launch reports can separate real SEO movement from measurement noise.
A Shopify migration analytics QA process is not about checking tags.
It is about deciding whether the data can be trusted.
Most migration analysis fails because teams start diagnosing SEO before confirming that GA4, Shopify analytics and tracking events are working correctly.
That leads to the wrong fixes.
Measurement needs to be validated first, so traffic, revenue and conversion changes can be interpreted correctly.
Why tracking QA fails
Most tracking QA fails for predictable reasons:
- testing happens after launch instead of before
- only page views are checked, not ecommerce events
- consent behaviour is not tested properly
- GA4 is assumed to be correct without validation
- Shopify analytics is not used as a comparison
- results are not logged
The result is data that looks plausible but cannot be trusted.
What you are actually validating
You are not validating tags.
You are validating:
- whether sessions are recorded correctly
- whether revenue is recorded correctly
- whether attribution is preserved
- whether events reflect real user behaviour
- whether different systems agree with each other
The goal is not perfect data. It is reliable data.
Tracking priority order
Check tracking in this order:
- Purchase and revenue tracking
- Checkout and conversion flow
- GA4 event accuracy
- Shopify analytics comparison
- Consent behaviour
- Channel attribution
- Supporting events (forms, downloads, outbound clicks)
If purchase tracking is broken, nothing else matters.
The first question is not “did SEO drop?”
The first question is:
Can we trust the numbers?
Before anyone diagnoses rankings, redirects or content loss, check whether the new Shopify store is measuring the same things as the old site.
A migration can change:
- the checkout flow
- thank-you page behaviour
- ecommerce event names
- product IDs and SKUs
- consent banner behaviour
- pixel loading order
- channel attribution
- URL paths
- referral handling
- form and resource-download tracking
If those change without a QA process, reports become misleading exactly when the business needs them most.
This prevents false SEO conclusions.
What to capture before launch
Do not wait until the new store is live to decide what “normal” looked like.
Before launch, export or screenshot:
- GA4 organic sessions, revenue and conversion data
- Shopify or WooCommerce order totals
- Search Console clicks, impressions and top landing pages
- top organic collection/category pages
- top organic product pages
- top blog or guide pages
- paid search and paid social conversion baselines
- email and direct traffic baselines
- current ecommerce event names
- current conversion names
- current pixel list
This gives you a comparison point if the new store launches and the reports suddenly look wrong.
What good tracking QA produces
A strong tracking QA process produces:
- confirmed purchase tracking
- consistent revenue across systems
- reliable attribution
- validated event structure
- a clear comparison baseline
- confidence in post-launch reporting
If tracking QA does not produce these, it is incomplete.
GA4 checks before the Shopify store goes live
Check GA4 in a staging or preview environment where possible.
Confirm:
- the correct GA4 property is connected
- page views fire once per page
- ecommerce events fire in the expected order
- add-to-cart events include product data
- checkout events are recorded where supported
- purchase events fire only once
- transaction IDs are present
- item names, IDs, prices and quantities are populated
- cross-domain or checkout referral issues are understood
- internal staff traffic is filtered or annotated
Do not just check that GA4 is receiving traffic. Check whether it is receiving meaningful ecommerce data.
If events fire but lack product or revenue data, treat reports as incomplete.
Shopify analytics checks
Shopify analytics should not be treated as a replacement for GA4, but it is useful as a sanity check.
After launch, compare:
- Shopify order count vs GA4 purchases
- Shopify revenue vs GA4 revenue
- Shopify conversion rate vs GA4 conversion rate
- Shopify traffic trends vs GA4 sessions
- Shopify top products vs GA4 item reports
The numbers will rarely match exactly. That is normal. What matters is whether the difference is explainable and consistent.
If Shopify orders exist but GA4 shows zero purchases, fix tracking before any SEO work.
If revenue drops only in GA4, treat it as a measurement issue first.
When GA4 and Shopify disagree
Some difference is normal. Perfect agreement is not the goal.
What matters is whether the difference is explainable.
| Pattern | Likely concern | First action |
|---|---|---|
| Shopify orders continue, GA4 purchases fall sharply | Purchase event, checkout or consent issue | Test checkout and purchase events before SEO changes |
| GA4 sessions drop, Search Console clicks stay stable | Analytics loading, consent or channel grouping issue | Check page view firing and attribution rules |
| GA4 revenue rises, Shopify revenue does not | Duplicate purchase events or value inflation | Check transaction IDs and duplicate firing |
| Shopify and GA4 both drop, Search Console also drops | Real search or conversion loss is more likely | Move into redirect, indexation and page-type diagnosis |
The point is not to pick a favourite dashboard. It is to decide which system answers the question in front of you.
Consent and cookie checks
Consent behaviour can change during a migration.
Check:
- analytics scripts before consent
- analytics scripts after consent
- marketing pixels before consent
- marketing pixels after consent
- rejected-consent behaviour
- region-specific behaviour if relevant
- whether the privacy policy matches the actual setup
Do not write privacy wording that claims a preference centre or opt-in process exists unless it actually does.
If consent blocks analytics, test accepted vs rejected states before diagnosing traffic.
Pixel and paid-media checks
If the store uses paid media, the migration can break optimisation even if SEO is fine.
Check:
- Meta pixel
- Google Ads conversion tags
- TikTok pixel
- Pinterest tag
- affiliate tracking
- email platform tracking
- server-side or customer-event pixels
For each one, record:
- where it is installed
- what event it fires
- whether purchase value is passed
- whether duplicate events are present
- who owns the account
- how it will be tested after launch
Search Console checks
Search Console will not confirm ecommerce tracking, but it tells you whether organic search visibility is changing.
Check:
- correct domain property access
- sitemap submission after launch
- important new URLs indexed or crawlable
- important old URLs redirecting
- top landing pages before and after launch
- clicks and impressions by page type
- branded vs non-branded trend
Do not diagnose traffic drops from GA4 alone. Search Console gives you the search-side view.
If Search Console clicks are stable but GA4 sessions drop, investigate analytics configuration.
Launch-day analytics QA
On launch day, test a real customer journey.
A full journey test is required, not just page views.
Record:
- homepage page view
- collection page view
- product page view
- search or filter interaction where relevant
- add to cart
- checkout start
- purchase
- email signup
- contact form
- resource download
- paid ad landing page
Use a QA log with owner, expected result, actual result, severity and fix status.
First 24 hours
During the first day, look for obvious tracking breaks:
- zero purchases in GA4 despite Shopify orders
- paid media spend with no conversions
- organic revenue suddenly disappearing while Shopify revenue continues
- self-referrals from checkout or payment providers
- duplicate purchase events
- missing item data
- campaign traffic moving into direct
These are measurement issues until proven otherwise.
First 14 days
After the first day, compare trends rather than isolated numbers.
Segment by:
- organic landing page type
- collection pages
- product pages
- blog or guide pages
- paid traffic
- email traffic
- direct traffic
- device type
If organic clicks are stable in Search Console but GA4 organic revenue collapses, investigate tracking and attribution first. If Search Console clicks fall for important old URLs, investigate redirects, indexation and page changes.
If attribution shifts suddenly, check redirects, UTMs and referral handling.
Severity levels
Use clear severity labels so analytics problems do not sit unresolved.
P1: purchase tracking broken, checkout conversion missing, paid pixels not firing, or reporting cannot be trusted.
P2: ecommerce item data incomplete, attribution distorted, important forms/downloads not tracked.
P3: non-critical event naming issues, dashboard formatting, secondary channel issues.
P4: documentation or reporting improvements.
Minimum analytics QA sheet
Your sheet should include:
- test area
- platform
- event or metric
- old-site baseline
- expected new behaviour
- actual result
- severity
- owner
- fix
- retest date
- notes
The aim is not perfect analytics. The aim is making the migration measurable enough that SEO, paid media and trading decisions are not based on broken data.
If tracking cannot be trusted, pause analysis until it is fixed.
Annotations are essential for interpreting data changes.
For post-launch monitoring, use the Post-Migration Monitoring Sheet.
For launch checks across redirects, crawl, analytics and checkout, use the Migration QA Checklist.
The practical rule
A Shopify migration does not fail because traffic drops.
It fails when you cannot tell why.
Tracking QA exists to remove that uncertainty.
Without it, every decision becomes guesswork.
Quick answer
Validate GA4, Search Console, Shopify order tracking, consent behaviour, forms and ecommerce events before diagnosing any migration traffic or revenue movement.
What you will do
- Separate real SEO movement from broken measurement.
- Confirm purchase, form and outbound tracking after launch.
- Create an annotation trail for domain, theme, redirect and tracking changes.
What to check first
- GA4 Realtime or DebugView.
- Shopify order and analytics reports.
- Google Search Console URL inspection and sitemap submission.
- Consent banner test mode or browser checks.
- Launch annotation sheet and migration issue log.
Work through it in this order
- List every measurement system: GA4, Search Console, Shopify reports, ad pixels, consent banner, forms and affiliate/outbound events.
- Check the GA4 stream and tag installation on the final Shopify domain.
- Run a test journey through homepage, collection, product, cart, checkout and purchase where possible.
- Confirm the test order appears in Shopify and the expected GA4 ecommerce event appears with transaction and revenue data.
- Verify Search Console for the final canonical domain and submit the sitemap index.
- Record launch annotations for DNS, theme, redirect import, consent changes, tag changes and app installs.
- Review Day 1 and Week 1 reports before treating any traffic change as an SEO failure.
Real-world notes
- Migration traffic drops often look dramatic when GA4 is duplicated, blocked by consent, or missing purchase events after checkout changes.
- Search Console mistakes are common when the team verifies the wrong protocol, `www` version or old domain property.
- If UTM parameters are stripped by redirects, paid and email traffic can be misread as direct or organic.
Final checks
- GA4 tag fires on live Shopify templates.
- Duplicate GA4 tags checked.
- Consent behaviour tested.
- Test order completed.
- Purchase event carries transaction ID and revenue.
- Search Console property matches final canonical domain.
- Sitemap submitted.
- Forms and outbound clicks tested.
- Launch annotations saved.
Watch-outs
- If checkout tracking depends on Shopify settings or apps, page_view alone is not enough evidence.
- If a consent banner changed during migration, compare accepted and rejected consent states before judging traffic.
- If redirects strip query strings, paid campaigns and email journeys may work visually but lose attribution.
Validate tracking before diagnosing the traffic drop; otherwise the team may fix SEO problems that do not exist.
Field questions
What tracking should be checked after a Shopify migration?
Check GA4 page views, ecommerce events, purchase events, consent behaviour, Search Console property access, sitemap submission, Shopify orders, paid pixels, enquiry forms and affiliate/outbound click tracking where relevant.
Why can traffic look wrong after moving to Shopify?
Traffic can look wrong because GA4 tags are missing, consent mode changed, ecommerce events stopped firing, checkout tracking differs, channel grouping changed or the wrong Search Console property is being reviewed.
When should analytics QA happen?
Run tracking QA on staging where possible, immediately after launch, after the first test order, and again after the first full day of real traffic.
