Google Analytics 4 Questions Answered: The Ultimate FAQ for Setup, Migration & Troubleshooting

GETTING STARTED WITH GA4

What is Google Analytics 4 (GA4)?

Google Analytics 4 (GA4) is Google’s latest web analytics platform that tracks and analyzes user behavior across websites and mobile apps. Unlike its predecessor Universal Analytics, GA4 uses an event-based data model rather than session-based tracking. This means every user interaction—whether it’s a page view, button click, video play, or purchase—is recorded as a distinct event.

GA4 was designed for the modern digital landscape where users interact with brands across multiple devices and platforms. It provides cross-device tracking, enhanced privacy features for GDPR compliance, AI-powered predictive insights, and a more flexible approach to measuring conversions. The platform is free for most users and integrates seamlessly with other Google products like Google Ads, Search Console, and BigQuery.

Is Google Analytics 4 free?

Yes, Google Analytics 4 is completely free for most websites and apps. The standard GA4 property has no cost and includes all core features: unlimited data streams, event tracking, conversion tracking, audience building, standard reports, and the Explore analysis hub. There are some limitations on the free version—you can collect up to 10 million events per month and data is retained for 2-14 months depending on your settings.

For enterprise-level needs, Google offers Analytics 360 (the paid version) which provides higher data limits, longer data retention (up to 50 months), advanced features like roll-up properties, BigQuery export with streaming, service level agreements, and dedicated support. However, the vast majority of websites will never need Analytics 360—the free GA4 version is robust enough for most businesses.

Do I need a Google account to use GA4?

Yes, you need a Google account to access and use Google Analytics 4. The same account you use for Gmail, YouTube, or other Google services works for GA4. If you don’t have a Google account, you can create one for free at accounts.google.com.

Once you have a Google account, you can create a GA4 property and add other users to access it. You can grant different permission levels to team members: Administrator (full access), Editor (can make changes but not manage users), Analyst (can create and share custom reports), or Viewer (read-only access). This means multiple people in your organization can access your GA4 data without sharing login credentials.

What’s the difference between Google Analytics 4 and Universal Analytics?

The differences between GA4 and Universal Analytics are fundamental, not superficial:

Data Model: Universal Analytics used session-based tracking, grouping all interactions during a visit into sessions. GA4 uses event-based tracking where every interaction is an individual event. This provides more granular data and better flexibility.

Cross-Platform Tracking: UA required separate properties for websites and mobile apps. GA4 combines web and app data in a single property with multiple data streams, giving you a unified view of user behavior across platforms.

User Tracking: UA relied heavily on cookies and tracked users primarily on single devices. GA4 uses User ID, Google Signals, and device ID to track users across devices and sessions, creating a more complete picture of the customer journey.

Privacy & Compliance: UA was built before GDPR and other modern privacy regulations. GA4 includes built-in privacy controls like Consent Mode, doesn’t log IP addresses by default, and is designed for a cookieless future.

Machine Learning: GA4 incorporates AI and machine learning throughout the platform, offering predictive metrics (purchase probability, churn probability), automated insights, and data modeling when information is incomplete.

Conversion Tracking: UA limited you to 20 goals per view. GA4 lets you mark any event as a conversion with unlimited conversions possible.

Reporting Interface: UA had 115+ standard reports. GA4 has fewer pre-built reports but offers much more powerful customization through the Explore section.

Why did Google create GA4?

Google created GA4 to address fundamental shifts in how people use the internet and how governments regulate data privacy. Several factors drove this complete rebuild:

Multi-device behavior: People constantly switch between phones, tablets, and computers. UA couldn’t effectively track this behavior. GA4 was built from the ground up for cross-device tracking.

Privacy regulations: GDPR, CCPA, and similar laws require different approaches to data collection. GA4 includes privacy-first features like Consent Mode and cookieless measurement.

Cookie deprecation: Third-party cookies are being phased out by browsers. UA relied heavily on cookies. GA4 uses multiple identification methods including first-party data and modeling.

App and web convergence: The line between websites and apps has blurred. GA4 treats both equally in a unified measurement system.

AI capabilities: Modern analytics requires machine learning for predictions and insights. GA4 was designed with AI at its core rather than as an add-on.

Data quality issues: UA’s session-based model created weird situations like the same person counting as multiple users. GA4’s event-based model provides cleaner, more accurate data.

Google also wanted a forward-looking platform that could evolve for the next decade, rather than continuing to patch an aging system.

When did GA4 launch?

Google officially launched Google Analytics 4 in October 2020, initially calling it “Google Analytics App + Web.” The product went through beta testing throughout 2020 before the public release.

However, GA4 became mandatory on July 1, 2023, when Universal Analytics stopped processing new data. Google gave users nearly three years to migrate from UA to GA4. After July 1, 2023, UA properties could still be accessed to view historical data, but no new data was collected.

Many businesses delayed migration until the deadline, which created challenges since GA4 and UA don’t share historical data. Those who switched early had years of GA4 data to reference; late adopters had to start from scratch with no historical trends.

Is GA4 mandatory?

Yes, GA4 is now mandatory if you want to use Google Analytics for ongoing tracking. Universal Analytics stopped collecting new data on July 1, 2023 (July 1, 2024 for Analytics 360 properties). If you want to track website or app traffic using Google’s analytics platform, you must use GA4.

There’s no option to continue using Universal Analytics for new data collection. While you can still access your old UA data for a limited time, the platform is essentially deprecated. Google has made it clear that GA4 is the only path forward for their analytics product.

That said, GA4 isn’t mandatory in the sense that you could use alternative analytics platforms like Matomo, Adobe Analytics, Mixpanel, or others if GA4 doesn’t meet your needs. But if you want to use Google’s analytics solution, GA4 is your only option.

Can I still access my Universal Analytics data?

As of now, you can still access historical Universal Analytics data, but this won’t last forever. Google has confirmed they will delete Universal Analytics data, but the exact deletion timeline varies:

Standard UA properties: Google will delete data 6 months after the July 1, 2023 sunset date. This means data should be accessible until approximately December 31, 2023 or early 2024. However, many users report still having access in 2025, so Google seems to be extending this grace period.

Analytics 360 properties: These enterprise accounts get a longer retention period, with data accessible until July 1, 2024 at minimum.

Your action required: Do not rely on Google keeping your UA data indefinitely. Export any reports, data, or insights you need before they’re deleted. You can export data manually from the UA interface or use the Google Analytics Reporting API to extract data programmatically. Many third-party tools also offer UA data export services.

Once Google deletes UA data, it’s gone permanently. There’s no way to recover it, and it cannot be imported into GA4 due to incompatible data structures.

GA4 SETUP & INSTALLATION

How do I set up Google Analytics 4?

Setting up GA4 involves five main steps:

Step 1: Create an account – Go to analytics.google.com and sign in with your Google account. Click “Start measuring” and enter your account name (usually your business name). Choose your data sharing settings and click Next.

Step 2: Set up a property – Enter your property name (typically your website name), select your reporting time zone and currency, then answer questions about your business size and goals. Accept Google’s terms of service.

Step 3: Create a data stream – Choose between Web, iOS app, or Android app. For websites, enter your URL and stream name. Enable “Enhanced Measurement” to automatically track scrolls, outbound clicks, site searches, video engagement, and file downloads.

Step 4: Install tracking code – Copy the measurement ID (looks like G-XXXXXXXXXX) and install it on your website. You can do this manually by adding code to your site’s header, through your CMS platform (WordPress, Shopify, etc.), or via Google Tag Manager.

Step 5: Verify tracking works – After installation, visit your website, then check GA4’s Real-time report. You should see yourself as an active user. If data appears, your setup is working correctly.

The entire process takes 20-30 minutes for a basic setup. Advanced configuration like custom events and conversions can be added later.

What is a GA4 property?

A GA4 property is a container within your Google Analytics account that represents a single website, app, or combination of both. Think of your Google Analytics account as a filing cabinet, and each property as a folder within that cabinet.

Each property has:

• A unique property ID
• Its own set of data streams (website, iOS app, Android app)
• Independent settings for data retention, user permissions, and tracking configuration
• Separate reports and data

You might create multiple properties for different reasons:

• Separate properties for different websites (example.com and example2.com)
• A testing property and a production property
• Properties for different business divisions or brands
• A property for your staging environment

However, most businesses only need one property. Within that property, you can have multiple data streams if you have both a website and mobile apps. This gives you a unified view of user behavior across all platforms.

What is a data stream in GA4?

A data stream is a source of data within a GA4 property. It represents a specific platform where you collect user interaction data. There are three types of data streams:

Web data stream: Tracks activity on your website. You need one web data stream for each website domain you want to track.

iOS app data stream: Tracks activity in your iOS mobile application.

Android app data stream: Tracks activity in your Android mobile application.

The powerful aspect of GA4’s data stream approach is that multiple streams can exist within a single property. This means your website, iOS app, and Android app can all send data to the same GA4 property, giving you a unified view of how users interact with your brand across all platforms.

Each data stream has:

• A unique measurement ID (web streams start with G-, apps use different formats)
• Its own Enhanced Measurement settings
• Platform-specific configuration options
• Individual data filters if needed

You configure tracking separately for each data stream, but all the data flows into the same property for unified reporting and analysis.

How do I install GA4 on my website?

There are three main methods to install GA4 on your website:

Method 1: Manual Installation Get your tracking code from GA4 (Admin > Data Streams > Your Stream > View tag instructions > Install manually). Copy the JavaScript code snippet. Paste it into the <head> section of every page on your website, as high as possible. This method works but requires editing your website code directly.

Method 2: CMS/Website Builder Integration Most platforms have easier installation methods:

• WordPress: Use plugins like Site Kit by Google, MonsterInsights, or GA Google Analytics. These handle the code installation for you.
• Shopify: Go to Online Store > Preferences, find the Google Analytics section, paste your measurement ID.
• Wix: Go to Settings > Tracking & Analytics, select Google Analytics, enter your measurement ID.
• Squarespace: Go to Settings > Advanced > External API Keys, connect your Google account.
• Webflow: Go to Project Settings > Integrations, paste your tracking code in the Head Code section.

Method 3: Google Tag Manager Install Google Tag Manager on your site once, then manage all tracking through GTM’s interface. In GTM, create a new GA4 Configuration tag, add your measurement ID, set it to trigger on all pages. This method gives you the most flexibility and control without editing website code for every tracking change.

