Migrating from Universal Analytics to GA4: Pitfalls to Avoid
· 10 min · Google Analytics
GA4 isn’t a “new UA”—it’s a different measurement model. Avoid the migration mistakes that break attribution, inflate conversions, and erase reporting continuity.
Migrating from Universal Analytics (UA) to Google Analytics 4 (GA4) is less like a software upgrade and more like switching measurement philosophies. UA focused on sessions and pageviews; GA4 is built around events, users, and cross-device behavior.
Many teams “install GA4” and assume the job is done—only to discover weeks later that conversions don’t match, attribution looks wrong, and critical reports are missing. This article walks through the most common pitfalls and how to avoid them with practical steps, realistic benchmarks, and examples.
1) Don’t treat GA4 as a 1:1 replacement for UA GA4 can answer many of the same business questions as UA, but not in the same way. The fastest route to frustration is expecting identical metrics and reports.
Key differences that cause migration surprises • Data model: UA is session-based; GA4 is event-based. • Engagement: GA4 replaces “Bounce Rate” emphasis with Engaged sessions and Engagement rate. • Attribution defaults: GA4 uses data-driven attribution by default (eligible properties), while many UA setups relied on last non-direct click. • Sampling and limits: GA4 is less prone to sampling in standard reports, but has exploration limits and different query behaviors.
Realistic benchmark: why your numbers won’t match It’s normal for GA4 and UA to disagree—even with perfect implementation. • Users: GA4 “Active users” often differs from UA “Users.” Variance of 5–20% is common during parallel tracking. • Sessions: GA4 sessions can be 5–15% lower due to different session handling. • Bounce rate: If you compare UA bounce rate to GA4 engagement rate, you may think performance “improved overnight.” It didn’t—you changed definitions.
Actionable guidance Define your “source of truth” KPIs (leads, purchases, revenue) and map them to GA4 equivalents. Document metric definitions in plain English (what it includes, excludes, and how it’s calculated). Run parallel tracking (UA historical vs GA4 new) long enough to establish baselines for seasonality—typically 4–8 weeks for most sites, longer for low-traffic businesses.
2) Pitfall: migrating without a tracking plan (and losing critical events) Because GA4 is event-first, the biggest risk is not “missing a pageview,” but failing to capture the actions that matter: form submits, purchases, sign-ups, downloads, phone clicks, and key funnel steps.
What commonly breaks • Form submissions tracked in UA via Event Category/Action/Label but not recreated in GA4 • Ecommerce events missing required parameters (e.g., item arrays) • Cross-domain journeys split into separate sessions • Conversion counts inflated by tracking the same action multiple times (e.g., button click + thank-you page view)
A practical tracking plan template Build a simple spec before implementation. Your plan should include: • Business goal (e.g., “Request a quote”) • GA4 event name (e.g., generate_lead) • Trigger definition (what exactly fires it) • Parameters (e.g., form_id, lead_type, value) • Conversion? (yes/no) • Owner (who maintains it)
Real-world example: lead gen site A B2B company tracked leads in UA using a thank-you page destination goal. After moving to GA4, they tracked both: • form_submit event on click • page_view of /thank-you/
Result: conversions were nearly 2x overnight. The fix was to choose one canonical conversion event (typically the server-confirmed thank-you page or a confirmed submit callback) and keep the other as a supporting event.
Actionable steps List your top 10–20 user actions that drive revenue. For each, decide whether it’s best measured by: - A page load (thank-you page) - A client-side event (click/submit) - A server-side event (recommended for purchases and critical leads) Implement events in Google Tag Manager (GTM) with clear naming and parameters. Mark only the events that represent true business outcomes as Conversions.
3) Pitfall: messy event naming and parameters (making reports unusable) GA4 is flexible, but that flexibility can create chaos. If one team uses formSubmit, another uses form_submit, and a third uses lead, you’ll end up with fragmented reporting and unreliable conversions.
GA4 event naming rules that trip teams up • Event names should be lowercase with underscores (recommended) • Avoid spaces and special characters • Keep names stable over time (renaming breaks continuity)
Recommended naming conventions (actionable) • Use Google’s recommended events when they match your use case: - purchase, generate_lead, sign_up, login, add_to_cart • Use custom events only when necessary and keep them consistent: - pricing_view, demo_request_submit, quote_step_completed
Parameter discipline: the difference between “tracked” and “useful” If you don’t standardize parameters, you’ll struggle to segment performance. • Good parameters for lead gen: - form_id, form_name, lead_type, page_category • Good parameters for content: - content_type, author, topic, word_count_bucket
Realistic benchmark: how m…