Migrating from GA4 to HitCounters

Last updated 2026-04-28

Switching analytics tools sounds scarier than it is. You can run HitCounters and GA4 side by side for as long as you want before turning off GA4 — the two don't conflict. Here's the practical path.

The 30-second version

  1. Install HitCounters alongside GA4 (don't remove GA4 yet).
  2. Watch both for 1-2 weeks to confirm data parity.
  3. Recreate your GA4 goals as HitCounters goals.
  4. Recreate any UTM-tagged campaigns (links keep working).
  5. Turn off GA4 when you're confident.

Step 1: Install HitCounters in parallel

Sign up at hitcounters.com, add your domain, and grab the tracking code. Drop it in your site's <head> — right next to your existing GA4 / GTM tag is fine. They don't interfere.

If you use Google Tag Manager, add HitCounters as a separate Custom HTML tag with an All Pages trigger. Detailed steps: GTM install guide.

Step 2: Verify both tools see traffic

Open your site in a private window. Within seconds:

  • HitCounters shows the visit on the dashboard in real time.
  • GA4 shows the visit in Realtime → Overview (usually within 30 seconds).

If both register the same visit, you're done with the install side.

Step 3: Compare numbers for 1-2 weeks

Don't panic when the numbers don't match exactly. They won't — ever. Reasons they differ:

  • Bot filtering. HitCounters scores every visit and flags bots; GA4 has weaker bot filtering and silently keeps a lot of bot traffic.
  • Cookie banners. If you have a consent gate that blocks GA4 until accepted but doesn't block HitCounters (we don't need consent), HitCounters will record more visits.
  • Sampling. GA4 samples once you cross thresholds. HitCounters never samples.
  • Time zones. Make sure both tools are set to the same time zone before comparing day-by-day.

Generally HitCounters reports more real visits and fewer bot visits than GA4. That's healthy.

Step 4: Recreate your goals

GA4 calls them "Conversions" or "Key Events." Same idea, different syntax:

GA4 eventHitCounters equivalent
page_view on /thank-youURL goal: contains /thank-you
Custom event sign_upEvent goal: signup — fire hcEvent('signup')
Custom event purchase with valueEvent goal: purchase — fire hcEvent('purchase', 49.99)
"Engaged session" auto-eventBuilt in: see Engagement card on Summary page

Set up goals on the Goals page. Full goals guide.

Step 5: UTM tags keep working

Existing campaigns that used GA4-style UTM parameters work as-is in HitCounters. The utm_source, utm_medium, utm_campaign, utm_term, utm_content fields all surface on the Reports → Campaigns tab.

For new campaigns, use our UTM builder — same syntax Google uses.

Step 6: Turn off GA4 (when ready)

Once you're confident:

  • Remove the GA4 tag from your site (or the GTM tag).
  • Or just leave it — GA4 is free and dual-tagging doesn't hurt anything.

Optionally, in GA4 you can go to Admin → Property → Property Settings and stop data collection. Existing data stays accessible until July 2027 (Google's announced retention).

What you gain

  • Real-time visitor logs you can actually read
  • AI traffic detection (ChatGPT, Claude, Perplexity, Gemini, Copilot) as a separate source
  • Engagement scoring without writing custom event code
  • No cookie banner needed
  • A dashboard you don't need a course to navigate

What you lose

  • Multi-touch attribution / channel grouping — GA4 has more sophisticated attribution if you actually use it.
  • Audience segments synced to Google Ads — if you bid on Google Ads with custom audiences, keep GA4 in parallel.
  • BigQuery export — GA4 lets you stream raw events to BigQuery; HitCounters exports CSV instead.

For most websites — bloggers, indie SaaS, agencies, content sites — nothing in that list matters. For an e-commerce store running paid Google Ads campaigns, dual-track and use both.

Related articles

Still need help? Send us a message — we reply within 24 hours.