Choose the method that matches your technical comfort level and platform. Tag Manager is best for complex tracking needs; CMS integrations are easiest for beginners.

Do I need Google Tag Manager for GA4?

No, you don’t need Google Tag Manager (GTM) to use GA4. You can install GA4 tracking directly on your website or through your CMS platform without GTM.

However, GTM offers significant advantages:

Easier tracking management: Once GTM is installed, you never need to edit your website code again. All tracking changes happen in the GTM interface.

Better organization: GTM keeps all your tracking tags in one place—GA4, Facebook Pixel, LinkedIn Insight, etc. You can see what’s tracking what at a glance.

Advanced event tracking: Setting up custom events is much simpler in GTM than coding them manually. You can track form submissions, button clicks, scroll depth, and more using GTM’s built-in triggers.

Testing capabilities: GTM’s preview mode lets you test tracking before it goes live, preventing errors that could pollute your data.

No developer dependency: Marketing teams can implement and modify tracking without waiting for developers.

Version control: GTM keeps a history of all changes, and you can roll back to previous versions if needed.

For simple GA4 installations (just page view tracking), you don’t need GTM. But if you plan to track events, conversions, or multiple marketing platforms, GTM makes your life significantly easier. Most analytics professionals recommend using GTM even for basic setups because it provides flexibility as your tracking needs grow.

What is Enhanced Measurement in GA4?

Enhanced Measurement is a GA4 feature that automatically tracks common user interactions without requiring any additional code or configuration. When you enable Enhanced Measurement during data stream setup, GA4 automatically captures:

Page views: Every time a page loads Scrolls: When users scroll to the bottom (90%) of a page Outbound clicks: Clicks on links that go to external domains Site search: Queries users enter in your site’s search function Video engagement: Interactions with embedded YouTube videos (plays, progress, completions) File downloads: Downloads of PDFs, Excel files, Word documents, text files, and other common file types

These events start tracking immediately—no developer work required. You can toggle individual Enhanced Measurement events on or off in Admin > Data Streams > [Your Stream] > Configure tag settings > Show more > Enhanced measurement.

Enhanced Measurement is a significant improvement over Universal Analytics, where tracking these interactions required custom event code. It’s one of the reasons GA4 setup is faster and provides richer data out of the box.

One caveat: Enhanced Measurement uses certain assumptions (like detecting downloads based on file extensions in URLs). For more precise tracking or custom interactions, you’ll still need to set up custom events.

How long does it take for GA4 data to appear?

GA4 processes data at different speeds depending on the report type:

Real-time reports: Data appears within seconds. The Real-time report shows activity from the last 30 minutes and updates almost instantly. This is perfect for verifying that tracking is working or monitoring live campaign performance.

Standard reports: Data typically appears within 24-48 hours. This processing delay is normal and allows GA4 to properly process events, deduplicate data, and apply machine learning models.

Exploration reports: Custom explorations may take 24-48 hours to reflect the most recent data, though they often update faster.

Audience building: After creating a new audience, it can take 24-48 hours before users start populating that audience.

Search Console integration: After linking Search Console to GA4, you need to wait at least 24 hours (sometimes up to 48 hours) before search query data appears in GA4 reports.

If you’re not seeing any data at all after 48 hours, there’s likely a tracking issue. Check that your tracking code is properly installed, verify it’s not blocked by ad blockers, and use Google Tag Assistant to troubleshoot implementation problems.

Don’t panic if fresh data isn’t immediately visible in standard reports—this delay is by design and doesn’t mean anything is broken.

Can I have multiple GA4 properties?

Yes, you can create multiple GA4 properties within a single Google Analytics account. There’s no hard limit on the number of properties you can have, though Google recommends keeping your account structure simple and organized.

Common scenarios where multiple properties make sense:

Multiple websites: Create a separate property for each distinct website (example.com and example2.com)

Development and production: Maintain a testing property for your staging environment and a separate production property for your live site

Different business units: Large companies might create separate properties for different divisions or brands

Geographic regions: International businesses sometimes create properties for different countries or regions

Client management: Agencies managing multiple clients create separate accounts (not just properties) for each client

However, resist the urge to create too many properties. Each property starts with zero historical data, and you’ll need to manage each one separately. Consider whether you really need separate properties or if you can achieve your goals using:

• Multiple data streams within one property
• Filters and segments to separate data in reports
• Custom dimensions to categorize traffic

Creating a new property is permanent—you can’t merge properties later or transfer historical data between them. Plan your property structure carefully before implementing GA4 across your organization.

How do I add users to my GA4 property?

To grant other people access to your GA4 property:

Step 1: Go to Admin (bottom left of GA4 interface)

Step 2: In the Account or Property column (depending on the level of access you want to grant), click “Account Access Management” or “Property Access Management”

Step 3: Click the blue “+” button in the top right, then select “Add users”

Step 4: Enter the user’s email address (must be a Google account email)

Step 5: Select their role:

• Administrator: Full control including user management
• Editor: Can modify configuration but can’t manage users
• Analyst: Can create and share assets but can’t modify configuration
• Viewer: Read-only access to reports

Step 6: Toggle whether to notify the user via email

Step 7: Click “Add” to complete

The user will receive an email invitation (if you enabled notifications) and can immediately access the property by visiting analytics.google.com and selecting the appropriate account.

Best practices:

• Grant the minimum permission level needed for each person’s role
• Use Viewer access for most people who just need to see reports
• Reserve Administrator access for a small group of trusted individuals
• Regularly audit your user list and remove people who no longer need access
• For agencies, consider creating a separate Google account for professional use

You can modify or remove access at any time by returning to Access Management.

GA4 VS UNIVERSAL ANALYTICS

What happened to Universal Analytics?

Universal Analytics officially stopped processing new data on July 1, 2023 (July 1, 2024 for Analytics 360 properties). This means UA properties no longer collect, process, or track new website traffic or user interactions after that date.

Google announced this sunset in March 2022, giving users about 15 months to migrate to GA4. The decision was driven by several factors:

• Changing privacy regulations (GDPR, CCPA)
• The deprecation of third-party cookies
• Need for cross-device tracking
• Demand for more sophisticated measurement

After the sunset date:

• UA properties became read-only
• Historical data remains accessible for a limited time (Google hasn’t specified exactly how long)
• No new data is collected
• UA properties can’t be reactivated
• Reports continue to be available but don’t update

Google has stated they will eventually delete Universal Analytics data, so you should export any reports or data you need for long-term record-keeping. Once deleted, this data is gone permanently and cannot be recovered.

The transition to GA4 represents a complete platform change, not just an update. That’s why migration required setting up new properties rather than upgrading existing ones.

Can I migrate my Universal Analytics data to GA4?

No, you cannot migrate or import historical Universal Analytics data into GA4. This is one of the most frustrating aspects of the GA4 transition, but it’s technically impossible due to fundamental differences in how the platforms structure data.

Why migration isn’t possible:

Different data models: UA uses session-based data; GA4 uses event-based data. These are incompatible structures that can’t be converted.

Different metrics: Many UA metrics (bounce rate, sessions, pageviews as sessions) don’t have exact equivalents in GA4.

Different dimensions: UA and GA4 categorize and organize data differently.

User identification: UA and GA4 track users using different methodologies.

What you CAN do:

Export UA data: Use the UA interface to export reports as PDFs or spreadsheets. Save any critical reports before Google deletes UA data.

Use the UA Reporting API: Extract raw UA data programmatically and store it in your own database or data warehouse.

Run both systems in parallel: If you started early, you could run UA and GA4 simultaneously to build historical GA4 data before the UA sunset.

Keep UA access open: Access your historical UA data until Google deletes it.

Create documentation: Screenshot or document key historical trends and benchmarks from UA so you have reference points.

The lack of data migration means GA4 properties start with zero historical data. This makes year-over-year comparisons impossible initially and requires building new baselines for your metrics.

Will my GA4 numbers match my Universal Analytics numbers?

No, GA4 and Universal Analytics numbers will not match, even when tracking the same website during the same time period. This is expected and not a sign that something is wrong.

Why the numbers differ:

Different data models: UA’s session-based tracking vs. GA4’s event-based tracking fundamentally changes how interactions are counted.

User counting: GA4’s cross-device tracking means some people who appeared as multiple users in UA (one on mobile, one on desktop) count as a single user in GA4. This typically makes user counts lower in GA4.

Session calculation: GA4 and UA calculate sessions differently. GA4 sessions don’t timeout at midnight, and campaign parameters don’t always start new sessions like they did in UA.

Bounce rate vs. engagement rate: UA measured bounces (single-page sessions with no interaction). GA4 measures engagement (sessions lasting 10+ seconds, with conversions, or with 2+ page views). These are almost opposite metrics.

Filtered traffic: GA4 and UA may filter bot traffic differently.

Tracking methodology: Differences in how third-party cookies are handled, how consent is managed, and how data is processed create discrepancies.

Time zone handling: Different time zone processing can shift data across days.

Common discrepancies:

• GA4 typically shows 10-30% fewer users than UA
• Session counts often differ by 5-20%
• Conversion rates can vary significantly if goal setups differ

Focus on trends and patterns rather than absolute numbers. If both platforms show traffic increasing 25% month-over-month, that’s the meaningful insight—not whether you have exactly 10,000 vs 11,000 users.

Should I keep Universal Analytics running alongside GA4?

This question is now moot since Universal Analytics stopped collecting data on July 1, 2023. But for historical context and for anyone reading this who may have had the question earlier:

Before the UA sunset, running both simultaneously was highly recommended. The benefits included:

Historical data accumulation: Starting GA4 early meant building months or years of historical data before fully transitioning.

Learning time: You could learn the GA4 interface while still relying on familiar UA reports.

Validation: Running both let you verify that GA4 tracked important events and conversions correctly.

Backup: If GA4 tracking failed, you still had UA data as a safety net.

Year-over-year comparisons: You needed at least 12 months of GA4 data before you could make annual comparisons.

The downside was minimal—both properties could use the same tracking code, so there was no performance impact. The only challenge was understanding why the numbers differed (which we covered in the previous question).

Now that UA is sunset, this is no longer a decision point. Everyone must use GA4 for ongoing tracking.

How do I find my Universal Analytics goals in GA4?

