Google Analytics 4

60-90 minAdvanced

Google Analytics 4 (GA4) provides essential traffic and engagement data for your Blogger blog. Since Blogger is a Google product, integration is straightforward. This guide covers the native integration method and manual installation for advanced tracking needs.

Prerequisites

  • Google Analytics account
  • GA4 property created
  • GA4 Measurement ID (G-XXXXXXXXXX)
  • Blogger admin access
Easy Recommended

Native Blogger Integration (Recommended)

Blogger has built-in Google Analytics support. This is the easiest and most reliable method.

1

Get Your GA4 Measurement ID

1

Sign in to Google Analytics (analytics.google.com)

2

Select your GA4 property

3

Go to Admin (gear icon, bottom left)

4

Under 'Property', click 'Data Streams'

5

Click on your web stream

6

Copy the 'Measurement ID' (starts with G-)

If you don't have a GA4 property, click 'Create Property' in Admin
2

Add to Blogger

1

Go to your Blogger dashboard

2

Click 'Settings' in the left menu

3

Scroll to 'Google Analytics Property ID' (under Basic)

4

Paste your G-XXXXXXXXXX Measurement ID

5

Click 'Save' (settings auto-save in new Blogger)

3

Verify Installation

1

Open your blog in a new browser tab

2

Return to Google Analytics

3

Go to Reports > Realtime

4

You should see '1 user in last 30 minutes' (that's you)

5

Navigate around your blog to confirm page views are tracked

Best Practices

Do

  • Use the native Blogger integration first—it's simplest
  • Verify tracking in Realtime report before considering it 'done'
  • Set up both GA4 and Search Console for full SEO insights
  • Create custom events for important actions (clicks, downloads)
  • Exclude your own traffic using IP filters in GA4
  • Connect GA4 to Search Console for keyword data

Don't

  • Install GA4 code in both Settings AND template (double counting)
  • Use Universal Analytics (UA) tags—it's been sunset
  • Forget to check Realtime after setup
  • Install tracking on staging blogs without filtering
  • Share your Measurement ID publicly (it's not secret, but still)
  • Ignore data for months—check regularly

Verification Checklist

  • Check GA4 Realtime report shows your visit
  • Navigate to multiple pages and verify pageviews appear
  • Use Google Tag Assistant Chrome extension
  • View source > Search for 'gtag' or 'G-'
  • Wait 24-48 hours and check main GA4 reports

Pro Tips

  • Link GA4 to Search Console: GA4 > Admin > Search Console Links
  • Create a 'Blog Traffic Dashboard' in GA4 for key metrics
  • Set up email reports for weekly traffic summaries
  • Use Explorations for custom reports on blog performance
  • Track outbound link clicks with Enhanced Measurement (default on)
  • Compare blog performance month-over-month in Reports Snapshot

Common Issues & Fixes

Problem: No data showing in GA4 Realtime
Solution: 1) Check that Measurement ID is correct (G- not UA-). 2) Wait 5 minutes. 3) Disable ad blockers. 4) Try incognito mode. 5) If using template method, verify code is before </head>.
Prevention: Always verify in Realtime immediately after setup.
Problem: Data appears doubled (twice as many pageviews)
Solution: You have GA4 installed in both Blogger Settings AND in the template. Remove one. Check Settings > Google Analytics Property ID and Theme > Edit HTML.
Prevention: Use only ONE installation method.
Problem: Using wrong ID format
Solution: GA4 uses 'G-XXXXXXXXXX' format. Universal Analytics used 'UA-XXXXX-X'. Make sure you have a GA4 property, not UA.
Prevention: Check the ID format before pasting. G- = GA4, UA- = old/deprecated.
Problem: Blogger Stats show different numbers than GA4
Solution: Blogger Stats and GA4 count differently. Blogger counts all hits including bots. GA4 filters more. Trust GA4 for accurate human traffic data.
Prevention: Use GA4 as your source of truth for analytics.
Problem: GA4 not tracking after ad blocker installed
Solution: Some ad blockers block GA4. This is expected. Your real users with ad blockers also won't be tracked—this is a known limitation of client-side analytics.
Prevention: Consider server-side tracking for more complete data (advanced).