Switching your analytics stack is not a five-minute decision, but it is also not as complicated as staying on a tool that increasingly conflicts with your compliance posture. This guide covers what to do before, during, and after a move from Google Analytics 4 to a cookieless, EU-hosted alternative — practically, without overselling what you gain or understating what you lose.
Quick answer
Before you switch, export your historical GA4 data and document your key metrics baselines — the numbers will not be comparable after the migration because the two tools measure differently. Run both tools in parallel for at least four weeks to understand the delta. Expect cookieless tools to show higher unique visitor counts for returning-visitor-heavy sites. You keep aggregate traffic metrics, referrers, UTM campaign data, and device breakdowns. You lose precise cross-day individual user journeys, multi-session attribution, and the entire Google ecosystem (Ads integration, Search Console native connection, GA360 reporting). For most European SMBs doing aggregate traffic analysis and campaign measurement, the trade-off is worth it.
Key takeaways
- Export your GA4 historical data before you delete the property or let the retention period expire. GA4 retains event data for 2 or 14 months depending on your settings — once it is gone, it is gone.
- Run GA4 and your new tool in parallel for a full four-week cycle before cutting over. The numbers will differ, and you need a baseline to understand why.
- Cookieless tools typically count unique visitors higher for returning-visitor-heavy sites, because the daily hash treats the same physical user as a new visitor each day.
- Session, bounce rate, and conversion definitions differ between tools. Map them explicitly before you report.
- What you lose: individual user journeys across days, multi-session attribution, Google Ads integration, and GA360 features. These are real losses — evaluate them honestly against your actual use cases.
- What you gain: no analytics tracking cookies (which removes the cookie-consent trigger for the analytics layer specifically), EU-hosted infrastructure, and a simpler dashboard with no data sampling within your plan quota.
Definitions
Billable event: in Atriqo's context, any event persisted to the analytics database — a pageview, outbound click, file download, 404 page hit, or custom event. This is the quota unit, not "pageviews" alone. A page that triggers a pageview and an outbound click counts as two billable events.
GDPR-native by design: a product positioning claim (not a compliance certification) meaning the tool was designed around EU data protection principles from the ground up. Switching to a GDPR-native tool does not make your whole site compliant — your other vendors, embeds, and pixels each carry their own obligations.
Daily hash: the session identification mechanism used by cookieless analytics. A cryptographic hash of the visitor's IP address, user agent, and a daily-rotating salt. The same physical visitor tomorrow produces a different hash — which is what makes multi-day individual tracking impossible without cookies.
Step 1: Export your GA4 data before you leave
GA4 data does not transfer to a new tool. Before you deactivate your GA4 property, export everything you might need for year-over-year comparisons, compliance reporting, or historical reference.
What to export:
- Traffic overview by channel (organic, direct, referral, paid, social) — monthly, for the last 24 months minimum.
- Top pages by pageviews and engagement rate — at least the trailing 12 months.
- UTM campaign performance — source, medium, campaign breakdowns.
- Conversion events and goal completions — if you have them configured, download the raw counts.
- Geographic breakdown — country-level at minimum.
- Device category breakdown.
How to export from GA4:
In the GA4 interface, use the standard reports under Reports > Acquisition, Engagement, and Conversions. Each report has an export button (top right) for CSV or Google Sheets. For a more complete export, use the GA4 Data API or BigQuery export if you have it enabled. The BigQuery raw-event export is the most complete format — if you have it set up, export the event tables covering your full retention window.
GA4 data retention is bounded. GA4 retains event-level data for either 2 months or 14 months depending on your property settings (found in Admin > Data Settings > Data Retention). Aggregated reports in the GA4 interface may show data beyond that window, but the underlying event data used for custom exploration reports is deleted after the retention period. Check your setting now — if you are on the 2-month default, you may already be losing historical granularity.
Step 2: Document your current metric baselines
Before you run both tools in parallel, write down your current numbers. This sounds obvious and is consistently skipped.
The numbers that matter most for comparison:
- Average monthly sessions over the last 3 months.
- Average monthly users (GA4's "active users" definition: users with at least one engaged session).
- Bounce rate (GA4 defines this as the opposite of engagement rate — sessions with no engaged interactions. Cookieless tools typically define bounce as sessions with exactly one pageview).
- Top 5–10 pages by pageviews.
- Top 3–5 traffic sources by sessions.
- Primary conversion event count (if you track conversions in GA4).
Why this matters: when you look at your new tool's numbers four weeks in and they do not match GA4, you will want to understand whether the delta is methodological (expected) or a tracking problem (fixable). Having documented baselines makes that diagnosis possible.
Step 3: Install the new tracker and run in parallel
Install your cookieless analytics tracker alongside GA4, not instead of it. Both should be active for a minimum of four weeks — ideally a full calendar month to capture weekly patterns.
For Atriqo (currently in development — join the waitlist for early access; the steps below describe the flow at launch):
Add the tracker script to your site's <head>. It does not set cookies, so it does not require consent banner gating in jurisdictions where consent is driven by cookie placement. Your existing GA4 consent flow applies to GA4 independently — you do not need to remove it until you remove GA4.
The free tier — 10,000 billable events per month, no credit card required, no expiry — covers most small and medium sites during the parallel period.
What to check during parallel running:
- Pageview counts between the two tools for your top 5 pages. Expect some delta — GA4 and cookieless tools handle bot filtering, self-traffic exclusion, and session definition differently.
- Unique visitor counts: cookieless tools will typically count higher for returning-visitor-heavy sites, because the daily hash treats the same user differently each day.
- UTM campaign attribution: check that your UTM parameters are passing through correctly. Cookieless tools read UTMs from the URL the same way GA4 does — if UTMs work in GA4, they work in the new tool.
- Real-time panel: verify that events are appearing in real-time immediately after install.
Step 4: Understand what the metrics mean — and where they differ
This is the most important section of the migration guide. The metric names look the same; the definitions are not.
Sessions
GA4: a session starts with the first event and ends after 30 minutes of inactivity. (Universal Analytics also reset sessions at midnight and on campaign-source changes; GA4 dropped both behaviours.)
Cookieless analytics (Atriqo): a session uses a 30-minute inactivity window. The same visitor tomorrow starts a new session with a new hash — there is no cross-day session continuation.
Practical implication: session counts should be broadly comparable for within-day visits. Multi-day differences will diverge because the daily hash resets.
Bounce rate
GA4: bounce rate is the inverse of engagement rate. A session "bounces" in GA4 when it has fewer than 10 seconds of engagement, no conversion event, and fewer than 2 pageviews. Note: this means a quick read of a 500-word article with no other interaction is a bounce in GA4.
Cookieless analytics (Atriqo): bounce rate is the percentage of sessions with exactly one pageview. Custom events, outbound clicks, and file downloads that fire in the same session do not prevent a bounce — only a second pageview does.
Practical implication: these are measuring different things. Atriqo's bounce rate will be higher than GA4's for most content sites, because GA4's engagement-based definition excludes many single-pageview sessions that Atriqo counts as bounces. Neither is wrong — they are different definitions. Document which definition you are using in your reports.
Unique visitors / users
GA4: "users" are tracked by a persistent client ID stored in the _ga cookie, plus cross-device data from signed-in Google accounts if Google Signals is enabled. A user who visits on Monday and Wednesday is counted as one user.
Cookieless analytics (Atriqo): unique visitors within a day are based on the daily hash. The same physical person visiting on Monday and Wednesday is counted as two distinct visitors. Monthly unique visitor totals are an aggregate of daily hash counts — they overcount returning visitors relative to GA4.
Practical implication: for sites with a high proportion of returning visitors (membership sites, newsletters with loyal readership), cookieless tools will show meaningfully higher unique visitor counts. For high-churn acquisition-focused sites where most visitors arrive once and leave, the delta will be smaller.
Real-time active visitors
GA4: shows users active in the last 5 minutes, based on the persistent client ID.
Atriqo: shows a count of distinct visitor hashes seen in the last 5 minutes across pageview events. Because hashes are daily, the count is an accurate same-day snapshot; it does not attempt to de-duplicate same-user across days.
Conversion tracking
GA4: conversions can be any event, tracked across multiple sessions. A purchase that starts with an ad click on Day 1 and completes on Day 3 can be attributed to the original session if the session data is preserved.
Cookieless analytics (Atriqo): conversion goals are same-session and same-day. A visitor who sees your pricing page on Monday and purchases on Wednesday will not be linked as a single conversion funnel — the hash changes daily. For products where the typical purchase decision and completion happen within a single session (e.g. SaaS trials that start immediately after signup, direct-purchase e-commerce), same-session conversion tracking is accurate. For products with longer consideration cycles, this is a real limitation.
Step 5: What you lose — honestly
The cookieless architecture solves the compliance friction problem, but it is not a feature-complete replacement for GA4 in every use case. Here is what you lose:
Cross-day individual user journeys. You cannot follow a specific user across multiple days. If you need to know "this user visited the features page on Tuesday, the pricing page on Thursday, and signed up on Saturday" as an individual journey, that is not possible with daily-rotating hashes.
Multi-session attribution. Related to the above. Revenue attribution for purchases that span multiple sessions requires persistent identifiers. Cookieless tools give you last-session attribution (what UTM source and page the conversion happened on), but not multi-touch attribution across weeks.
Google Ads integration. If you are running Google Ads and using GA4 for conversion import, audience creation, or smart bidding optimization, those integrations are Google-ecosystem-only. Switching analytics tools does not affect your Google Ads account directly, but you lose the native conversion feedback loop into Google's bidding algorithms.
Google Search Console native connection. GA4 has a native Search Console integration that surfaces organic search queries, clicks, and impressions alongside your behavioral data. Privacy-first analytics tools typically do not have this integration natively. You can still use Search Console directly — you just lose the combined view.
Behavioral segments and audiences. GA4's audience builder and behavioral segmentation are far more granular than what cookieless analytics provides. If your marketing relies on remarketing audiences built from GA4 behavior data, that capability disappears.
Data sampling. GA4's free tier applies data sampling above certain thresholds in exploration reports, which can affect accuracy. Atriqo does not sample within your plan quota — every event is counted. Over-quota behaviour is plan-dependent and visible, never silent: on the free tier, events beyond the monthly cap are not stored; on paid tiers, sustained traffic above 110% of quota switches to clearly-labelled sampling (the dashboard shows "sampling active") instead of dropping data silently. Either way, the numbers will not match GA4 even when they "should."
Step 6: What you gain — specifically
No analytics tracking cookies means no cookie consent trigger for the analytics layer. If GA4 was the reason you had a cookie consent banner, removing it removes that specific obligation. Your site may still need a banner if you have other vendors, pixels, embeds, or ad networks — check your full vendor stack.
EU-hosted infrastructure removes the GDPR Article 44 transfer question for the analytics tool. Data collected in the EU stays in the EU. The documented DPA concern about EU-US transfers (covered in the Austrian, French, and Italian decisions of 2022) does not apply to a tool hosted entirely in Europe.
No sampling within quota. Inside your plan's monthly quota, every event is counted and stored — your reports reflect actual traffic, not a statistical sample. (Over-quota behaviour is plan-dependent and always shown in the dashboard, never silent.)
Simpler setup and maintenance. No Consent Mode configuration. No cookie policy table updates for the analytics tool. No CMP integration. Add the script tag, check the first event appears, done.
A dashboard you can actually read. GA4's interface has a steep learning curve and many features that most teams never use. Privacy-first analytics tools prioritize the metrics that matter for most decisions — traffic trends, top pages, referrer sources, UTM performance, device breakdown — in a fast, simple dashboard.
Step 7: The parallel running period and cutting over
Do not cut over until you understand the delta between the two tools. Four weeks minimum; a full calendar month is better.
At the end of the parallel period, answer these questions:
- What is the ratio of cookieless tool pageviews to GA4 pageviews for your top 5 pages? If it is consistently 0.95–1.05, the tools agree well. If it is consistently 0.7 or 1.4, investigate why before cutting over.
- Are your UTM campaign attributions landing correctly in the new tool? Check that your top UTM sources and campaigns appear.
- Are conversion events firing as expected? If you have custom events in GA4, check that the equivalent events are configured in the new tool.
- Have you exported the historical GA4 data you need (Step 1)?
Cutting over:
When you are confident in the new tool, remove the GA4 snippet from your site. You do not need to delete the GA4 property immediately — data continues to be visible in the GA4 interface even after you stop sending events. Keep the property accessible for historical reference.
If you have Google Ads conversion tracking through GA4, set up direct conversion tracking in Google Ads before removing GA4 (Google Ads can track conversions independently of GA4 through its own tag or through server-side conversion upload).
The historical data gap:
Accept that your historical data in the new tool starts from zero on the day you install it. Year-over-year comparisons for the first year will require comparing cookieless tool current-year data against GA4 historical data — manually. This is an inherent cost of switching. Plan your reporting accordingly.
Facts vs interpretation
Documented facts: GA4 sets _ga and _ga_* cookies by default (Google developer docs). European DPAs issued decisions in 2022 against specific uses of Google Analytics involving EU-US data transfers (Austria, France, Italy). GA4 event-level data retention is bounded at 2 or 14 months depending on property settings. Cookieless analytics tools use a daily-rotating hash that makes cross-day individual user tracking impossible by design.
Our interpretation: That these facts make switching worthwhile for most European SMBs is Atriqo's commercial position. For teams with heavy reliance on Google Ads integration, cross-session attribution, or behavioral segmentation, the trade-off may not be worth it. Evaluate your actual use cases against the limitations above before deciding.
This article does not constitute legal advice. Whether your specific use of Google Analytics raises compliance concerns depends on your configuration, your jurisdiction, and your legal counsel's guidance.
Getting started with Atriqo
Atriqo is a privacy-first, cookieless web analytics tool, hosted in the EU (Germany), built as a GDPR-native-by-design alternative to Google Analytics.
The free tier — 10,000 billable events per month (a billable event is any tracked event: pageview, outbound click, file download, 404, or custom event), no credit card required, no expiry — is available at launch. It covers most small sites through the parallel running period and beyond.
If you want early access, join the waitlist.
This guide describes the practical process of migrating from Google Analytics 4 to cookieless analytics and explains how the two tools differ technically. It does not constitute legal advice. For specific compliance guidance on your site's vendor stack and analytics configuration, consult a qualified legal professional familiar with EU data protection law.