Universal Analytics goals don’t automatically appear in GA4, but the GA4 Setup Assistant can help map them. Here’s how to find equivalent conversions:

If you used the Setup Assistant during migration:

1. Go to Admin > Events
2. Look for events marked as conversions
3. The assistant attempted to convert your UA goals into GA4 conversion events

If you didn’t use the Setup Assistant: You’ll need to manually recreate your goals as conversion events:

1. Identify your UA goals (write down what each goal tracked)
2. Determine the equivalent GA4 event:
   • URL destination goals → page_view event with specific page_location
   • Event goals → corresponding GA4 event
   • Duration goals → engagement_time_msec parameter
   • Pages/screens per session → no direct equivalent (use engagement rate)
3. Configure the GA4 event if needed (may require custom event creation)
4. Mark the event as a conversion in Admin > Events

Common UA goal to GA4 conversion mappings:

• Form submission goal → form_submit or custom event
• Purchase goal → purchase event (automatically tracked with ecommerce)
• Newsletter signup → sign_up or custom event
• Contact page view → page_view event for that specific page
• Video completion → video_complete event (if Enhanced Measurement is enabled)

Note that GA4’s conversion model is more flexible than UA’s goals. Any event can be a conversion, and you’re not limited to 20 goals per view. This means you might want to track more conversions in GA4 than you did in UA.

Document your UA goals before the data disappears so you have a clear reference for recreating them in GA4.

What is the GA4 equivalent of bounce rate?

GA4 replaced bounce rate with engagement rate, though it recently brought back bounce rate as well. Understanding both metrics is important:

Engagement Rate (GA4’s preferred metric): Percentage of sessions that were “engaged sessions.” An engaged session is one that meets any of these criteria:

• Lasted 10 seconds or longer
• Had a conversion event
• Had 2 or more page views or screen views

Formula: (Engaged sessions / Total sessions) × 100

Bounce Rate (added back to GA4 due to user demand): Percentage of sessions that were NOT engaged sessions.

Formula: (Non-engaged sessions / Total sessions) × 100
Or simply: 100% – Engagement rate

The key difference: UA’s bounce rate measured single-page sessions with no interaction (time on page wasn’t considered). GA4’s bounce rate measures sessions without sufficient engagement.

Why the change matters:

UA bounce scenario: Someone lands on your contact page, spends 3 minutes finding your phone number, then calls you. UA counts this as a bounce (negative signal).

GA4 bounce scenario: The same visit would NOT be a bounce because it exceeded 10 seconds, indicating engagement (positive signal).

GA4’s engagement rate provides more nuance about actual user interest rather than just counting page views. A single-page session where someone spends 2 minutes reading an article is valuable—GA4 recognizes this; UA didn’t.

You can find bounce rate and engagement rate in most GA4 reports. Both metrics appear in the Acquisition, Engagement, and traffic source reports.

GA4 REPORTS & INTERFACE

Where are the reports in GA4?

GA4’s report structure is different from Universal Analytics, which confuses many users initially. Here’s where everything lives:

Left Sidebar Navigation:

• Home: Dashboard overview with key metrics
• Reports: Contains all standard reports (this is where you’ll spend most time)
• Explore: Custom analysis and advanced reporting
• Advertising: Attribution and ad performance (requires Google Ads linkage)
• Admin: Settings and configuration

Inside the Reports section (click Reports in left sidebar):

• Reports Snapshot: Quick overview of key metrics
• Realtime: Current activity (last 30 minutes)
• Life Cycle: Four major report categories
  • Acquisition (how users find you)
  • Engagement (what users do)
  • Monetization (revenue and ecommerce)
  • Retention (repeat visits)
• User: Demographic and technology reports
  • User attributes (demographics, interests)
  • Tech (device, browser, OS)

The Explore section (separate from Reports):

• Free form exploration
• Funnel analysis
• Path exploration
• Segment overlap
• User lifetime value
• Cohort analysis

The structure is more hierarchical than UA. Instead of browsing dozens of reports in a long list, you navigate through categories. This makes the interface cleaner but requires learning where specific reports live.

Pro tip: Use the search bar at the top. Type what you’re looking for (like “landing pages” or “traffic sources”) and GA4 will surface relevant reports.

How do I see page views in GA4?

Page view data appears in several places in GA4:

Method 1: Engagement Reports (easiest)

1. Go to Reports > Engagement > Pages and screens
2. You’ll see a table showing all pages with:
   • Views (page views)
   • Users
   • Average engagement time
   • Event count

Method 2: Realtime Report

1. Go to Reports > Realtime
2. Scroll to “Views by Page title and screen name”
3. See which pages people are viewing right now

Method 3: Events Report

1. Go to Reports > Engagement > Events
2. Find the “page_view” event
3. Click it to see detailed page view data with parameters

Method 4: Explore (for custom analysis)

1. Go to Explore > Blank template
2. Add “Page path and screen class” as a dimension
3. Add “Views” as a metric
4. Customize with filters and segments as needed

Understanding the Views metric: In GA4, “Views” is the equivalent of page views in UA. The metric counts how many times each page was loaded. However, single-page applications (SPAs) that use virtual page views may count views differently than traditional multi-page sites.

If you’re used to UA’s Behavior > Site Content > All Pages report, the GA4 equivalent is Engagement > Pages and screens. The data is similar but with engagement metrics added.

Where is the bounce rate in GA4?

Bounce rate was initially removed from GA4 but was added back due to user demand. Here’s where to find it:

Standard Reports: Most traffic reports now include bounce rate as a metric:

• Reports > Acquisition > Traffic acquisition (shows bounce rate by source/medium)
• Reports > Acquisition > User acquisition (shows bounce rate by channel)
• Reports > Engagement > Pages and screens (shows bounce rate by page)
• Reports > Engagement > Landing page (shows bounce rate by landing page)

Adding Bounce Rate to Reports: If you don’t see bounce rate in a report:

1. Click the pencil icon (Customize report) in the top right
2. Click “Metrics”
3. Add “Bounce rate” from the available metrics
4. Click “Apply”
5. Save the report to keep your changes

Explore Section: When building custom explorations:

1. In the Variables panel, find “Metrics”
2. Search for and add “Bounce rate”
3. Drag it into your analysis table or chart

Important: Remember that GA4’s bounce rate is calculated differently than UA’s bounce rate (see the earlier FAQ about bounce rate equivalents). GA4 bounce rate = percentage of sessions that were NOT engaged (lasted <10 seconds, no conversion, single page view).

If you preferred the old UA bounce rate metric, you’ll need to interpret GA4’s bounce rate through this new definition. Or focus on engagement rate instead, which is often more meaningful.

How do I see real-time data in GA4?

The Real-time report shows what’s happening on your site right now (last 30 minutes):

Access the Real-time Report:

1. Click “Reports” in the left sidebar
2. Click “Realtime” (first item under the Reports snapshot)

What you’ll see:

• Users in last 30 minutes: Count of active users right now
• Users by minute: Bar chart showing users per minute for the last 30 minutes
• Snapshot card: Views, event count, and conversions in the last 30 minutes
• By user source: Where current visitors came from (direct, organic, referral, etc.)
• By device: Desktop, mobile, or tablet
• By location: Map showing where users are located
• By audience: Which audience segments users belong to (if you’ve set up audiences)
• Views by page title: Which pages people are currently viewing
• Events by name: Which events are being triggered right now
• Conversions by name: Real-time conversion tracking

Use cases for Real-time reports:

• Verifying new tracking is working after installation
• Monitoring live campaign launches
• Watching event/sale traffic as it happens
• Testing event tracking before it goes live
• Checking if a specific page is causing issues
• Seeing immediate impact of social media posts or email campaigns

Limitations:

• Data only goes back 30 minutes (not useful for historical analysis)
• Some data may be sampled during high-traffic periods
• User identification may be less accurate than in standard reports

The Real-time report is perfect for immediate feedback but should never be used for business decisions or performance analysis—use standard reports for that.

What are Life Cycle reports in GA4?

Life Cycle reports are GA4’s main organizational structure for understanding the complete user journey. They’re divided into four categories that represent stages of the customer lifecycle:

1. Acquisition Answers: “How do people find my site?”

• Shows traffic sources, channels, campaigns
• Tracks first-time vs. returning users
• Identifies which channels bring new users vs. drive repeat visits
• Reports: Acquisition overview, User acquisition, Traffic acquisition

2. Engagement Answers: “What do people do on my site?”

• Tracks user interactions and behavior
• Shows which content engages users
• Monitors event activity
• Reports: Engagement overview, Events, Conversions, Pages and screens, Landing page

3. Monetization Answers: “How do I make money from users?”

• Tracks ecommerce transactions
• Shows revenue metrics
• Analyzes purchase behavior
• Reports: Monetization overview, Ecommerce purchases, Publisher ads, In-app purchases

4. Retention Answers: “Do users come back?”

• Measures user loyalty
• Tracks repeat visit patterns
• Predicts lifetime value
• Reports: Retention overview, User engagement, Lifetime value

This structure maps to the customer journey:

1. Users discover you (Acquisition)
2. They interact with your content (Engagement)
3. Some make purchases or generate revenue (Monetization)
4. Quality users return (Retention)

Understanding this framework helps you navigate GA4 more intuitively. Instead of browsing a long list of disconnected reports like in UA, you think about which stage of the user journey you want to analyze, then go to the corresponding Life Cycle section.

Each section contains an Overview report (quick summary) plus detailed reports that dig deeper into specific aspects.

Where are the demographics reports in GA4?

Demographics reports in GA4 are under the User section, but they require additional configuration to populate data:

Accessing Demographics Reports:

1. Click “Reports” in the left sidebar
2. Click “User” (below Life Cycle)
3. Click “User attributes”
4. Select “Overview” to see a summary or “Demographic details” for deeper analysis

What you’ll see (once configured):

• Age ranges (18-24, 25-34, 35-44, 45-54, 55-64, 65+)
• Gender (male, female)
• Interests categories
• Language
• Country
• City

Important: Demographics data won’t appear automatically. You must:

Step 1: Enable Google Signals

1. Go to Admin > Data Settings > Data Collection
2. Turn on “Google signals data collection”
3. Accept the terms

Step 2: Wait for data Demographics data only includes users who:

• Are signed into their Google account
• Have ad personalization enabled
• Meet certain thresholds (Google doesn’t show demographics if sample size is too small for privacy)

Step 3: Be patient It can take 24-48 hours for demographics data to start appearing after enabling Google Signals.

Limitations:

• Only a subset of your traffic will have demographics data (typically 40-70% depending on your audience)
• Google withholds demographics data if the sample size is below privacy thresholds
• Demographics are inferred from Google account data, not directly reported by users
• Some regions or audience segments may not have sufficient data

Demographics reports are useful for understanding your audience profile but shouldn’t be used for precise segmentation since not all users will have this data.

How do I see mobile vs desktop traffic in GA4?

Device category data (mobile, desktop, tablet) appears throughout GA4. Here are the main locations:

Method 1: User Reports (easiest)

1. Go to Reports > User > Tech > Overview
2. You’ll see a breakdown by device category with users, sessions, and engagement metrics

Method 2: Tech Details Report

1. Go to Reports > User > Tech > Tech details
2. At the top of the page, select “Device category” from the dropdown
3. View detailed metrics for desktop, mobile, and tablet

Method 3: Real-time Report

1. Go to Reports > Realtime
2. Look at the “Users by device” card showing current device split

Method 4: Add Device Category to Any Report Most reports let you add device category as a dimension:

1. In any report, look for the dropdown that says “All users” or shows the current dimension
2. Click it and search for “Device category”
3. Select it to break down that report by device type

Method 5: Custom Exploration

1. Go to Explore
2. Create a free form report
3. Add “Device category” as a dimension
4. Add any metrics you want to analyze
5. Filter and segment as needed

What you’ll learn:

• Which devices your audience prefers
• Performance differences across devices (mobile may have lower conversion rates)
• Engagement differences (mobile users may have shorter sessions)
• Technical issues (high bounce rate on mobile might indicate design problems)

You can also see more detailed device data like:

• Operating system (iOS, Android, Windows)
• Browser (Chrome, Safari, Firefox)
• Screen resolution
• Device model (iPhone 12, Samsung Galaxy S21)

Device analysis is crucial for optimization since mobile and desktop users often behave differently and require different experiences.

GA4 EVENTS & CONVERSIONS

What are events in GA4?

Events are the foundation of GA4’s data model. Every user interaction with your website or app is recorded as an event. Unlike Universal Analytics which centered on sessions and pageviews, GA4 treats everything as events.

Event components:

• Event name: What happened (e.g., page_view, click, purchase, sign_up)
• Event parameters: Additional details about the event (up to 25 per event)
• Timestamp: When the event occurred
• User properties: Information about the user who triggered the event

Types of events in GA4:

1. Automatically collected events: GA4 tracks these by default without any configuration

• first_visit (user’s first time on your site)
• session_start (beginning of a session)
• user_engagement (periodic check-in during active sessions)

2. Enhanced Measurement events: Automatically tracked if Enhanced Measurement is enabled

• page_view
• scroll (90% of page depth)
• click (outbound links)
• view_search_results (site searches)
• video_start, video_progress, video_complete
• file_download

3. Recommended events: Standard event names Google recommends for common actions

• login, sign_up, share
• search, view_item, add_to_cart, purchase
• generate_lead, subscribe

4. Custom events: Events you create for unique interactions specific to your business

• calculator_used
• tool_opened
• demo_requested
• pricing_page_viewed

Events can have parameters providing context:

• page_view event includes page_location, page_title, page_referrer parameters
• purchase event includes transaction_id, value, currency, items parameters
• Custom events can have custom parameters

Understanding events is fundamental to using GA4 effectively. Every report, conversion, and analysis is built on events.

How do I track custom events in GA4?

There are three main methods to track custom events, listed from easiest to most complex:

Method 1: Create Event in GA4 Interface (no code required) Best for simple events based on existing events.

1. Go to Admin > Events
2. Click “Create event”
3. Set up conditions (e.g., “when page_view occurs and page_location contains /thank-you”)
4. Name your event
5. Click Create

This method creates a new event whenever specific conditions are met on an existing event.

Method 2: Use Google Tag Manager Best for most custom event tracking.

1. In GTM, go to Tags > New
2. Choose “Google Analytics: GA4 Event” as tag type
3. Select your GA4 Configuration tag
4. Enter your event name
5. Add event parameters if needed
6. Set up a trigger (what causes the event to fire)
7. Save and publish

Example: Track button clicks

• Trigger: Click – All Elements, with Click Text equals “Download Now”
• Event name: button_click
• Parameters: button_text = {{Click Text}}

Method 3: Add Code to Your Website Best for complex tracking or when you don’t use GTM.

Add this JavaScript where you want the event to fire:

Copygtag(‘event’, ‘event_name’, {

parameter1: ‘value1’,

parameter2: ‘value2’

});

Example: Track newsletter signup

Copygtag(‘event’, ‘newsletter_signup’, {

method: ‘footer_form’

});

Best practices for custom events:

• Use lowercase with underscores (button_click not ButtonClick)
• Keep event names under 40 characters
• Use recommended event names when applicable
• Add meaningful parameters for context
• Test events in DebugView before going live
• Document your events so others understand what they track

Common custom events to track:

• Form submissions (not automatically tracked)
• Button clicks (specific buttons, not all clicks)
• Modal opens/closes
• Filter usage
• Calculator interactions
• Accordion expansions
• Tab switches
• Chat opens

Custom events unlock GA4’s full potential, letting you track business-specific interactions that matter to your goals.

What’s the difference between events and conversions in GA4?

This confuses many people: Events and conversions are not different things. A conversion IS an event—specifically, an event you’ve marked as important to your business goals.

Events: Any user interaction tracked in GA4. You might have hundreds of different events (page_view, scroll, click, add_to_cart, etc.)

Conversions: A subset of events that you’ve designated as valuable business outcomes.

The relationship:

1. All conversions are events
2. Not all events are conversions
3. You decide which events become conversions

How to mark an event as a conversion:

1. Go to Admin > Events
2. Find the event you want to track as a conversion
3. Toggle the “Mark as conversion” switch
4. That event now counts as a conversion in all reports

Example:

• Event: “form_submit” (tracks all form submissions)
• Conversion: Mark “form_submit” as a conversion
• Result: Every form submission now counts as a conversion in reports

Why the distinction matters:

Events tell you WHAT people do. Conversions tell you when they do something VALUABLE.

You might track 50 different events, but only 5 might be conversions (purchase, sign_up, contact_form, demo_request, newsletter_subscribe). This focuses your reporting on business outcomes rather than all activity.

Conversion reporting: Once marked, conversions appear in:

• Reports > Engagement > Conversions
• Conversion metrics in acquisition reports
• Google Ads (if linked)
• Attribution reports

Unlimited conversions: Unlike UA which limited you to 20 goals, GA4 allows unlimited conversion events. However, Google Ads only imports the first 30 conversions if you have more than that.

Best practice: Be selective about conversions. Mark events that truly represent business value. If everything is a conversion, nothing is a conversion.

How do I set up conversion tracking in GA4?

Setting up conversion tracking is straightforward once you understand that conversions are just events marked as important:

Step 1: Identify what you want to track as conversions Common conversions:

• Purchases (ecommerce)
• Lead form submissions
• Account signups
• Newsletter subscriptions
• Phone calls
• Demo requests
• File downloads (if that’s your goal)
• Specific page views (thank you pages)

Step 2: Ensure the event is being tracked

• Check if the event already exists (go to Reports > Engagement > Events)
• If it doesn’t exist, you need to create or configure it first
• Use Enhanced Measurement for basic events (page_view, file_download)
• Set up custom events for specific interactions

Step 3: Mark the event as a conversion

1. Go to Admin > Events
2. Find your event in the list
3. Toggle “Mark as conversion” to ON
4. The event is now a conversion

Step 4: Verify it’s working

1. Trigger the conversion action on your site (submit a form, make a purchase, etc.)
2. Go to Reports > Engagement > Conversions
3. Within 24 hours, you should see the conversion appear with a count

For specific conversion types:

Purchase conversions (ecommerce): The “purchase” event is automatically marked as a conversion if you have ecommerce tracking set up. No additional configuration needed.

Form submission conversions:

1. Set up form tracking (via GTM or event creation)
2. Create event: “form_submit”
3. Mark “form_submit” as conversion

Thank you page conversions:

1. The “page_view” event already exists
2. Go to Admin > Events > Create event
3. Create event: “conversion_page_view”
4. Condition: page_location contains “/thank-you”
5. Mark “conversion_page_view” as conversion

Outbound link conversions:

1. Enhanced Measurement automatically tracks clicks
2. Go to Admin > Events > Create event
3. Create event based on click event with specific link parameters
4. Mark as conversion

Best practices:

• Test conversions before considering them live
• Use DebugView to verify events fire correctly
• Name conversions clearly (not just “conversion1”)
• Document what each conversion represents
• Review conversions monthly and remove ones no longer relevant

Conversion tracking is essential for measuring marketing effectiveness, calculating ROI, and optimizing your website for business goals.

What are key events in GA4?

“Key events” is Google’s new terminology for what were called “conversions” in GA4. In early 2024, Google renamed “conversions” to “key events” across the GA4 interface, though the functionality remains identical.

Why the name change? Google wanted to reduce confusion between:

• GA4 “conversions” (any important event)
• Google Ads “conversions” (specifically revenue-generating actions)

By calling them “key events” in GA4, it’s clearer that these are important events you want to track, whether or not they generate immediate revenue.

What are key events? Key events are significant user interactions that align with your business objectives. They’re regular events that you’ve marked as important.

Examples:

• Purchase (obviously key)
• Newsletter signup (key for content sites)
• Free trial start (key for SaaS)
• Contact form submission (key for service businesses)
• Whitepaper download (key for B2B)
• Account creation (key for apps)

How to mark an event as a key event:

1. Go to Admin > Events
2. Toggle “Mark as key event” for important events (The toggle says “Mark as key event” in newer GA4 versions; older versions say “Mark as conversion”)

Where key events appear:

• Reports > Engagement > Key events (or Conversions in older interface versions)
• Acquisition reports show key event counts and rates
• Attribution reports analyze key event paths

Technical note: The underlying functionality didn’t change—only the label. If you marked events as conversions before the terminology change, they’re now called key events automatically. Your historical data remains intact.

Best practice: Whether you call them conversions or key events, the strategy is the same—mark 3-10 truly important events that represent real business value. Don’t mark every event as a key event, or you’ll dilute the usefulness of this designation.

For the purposes of setup and optimization, “key events” and “conversions” are synonymous. Use whichever term appears in your GA4 interface version.

GA4 FOR ECOMMERCE

How do I set up ecommerce tracking in GA4?

Ecommerce tracking in GA4 requires implementing specialized events that capture transaction details. Here’s the complete setup:

Step 1: Choose your implementation method

Option A: Direct website integration (requires developer) Add ecommerce tracking code to your website

Option B: Through your ecommerce platform

• Shopify: Use built-in GA4 integration or apps like Analyzify
• WooCommerce: Use plugins like GA4 for WooCommerce
• BigCommerce: Native GA4 integration in settings
• Magento: Use extensions or custom implementation

Option C: Via Google Tag Manager Set up data layers and GA4 ecommerce tags in GTM

Step 2: Implement required ecommerce events

GA4 recognizes specific ecommerce events:

• view_item: User views a product
• add_to_cart: User adds product to cart
• begin_checkout: User starts checkout
• purchase: Transaction completes (most critical)
• view_cart: User views shopping cart
• remove_from_cart: User removes item
• add_payment_info: User enters payment details
• add_shipping_info: User enters shipping details
• view_promotion: User sees promotion
• select_promotion: User clicks promotion

Step 3: Include required parameters

Each ecommerce event needs specific parameters:

For purchase event (minimum required):

Copygtag(“event”, “purchase”, {

transaction_id: “T_12345”,

value: 25.42,

currency: “USD”,

items: [

{

item_id: “SKU_12345”,

item_name: “Product Name”,

price: 25.42,

quantity: 1

}

]

});

For view_item event:

Copygtag(“event”, “view_item”, {

items: [

{

item_id: “SKU_12345”,

item_name: “Product Name”,

price: 25.42

}

]

});

Step 4: Test your implementation

1. Make a test purchase on your site
2. Go to Admin > DebugView in GA4
3. Verify ecommerce events fire with correct parameters
4. Check Reports > Monetization > Ecommerce purchases within 24 hours

Step 5: Mark purchase as key event/conversion

1. Go to Admin > Events
2. Find “purchase” event
3. Toggle “Mark as key event” (should be automatic but verify)

Common implementation mistakes:

• Missing transaction_id (causes duplicate transactions)
• Wrong currency code (use ISO 4217 codes: USD, EUR, GBP)
• Value not matching total price
• Items array missing required fields
• Tracking test purchases without filtering them out

Ecommerce reporting requires:

• All ecommerce events firing correctly
• Consistent item IDs across events
• Complete transaction data
• 24-48 hours for data to fully populate reports

Once properly configured, you’ll see:

• Revenue metrics across all reports
• Product performance data
• Shopping behavior analysis
• Purchase funnels
• Item promotion effectiveness

Ecommerce tracking is complex. Consider hiring a GA4 specialist if you’re not comfortable with technical implementation.

What ecommerce data can GA4 track?

GA4 provides comprehensive ecommerce tracking covering the entire shopping journey:

Transaction-level data:

• Total revenue
• Number of transactions
• Average order value
• Transaction ID (unique identifier)
• Tax amount
• Shipping cost
• Currency
• Payment method (if configured)

Product-level data:

• Product name
• Product ID/SKU
• Product category
• Product brand
• Product variant (size, color, etc.)
• Product quantity
• Product price
• Product position in list
• Product list name (where it was clicked)

Shopping behavior data:

• Product views
• Add-to-cart actions
• Cart removals
• Checkout initiations
• Checkout completions
• Purchase completions
• Refunds

Promotional data:

• Promotion views
• Promotion clicks
• Promotion name
• Promotion creative
• Promotion position
• Discount amount

User-level ecommerce data:

• Customer lifetime value
• Purchase frequency
• Time between purchases
• Average revenue per user
• New vs. returning customers
• Items per purchase

Item-specific metrics:

• Item revenue
• Item views
• Item add-to-cart rate
• Item purchase rate
• Item refund rate
• Items purchased together

Funnel analysis:

• Step-by-step shopping funnel
• Drop-off rates at each stage
• Time spent in each stage
• Completion rates

All this data can be segmented by:

• Traffic source/medium
• Campaign
• Device type
• Geographic location
• User demographics
• Time period
• Custom dimensions

Where to find ecommerce data in GA4:

• Reports > Monetization > Overview
• Reports > Monetization > Ecommerce purchases
• Reports > Monetization > Purchase journey
• Reports > Monetization > Checkout journey
• Reports > Monetization > Item promotion
• Explore > Funnel exploration (custom purchase funnels)
• Explore > Path exploration (shopping paths)

Advanced capabilities:

• Integration with Google Ads for ROAS tracking
• BigQuery export for custom analysis
• Product list performance comparison
• Cohort analysis for repeat purchases
• Predictive metrics for purchase probability

The depth of ecommerce data in GA4 far exceeds what was available in Universal Analytics, especially around product-level details and user journey analysis.

How do I connect Google Search Console to GA4?

Linking Google Search Console to GA4 unlocks powerful SEO insights by combining search performance data with user behavior analytics:

Step-by-step connection process:

Step 1: Verify prerequisites

• You need Editor or Administrator access to the GA4 property
• You need Owner, Full User, or Restricted User access in Google Search Console
• Both must use the same Google account (or you need access to both)

Step 2: Navigate to Product Links

1. Open GA4 and click Admin (bottom left)
2. In the Property column, click “Product Links”
3. Click “Search Console Links”

Step 3: Link the properties

1. Click “Link” button
2. Click “Choose accounts”
3. Select your Search Console property from the list
4. Click “Confirm”
5. Click “Next”

Step 4: Select web stream

1. Click “Select” to choose which GA4 data stream to link
2. Select your website data stream
3. Click “Next”

Step 5: Review and submit

1. Verify the Search Console property and data stream are correct
2. Click “Submit”
3. You’ll see a confirmation that the link was created

Step 6: Wait for data

• Allow 24-48 hours for data to start appearing
• Search Console data only goes back to when you created the link (no historical integration)

Verification: After 24-48 hours, check Reports > Acquisition > Search Console to confirm data is flowing.

Common connection issues:

• No Search Console property available: Make sure you’ve verified your website in Search Console first
• Permission errors: Verify you have sufficient access in both platforms
• Domain mismatch: The GA4 data stream URL must match the Search Console property URL
• Multiple properties: If you have multiple Search Console properties (http vs https, www vs non-www), choose the one that matches your primary website version

What happens after linking:

• Search query data appears in GA4 reports
• You see which keywords drive traffic
• User behavior metrics connect to organic search terms
• Landing page performance includes search data

Important notes:

• You can link multiple Search Console properties to one GA4 property if needed
• The link doesn’t affect Search Console data or functionality
• Unlinking doesn’t delete historical data that was already shared
• Data sharing is one-way (Search Console → GA4), not bidirectional

This integration is essential for SEO professionals using GA4 to understand organic search performance comprehensively.

What SEO data can I see in GA4 after linking Search Console?

Once you’ve linked Search Console to GA4, you gain access to rich organic search data:

Available in Reports > Acquisition > Search Console:

1. Queries Report(search terms)

• Exact search queries people used to find your site
• Impressions (how many times your site appeared in search results)
• Clicks (how many times people clicked your listing)
• Average position (your ranking for each query)
• Click-through rate (CTR)

2. Google Organic Search Traffic ReportShows the volume and trends of your organic search traffic over time
3. Google Organic Search Queries Report
   Detailed breakdown of individual search terms with performance metrics

Metrics available for organic search:

• Search impressions: Times your site appeared in Google search results
• Search clicks: Times users clicked your listing
• Average search position: Your typical ranking position
• CTR: Percentage of impressions that resulted in clicks
• Engaged sessions from organic search: Quality of traffic
• Conversions from organic search: Business outcomes
• Engagement rate: How well organic traffic engages with your site
• Session duration: Time spent by organic visitors

You can analyze:

Query performance:

• Which keywords drive the most traffic
• Which keywords have high impressions but low clicks (CTR opportunity)
• Which keywords rank well but don’t drive conversions
• Trending queries over time

Landing page analysis:

• Which pages receive the most organic traffic
• Engagement rates by landing page from organic search
• Conversion rates by landing page
• Pages with high bounce rates from search

Organic traffic behavior:

• What organic visitors do after arriving
• Which pages they visit next
• How long they stay
• Whether they convert

Comparison capabilities:

• Compare organic performance across date ranges
• Compare performance by device (mobile vs desktop organic)
• Compare different queries or landing pages
• Benchmark organic against other channels

What you WON’T see (limitations):

• Individual user search queries (Google anonymizes some for privacy)
• Complete search query data (some queries are grouped as “not provided”)
• Search Console data from before the link was created
• Image search, video search, or other specialized search types (only web search)

How to use this data for SEO:

Identify content gaps: Queries with high impressions but low clicks might need better titles/descriptions

Optimize for conversions: Keywords driving traffic but not conversions might need landing page improvements

Find keyword opportunities: High-ranking queries with low engagement suggest content improvements

Track SEO progress: Monitor position changes and traffic trends for target keywords

Understand user intent: See what people actually searched for before arriving at each page

Device optimization: Compare mobile vs desktop organic performance to identify issues

The Search Console integration transforms GA4 from a general analytics tool into a powerful SEO analysis platform, combining search visibility data with on-site behavior metrics.

How do I track organic search traffic in GA4?

Organic search traffic tracking happens automatically in GA4, but understanding where to find and analyze it is key:

Automatic tracking: GA4 automatically identifies and categorizes organic search traffic through:

• Referrer URLs (when users come from google.com, bing.com, etc.)
• Default channel groupings (assigns traffic to “Organic Search” channel)
• Source/Medium attribution (assigns source as google, bing, duckduckgo, etc. with medium as “organic”)

Where to find organic search data:

Method 1: Acquisition Overview

1. Go to Reports > Acquisition > Overview
2. Look at the “Sessions by Channel” chart
3. Find “Organic Search” channel
4. Click it to drill deeper

Method 2: Traffic Acquisition Report

1. Go to Reports > Acquisition > Traffic acquisition
2. The report shows all traffic sources
3. Look for rows where Session source/medium includes “organic”
4. Examples: google / organic, bing / organic

Method 3: User Acquisition Report

1. Go to Reports > Acquisition > User acquisition
2. Shows first-time visitor sources
3. Find organic search channels
4. Compare new vs. returning organic traffic

Method 4: Create Custom Exploration

1. Go to Explore > Free Form
2. Add dimension: “Session source/medium”
3. Add filter: “Session medium = organic”
4. Add metrics: Users, Sessions, Engagement rate, Conversions
5. Analyze organic search performance in detail

Method 5: Search Console Reports (after linking)

1. Go to Reports > Acquisition > Search Console
2. See organic search with keyword-level detail
3. View queries, positions, and CTRs

Organic search metrics to track:

• Users from organic search: Unique visitors from search engines
• Sessions from organic search: Total visits from search
• Engagement rate: Quality of organic traffic
• Conversions: Business outcomes from organic visitors
• Average engagement time: How long organic visitors stay
• Events per session: Activity level of organic traffic
• Bounce rate: Percentage of non-engaged organic sessions

Organic search dimensions to analyze:

• Source: Which search engine (google, bing, yahoo, duckduckgo)
• Landing page: Where organic visitors first arrive
• Device category: Mobile, desktop, or tablet organic traffic
• Geographic location: Where organic visitors are located
• Campaign (if using UTM parameters for organic tracking)

Segmenting organic traffic:

Create segments to analyze organic traffic separately:

1. Go to Explore
2. Create segment with condition: “Session medium = organic”
3. Apply segment to any exploration
4. Compare organic vs. other channels

Common organic tracking issues:

Problem: Organic traffic showing as direct

• Cause: Missing or broken tracking code
• Solution: Verify GA4 tag fires on all pages

Problem: Organic traffic not categorized correctly

• Cause: Custom channel grouping overriding defaults
• Solution: Check Admin > Data Settings > Channel Groups

Problem: Organic traffic seems too low

• Cause: Many reasons (site speed, crawl issues, ranking problems)
• Solution: Cross-reference with Search Console data

Advanced organic tracking:

Track organic by search engine separately:

• Create custom channel groups separating Google, Bing, Yahoo
• Compare performance across search engines

Track branded vs. non-branded organic (requires Search Console):

• Analyze queries containing your brand name separately
• Compare engagement and conversion rates

Track organic landing page performance:

• See which pages receive organic traffic
• Identify high-performing vs. underperforming pages
• Optimize based on data

Monitor organic trends over time:

• Create date comparisons (month-over-month, year-over-year)
• Identify seasonality patterns
• Track impact of SEO changes

Organic search tracking is foundational for measuring SEO effectiveness and should be monitored regularly alongside Search Console metrics for complete search performance visibility.

Can GA4 help with keyword research?

Yes, but with important limitations. GA4 can supplement keyword research through Search Console integration, though it’s not a keyword research tool in the traditional sense:

What GA4 CAN show you (via Search Console integration):

1. Keywords currently driving traffic

• See actual search queries bringing visitors to your site
• Understand what you already rank for
• Identify unexpected ranking wins

2. Keyword performance metrics

• Which keywords drive the most traffic
• Which have high impressions but low clicks (opportunity for better titles/descriptions)
• Which keywords convert vs. just drive traffic
• Engagement levels by keyword

3. Keyword trends

• Rising and declining search terms
• Seasonal keyword patterns
• Changes in search volume over time

4. Long-tail keyword discovery

• See actual long-tail phrases people use
• Identify content gap opportunities
• Find question-based queries

5. Keyword-to-conversion mapping

• Which keywords lead to conversions
• ROI of different keyword categories
• User journey patterns from different keywords

How to use GA4 for keyword insights?

Find high-opportunity keywords:

1. Go to Reports > Acquisition > Search Console > Queries
2. Sort by impressions (descending)
3. Find keywords with high impressions but low clicks
4. These need better title tags and meta descriptions

Identify converting keywords:

1. Same report, add secondary dimension or filter for conversions
2. See which keywords drive actual business results
3. Create more content targeting similar terms

Discover content gaps:

1. Look for keywords where you rank 11-20 (page 2)
2. These are improvement opportunities—you’re close to page 1
3. Optimize existing content or create better content

Understand user intent:

1. Analyze engagement rate by keyword
2. High engagement = good intent match
3. Low engagement = mismatch between search intent and content

What GA4 CANNOT do for keyword research:

No search volume data: GA4 shows impressions (how often YOUR site appeared) but not total search volume for keywords

No keyword suggestions: Won’t suggest new keywords to target

No competition analysis: Can’t show keyword difficulty or competitor rankings

No “not provided” access: Many keywords still hidden due to privacy (especially branded searches from logged-in users)

Limited to your current rankings: Only shows keywords where you already appear in search results

Better keyword research tools: For comprehensive keyword research, use dedicated tools alongside GA4:

• Google Keyword Planner: Search volume, competition, bid estimates
• Semrush: Keyword research, competitor analysis, keyword difficulty
• Ahrefs: Keyword explorer, SERP analysis, keyword difficulty
• Moz Keyword Explorer: Keyword suggestions, difficulty scores
• Google Trends: Trend data and related queries
• Answer the Public: Question-based keyword ideas

Optimal workflow:

1. Use dedicated keyword tools to identify target keywords
2. Create content targeting those keywords
3. Use GA4 + Search Console to monitor performance
4. Identify which keywords actually drive traffic and conversions
5. Discover unexpected ranking keywords through GA4
6. Double down on what works based on GA4 data

GA4’s value for SEO: While GA4 isn’t a keyword research tool, it’s invaluable for:

• Understanding performance of keywords you’re already targeting
• Measuring SEO ROI through conversion tracking
• Identifying which content types and topics resonate with searchers
• Discovering unexpected opportunities from current rankings
• Connecting keyword performance to business outcomes

Think of GA4 as your keyword performance analyzer rather than your keyword discovery tool. Use it to optimize based on real data rather than to find new keywords to target.

GA4 PRIVACY, GDPR & COMPLIANCE

Is GA4 GDPR compliant?

GA4 is not automatically GDPR compliant—compliance depends on how you implement and configure it. GA4 includes privacy-enhancing features, but you’re responsible for using them properly:

Built-in privacy features GA4 offers:

1. IP anonymization(automatic)

• GA4 doesn’t log or store IP addresses by default
• Big improvement over UA which required manual IP anonymization

2. Consent Mode

• Adjusts tracking based on user consent choices
• Works with cookie consent banners
• Uses data modeling when users decline cookies

3. Data retention controls

• Set how long user-level data is retained (2 or 14 months)
• Aggregate data retained longer but without user identifiers

4. Data deletion

• Tools to delete user data upon request
• Required for GDPR “right to be forgotten”

5. Google Signals opt-in

• Cross-device tracking requires explicit enabling
• Not active by default

6. No personally identifiable information (PII)

• Terms of Service prohibit collecting PII
• Built-in filters can remove PII accidentally collected

What YOU must do for GDPR compliance?

1. Get valid consent

• Implement cookie consent banner
• Get explicit consent before GA4 tracking starts
• Don’t use pre-ticked boxes (not valid consent)
• Make consent optional (not required to access site)

2. Update privacy policy

• Disclose GA4 usage clearly
• Explain what data is collected
• Explain how data is used
• Provide links to Google’s privacy policies
• Explain users’ rights (access, deletion, etc.)

3. Configure data retention

• Go to Admin > Data Settings > Data Retention
• Choose appropriate retention period
• Shorter is better for privacy (2 months if possible)

4. Enable Consent Mode

• Integrate GA4 with your consent management platform
• Configure proper behavior for consented vs. non-consented users

5. Sign data processing agreement with Google

• Available at Admin > Account > Account Settings
• Legally required for GDPR compliance

6. Honor user rights

• Respond to data access requests
• Delete user data when requested
• Provide data exports if requested

7. Limit data collection

• Only collect data necessary for legitimate purposes
• Don’t track sensitive information
• Configure Enhanced Measurement to disable unnecessary events

Why GA4 alone isn’t enough?

Data transfer concern: GA4 processes data on US servers. After the Privacy Shield was invalidated, transferring EU data to the US creates legal gray areas. Some EU authorities have ruled GA4 use illegal without additional safeguards.

Google’s role: Google is a data processor under GDPR, but you’re the data controller. You’re ultimately responsible for compliant data collection.

Enforcement variation: GDPR enforcement varies by EU country. What’s acceptable in one jurisdiction might be problematic in another.

Steps for maximum GDPR compliance:

1. Use Consent Mode V2(Google’s latest version)

• More granular consent controls
• Better privacy protection
• Required for some EU jurisdictions

2. Consider server-side tracking

• Process data on your own servers first
• More control over what’s sent to Google
• Additional technical complexity

3. Use Standard Contractual Clauses (SCCs)

• Legal mechanism for EU-US data transfer
• Available through Google’s data processing amendment

4. Document everything

• Keep records of consent
• Document data processing activities
• Maintain audit trail

5. Regular privacy audits

• Review what data GA4 collects
• Verify consent mechanisms work properly
• Update practices as regulations evolve

Alternatives if GDPR is a major concern:

• Matomo: Self-hosted, GDPR-friendly alternative
• Plausible: Privacy-first analytics
• Fathom: Compliant by design
• Simple Analytics: No cookies, no personal data

Bottom line: GA4 provides tools for GDPR compliance, but proper implementation, user consent, transparent privacy policies, and appropriate legal agreements are YOUR responsibility. Consult with legal counsel if you’re unsure about your specific situation.

Does GA4 require cookie consent?

The short answer: In most jurisdictions that have privacy laws (EU, UK, California, etc.), yes, you need cookie consent before GA4 tracking starts.

Why GA4 requires consent in many regions:

1. GA4 uses cookiesEven though GA4 can work without cookies, the default implementation uses cookies including:

• _ga: Main cookie storing unique client ID (2 years expiration)
• ga: Cookie for specific GA4 property
• _gid: Used to distinguish users (24 hours expiration)
• gac: Stores campaign information

2. These aren’t “strictly necessary” cookiesUnder GDPR and similar laws, cookies fall into categories:

• Strictly necessary: Required for site functionality (no consent needed)
• Analytics: Track user behavior (consent required)
• Marketing: Track users across sites (consent required)

GA4 cookies are analytics cookies, not strictly necessary, so they require consent.

3. User tracking involves personal dataGA4 tracks behavior that can identify individuals, making it personal data under GDPR. Processing personal data requires legal basis, typically user consent.

Where cookie consent is required:

EU/EEA (GDPR + ePrivacy Directive): Yes, explicit consent required before GA4 cookies are set

UK (UK GDPR): Yes, consent required

California (CCPA): Technically an opt-out rather than opt-in, but consent mechanisms still best practice

Other US states (Virginia, Colorado, Connecticut, etc.): Various requirements, many requiring opt-out capabilities

Canada (PIPEDA): Consent generally required

Brazil (LGPD): Consent or legitimate interest required

Australia (Privacy Act): Disclosure required, working toward more stringent requirements

Where consent might not be required:

• Many countries without comprehensive privacy laws
• Some interpretations of “legitimate interest” legal basis (risky approach)

How to implement consent properly:

1. Use a Consent Management Platform (CMP)Popular CMPs:

• OneTrust: Enterprise-grade solution
• Cookiebot: User-friendly, comprehensive
• Termly: Affordable option
• Cookie Yes: Good for small businesses
• Quantcast: Free tier available

2. Configure GA4 Consent ModeEnsures GA4 respects user consent choices:

• If user accepts: Full tracking
• If user declines: Cookieless measurement using modeling
• If user partially accepts: Tracking adjusted accordingly

3. Block GA4 until consentDon’t load GA4 tracking code until user consents:

Copy// Wait for consent before initializing GA4

if (userConsentedToAnalytics) {

gtag(‘config’, ‘G-XXXXXXXXXX’);

}

4. Make consent meaningful

• Clear explanation of what cookies do
• Easy-to-understand language
• Genuine choice (yes/no, not just “accept”)
• No pre-checked boxes
• Access to site if declined

5. Honor consent across sessions

• Store consent choice in cookie
• Don’t re-ask every page
• But allow users to change their mind

Common mistakes to avoid:

Cookie walls: Blocking site access until consent is given (generally not GDPR compliant)

Implied consent: Loading GA4 automatically and assuming silence means consent (not valid)

Pre-checked boxes: Having “accept” checked by default (not valid consent)

Unclear language: Vague privacy policies that don’t explain GA4 usage

No opt-out: Not providing way to withdraw consent later

Loading GA4 before consent: Starting tracking before user makes choice

Can GA4 work without cookies?

Yes, with limitations:

Consent Mode – Modeling When users decline cookies, GA4’s Consent Mode uses:

• First-party data
• Machine learning modeling
• Aggregate data
• Cookieless pings

This provides directional insights but less precision than full tracking.

Server-side tracking Process data on your servers before sending to GA4:

• More control over data collection
• Can implement cookie-free tracking
• More complex to set up

Client ID alternatives Use localStorage or other methods instead of cookies:

• Different legal implications
• May still require consent depending on jurisdiction

Bottom line for consent:

• If you operate in EU, UK, California, or other regulated jurisdictions: implement proper cookie consent for GA4
• Block GA4 loading until consent is obtained
• Use Consent Mode to respect user choices
• Update your privacy policy appropriately
• Consult legal counsel for your specific situation

GA4 can technically function without consent mechanisms, but doing so exposes you to significant legal risk in most developed markets.

What is Google Consent Mode in GA4?

Google Consent Mode is a framework that allows GA4 (and other Google tools) to adjust behavior based on user consent choices. It bridges cookie consent requirements with analytics needs:

How Consent Mode works:

Without Consent Mode:

• User declines cookies → No tracking at all → You lose all data from non-consenting users

With Consent Mode:

• User declines cookies → GA4 uses privacy-safe tracking methods → You get modeled data insights

Two consent types:

1. ad_storage(advertising cookies) Controls whether Google can store cookies for advertising purposes:

• Remarketing
• Conversion tracking for ads
• Personalized advertising

2. analytics_storage(analytics cookies) Controls whether Google can store cookies for analytics:

• GA4 tracking
• User behavior analysis
• Site statistics

Users can consent to one, both, or neither.

Consent Mode versions:

Basic Consent Mode (v1):

• GA4 only loads after user consents
• Ping sent to Google when consent denied (no cookies)
• Limited data collected from non-consenting users

Advanced Consent Mode (v2 – current):

• GA4 loads immediately but respects consent state
• More sophisticated cookieless measurement
• Better conversion modeling
• More accurate reporting

What happens in each consent state:

Full consent (both granted):

• Full cookie-based tracking
• Complete user journey tracking
• Detailed analytics
• Remarketing enabled

Partial consent (analytics granted, ads denied):

• GA4 tracking works normally
• No remarketing pixels
• No ad conversion tracking
• User behavior data collected

Partial consent (ads granted, analytics denied):

• Unusual scenario
• Ad cookies set but no analytics tracking
• Rarely used configuration

No consent (both denied):

• No cookies set
• Cookieless pings sent to Google
• Data modeling provides aggregate insights
• No personal identifiers collected

How Consent Mode improves data:

Conversion modeling: When users decline cookies, Consent Mode uses machine learning to:

• Estimate conversions that aren’t directly trackable
• Fill gaps in funnel data
• Provide directional accuracy

Behavioral modeling: Infers behavior patterns from:

• Users who did consent (full data)
• Cookieless pings from non-consenting users
• Aggregate trends
• First-party data

This gives you modeled insights instead of complete data loss.

Implementation:

Method 1: Via Consent Management Platform Most CMPs integrate with Consent Mode:

• OneTrust
• Cookiebot
• Cookie Yes
• Termly

They automatically send consent signals to Google.

Method 2: Manual implementation Add consent mode commands to your site:

Copy// Default state before consent (both denied)

gtag(‘consent’, ‘default’, {

‘analytics_storage’: ‘denied’,

‘ad_storage’: ‘denied’

});

 

// Update after user consents

gtag(‘consent’, ‘update’, {

‘analytics_storage’: ‘granted’,

‘ad_storage’: ‘granted’

});

Method 3: Via Google Tag Manager Configure Consent Mode in GTM:

• Create Consent Initialization tag
• Set up consent triggers
• Update consent based on user choice

Consent Mode V2 (latest version):

Added two new consent types:

ad_user_data: Controls whether user data can be sent to Google for advertising

ad_personalization: Controls whether data can be used for personalized ads

Required for EU/EEA/UK as of March 2024.

Benefits of using Consent Mode:

1. Better data completeness: Get modeled insights instead of no data from non-consenting users
2. Legal compliance: Respect privacy laws while maintaining analytics
3. Conversion tracking: Model conversions even without cookies
4. Future-proof: Works in cookieless future
5. Google Ads integration: Improve conversion tracking for campaigns

Limitations:

Not perfect accuracy: Modeled data is estimates, not actual measurements

Still requires consent: Consent Mode doesn’t eliminate need for cookie banners

Complex implementation: Requires technical setup and testing

Regional variations: Different jurisdictions interpret legality differently

Best practices:

1. Implement Advanced Consent Mode V2 for best results
2. Test thoroughly to ensure consent signals work correctly
3. Document consent flows for compliance purposes
4. Monitor consent rates to understand data coverage
5. Use with proper consent banner (Consent Mode isn’t a substitute for getting consent)

Checking if Consent Mode is working:

1. Open your website
2. Open browser DevTools (F12)
3. Go to Network tab
4. Look for requests to google-analytics.com
5. Check for gcs parameter (indicates Consent Mode active)
6. Values: G100 (full consent), G110 (ads denied), etc.

Common misconception: Consent Mode doesn’t eliminate the need for cookie consent banners. You still need to ask users for permission. Consent Mode just makes GA4 work better when users decline.

Bottom line: Consent Mode is essential for GA4 implementation in privacy-regulated regions. It balances compliance with data needs, providing modeled insights when users decline cookies while respecting their privacy choices.

GA4 TROUBLESHOOTING & COMMON ISSUES

Why is my GA4 data different from Universal Analytics?

If you’re comparing GA4 and Universal Analytics data, discrepancies are completely normal and expected. They’re not errors—they’re the result of fundamental differences:

Why the numbers don’t match:

1. Different data models

• UA: Session-based (groups interactions into sessions)
• GA4: Event-based (tracks individual interactions)
• Result: Session counts and user flows calculated differently

2. Cross-device tracking

• UA: Same person on phone and laptop = 2 users
• GA4: Cross-device tracking recognizes same person = 1 user
• Result: GA4 typically shows 10-30% fewer users

3. Session calculation differences

• UA: Sessions timeout at midnight; campaign changes start new sessions
• GA4: Sessions continue past midnight; campaign attribution handled differently
• Result: Session counts diverge, especially for late-night traffic

4. Bounce rate vs. engagement rate

• UA: Bounce = single-page session, regardless of time spent
• GA4: Non-engaged session = <10 seconds, no conversion, single page
• Result: Metrics aren’t comparable (they measure different things)

5. Bot filtering

• UA: Bot filtering configuration in settings
• GA4: Different bot detection methods and rules
• Result: Different amounts of traffic filtered out

6. Sampling thresholds

• UA: Sample after 500k sessions in date range
• GA4: Different sampling triggers
• Result: Sampled data may differ

7. Time zone handling

• UA: All data processed in property time zone
• GA4: Can handle time zones differently depending on configuration
• Result: Data might shift between days

8. Privacy & consent

• Both platforms affected differently by:
  • Ad blockers
  • Privacy browser settings
  • Cookie consent rates
  • DNT headers
• Result: Different percentage of traffic tracked

Typical discrepancies and expected ranges:

Users: GA4 typically 10-30% lower than UA (due to cross-device tracking)

Sessions: GA4 often 5-20% different from UA (could be higher or lower)

Pageviews: Generally similar but GA4’s “Views” may differ slightly

Bounce rate: Not directly comparable (different definitions)

Conversions: Can vary significantly if goal setups differ

What to do instead of comparing numbers:

1. Compare trends, not absolutesBoth platforms show traffic increasing 25%? That’s what matters, not whether it’s 10,000 vs. 11,000 users.
2. Use GA4 as your source of truth going forwardStop relying on UA data (it’s sunset anyway). Build GA4 baselines.
3. Document UA benchmarksBefore UA data disappears, note important metrics as historical reference:

• Average monthly users
• Typical conversion rates
• Seasonal patterns
• Key performance indicators

4. Focus on GA4’s new capabilitiesInstead of trying to recreate UA reports, leverage GA4’s advantages:

• Cross-device tracking
• Event-based flexibility
• Better ecommerce tracking
• Predictive metrics

5. Give GA4 time to build historyYou need at least 3-6 months of GA4 data before meaningful comparisons within GA4 itself.

When discrepancies indicate real problems:

GA4 shows ZERO data: Tracking isn’t installed or is broken

GA4 shows 90%+ less traffic: Major tracking implementation issue

Only specific pages missing: Tracking code not on those pages

Sudden drops/spikes: Could indicate tracking changes, not real traffic changes

No mobile traffic: Possible tracking issue with responsive design

How to validate GA4 is working correctly:

1. Real-time testVisit your site and confirm you appear in Real-time report
2. Tag AssistantUse Google Tag Assistant extension to verify tags fire
3. DebugViewEnable debug mode and watch events fire in real-time with all parameters
4. Compare multiple sourcesCheck GA4 traffic against:

• Server logs
• Email campaign click tracking
• Google Ads click counts
• Social media analytics

5. Monitor trendsDay-over-day changes should be gradual unless you have specific reasons (campaign launch, etc.)

The bottom line: Don’t expect GA4 and UA to match. They fundamentally measure things differently. Accept the discrepancies, understand why they exist, and move forward with GA4 as your analytics platform. Spending time trying to make the numbers match is futile and not worth the effort.

Why am I seeing (not set) in my GA4 reports?

“(not set)” appears in GA4 reports when a dimension doesn’t have a value for certain events or sessions. It’s not necessarily an error—sometimes it’s expected behavior:

Common reasons for (not set):

1. Page title not set

• Some pages don’t have <title> tags
• Page titles loading asynchronously after GA4 fires
• Single-page applications (SPAs) not updating title properly
• Fix: Ensure all pages have title tags; for SPAs, update title before tracking

2. Landing page attribution

• Sessions that started before GA4 was installed
• Direct traffic without referrer information
• First interaction predates tracking window
• Normal behavior: Can’t assign landing page to sessions that started elsewhere

3. Campaign parameters missing

• URLs without UTM parameters
• Internal traffic misclassified
• Manual campaign tagging incomplete
• Fix: Implement consistent UTM tagging for all campaigns

4. Geographic data unavailable

• User’s IP address anonymous or hidden (VPN, privacy tools)
• IP geolocation database doesn’t recognize IP
• Privacy settings prevent geographic identification
• Expected behavior: Some percentage will always show (not set)

5. Device information missing

• User agent string unrecognizable
• Bot traffic not fully filtered
• Privacy-focused browsers hiding device info
• Expected behavior: Small percentage is normal

6. Custom dimensions not populated

• Event fired without custom parameter
• Custom dimension configured but not sent
• Timing issue (dimension sent later than event)
• Fix: Verify custom dimension code sends with every relevant event

7. User properties not set

• New users before user property assignment
• Logic error in user property code
• Conditional user properties not meeting conditions
• Fix: Check user property implementation logic

8. Ecommerce data incomplete

• Transaction event missing required parameters
• Product array empty or malformed
• Item details not included
• Fix: Validate ecommerce implementation sends all required fields

How to investigate (not set) values:

Step 1: Identify where it appears

• Which report shows (not set)?
• Which dimension has (not set) values?
• What percentage of traffic shows (not set)?

Step 2: Check if it’s normal Some (not set) values are expected:

• Small percentage of geographic data: Normal
• Some landing pages in returning visitor data: Normal
• Campaign data for direct traffic: Expected

Step 3: Verify data collection

• Use DebugView to watch events in real-time
• Check if dimension populates for test events
• Validate code sends dimension with events

Step 4: Review implementation

• Inspect page source for missing tags
• Check timing of when dimension is set vs. when event fires
• Verify conditional logic for dimension assignment

Step 5: Examine patterns

• Does (not set) appear for specific pages only?
• For specific traffic sources only?
• For certain device types only?

Troubleshooting specific (not set) scenarios:

Page title (not set):

Copy// Ensure title set before page_view

document.title = “Your Page Title”;

gtag(‘event’, ‘page_view’);

Campaign data (not set):

• Verify UTM parameters in URL
• Check URL hasn’t been shortened/altered
• Confirm parameters aren’t stripped by redirects

Geographic data (not set):

• Generally unavoidable for VPN/proxy users
• If showing >10%, possible IP anonymization issue

Custom dimension (not set):

Copy// Send dimension WITH event

gtag(‘event’, ‘your_event’, {

‘custom_dimension’: ‘value’  // Include every time

});

When to worry about (not set):

High percentages: If >10-20% of a dimension shows (not set), investigate

Business-critical dimensions: If key metrics have (not set), fix immediately

Sudden increases: If (not set) suddenly jumps, recent change likely caused it

Complete sections: If entire reports show only (not set), tracking is broken

When (not set) is acceptable:

Geographic data: 5-15% (not set) is normal due to VPNs and privacy tools

Demographics: Significant (not set) expected (many users don’t share this data)

Landing page for returning users: Normal for sessions that predate tracking

Campaign data for direct traffic: Expected (no campaigns for direct visits)

Best practices to minimize (not set):

1. Ensure all pages have proper titles
2. Consistently tag campaigns with UTM parameters
3. Send custom dimensions with relevant events every time
4. Test implementation thoroughly before going live
5. Monitor (not set) percentages regularly to catch issues early
6. Document expected (not set) values so you know what’s normal

Bottom line: Some (not set) values are normal and unavoidable. Focus on reducing (not set) for business-critical dimensions while accepting that perfect data completeness is impossible due to privacy tools, bots, and edge cases.

Why is my GA4 Real-time report showing no users?

If the Real-time report shows zero users when you know people are on your site, you have a tracking issue:

Immediate checks:

1. Verify you’re looking at the correct property

• Check the property selector (top left)
• Confirm it’s the right website
• Organizations with multiple properties often look at the wrong one

2. Visit your own website

• Open your site in a new browser tab
• Check if YOU appear in Real-time report
• Wait 10-15 seconds for data to process

3. Check if tracking code is installed

• View page source (Ctrl+U or Cmd+Option+U)
• Search for your GA4 measurement ID (G-XXXXXXXXXX)
• Confirm GA4 code exists in <head> section

Common causes and fixes:

Cause: Tracking code not installed

• Code missing from pages
• Installation incomplete
• Fix: Install GA4 tracking code properly

Cause: Ad blocker

• Browser extensions blocking GA4
• Privacy-focused browsers (Brave, DuckDuckGo)
• Test: Try in incognito mode or different browser

Cause: Internal traffic filter

• You filtered your IP address
• All testing blocked by filters
• Fix: Temporarily disable filters in Admin > Data Settings > Data Filters

Cause: Wrong measurement ID

• Copied ID incorrectly
• Using UA tracking code instead of GA4
• Fix: Double-check measurement ID matches your GA4 property

Cause: Tag Manager not publishing

• GTM container in preview mode only
• Changes not published to live
• Fix: Publish GTM container version

Cause: Tag Manager trigger not firing

• Trigger misconfigured
• Trigger conditions not met
• Fix: Use GTM Preview mode to debug triggers

Cause: Consent blocking

• Cookie consent banner blocks GA4
• Consent not granted in testing
• Fix: Accept cookies or temporarily disable consent requirement for testing

Cause: JavaScript errors

• Site errors preventing GA4 code execution
• Conflicts with other scripts
• Fix: Open browser console (F12), check for errors

Cause: Incorrect domain

• Multi-domain setup issue
• Subdomain not tracked
• Fix: Verify data stream URL matches site URL

Cause: Server-side issues

• Content Management System blocking script
• Security plugin blocking tracking
• Caching preventing new code from loading
• Fix: Clear cache, check security settings

Cause: Network-level blocking

• Corporate firewall blocking Google Analytics
• Network policies preventing tracking
• Fix: Test from different network

Step-by-step troubleshooting process:

Step 1: Use Google Tag Assistant

1. Install Tag Assistant extension
2. Visit your website
3. Click Tag Assistant icon
4. Check if GA4 tag is detected and firing

Step 2: Check browser console

1. Open DevTools (F12)
2. Go to Console tab
3. Look for errors related to GA4 or gtag
4. Errors indicate implementation problems

Step 3: Check Network tab

1. Open DevTools (F12)
2. Go to Network tab
3. Filter for “collect” or “google-analytics”
4. Refresh page and look for GA4 requests
5. If no requests appear, tracking isn’t firing

Step 4: Verify in DebugView

1. Enable debug mode:
   • Add ?debug_mode=true to URL, or
   • Install GA4 Debug extension
2. Go to Admin > DebugView in GA4
3. Visit your site
4. Events should appear in DebugView
5. If they do, tracking works but might have Real-time delay

Step 5: Test from different contexts

• Different browser
• Incognito/private mode
• Different device
• Different network

If tracking works but Real-time is empty:

Sometimes tracking fires correctly but Real-time doesn’t show data:

Processing delay: Real-time usually updates within seconds but can occasionally delay

Filter misconfig: Filters might affect Real-time report differently

Time zone issues: Check if property time zone matches your location

Heavy traffic: High traffic can sometimes delay Real-time processing

Quick validation without Real-time:

If Real-time isn’t working but you need to verify tracking:

1. Check standard reports: Wait 24-48 hours and check Reports section
2. Use DebugView: More reliable for immediate validation
3. Check Explore: Create exploration with recent date range

After fixing the issue:

1. Clear browser cache
2. Hard refresh page (Ctrl+Shift+R or Cmd+Shift+R)
3. Wait 30 seconds
4. Check Real-time report again
5. Verify events are firing in DebugView

Preventing future issues:

1. Test after every tracking change
2. Use Tag Assistant for ongoing monitoring
3. Set up alerts for traffic drops
4. Document your setup so others don’t break it
5. Version control your tracking code

When to contact support:

If you’ve verified:

• ✅ Code is installed correctly
• ✅ No JavaScript errors
• ✅ Tags firing in Tag Assistant
• ✅ Network requests succeeding
• ✅ No filters blocking data

But Real-time STILL shows zero users after 24 hours, contact Google Analytics support—there may be a rare property-level issue.

Bottom line: Real-time showing no users almost always indicates installation or configuration issue. Methodically work through the troubleshooting steps above to identify and fix the problem.