Google Analytics 4 Cheat Sheet

Google Analytics 4 Cheat Sheet

Google Analytics 4 (GA4) is a web and app analytics platform that helps businesses understand how users discover their websites, interact with content, and complete important actions. This cheat sheet explains the essential GA4 concepts, metrics, events, reports, tracking methods, and troubleshooting steps that digital marketers should know.

1. What Is Google Analytics 4?

Google Analytics 4 is Google's analytics platform built around an event-based measurement model. Instead of relying primarily on session-based pageview measurement, GA4 records user interactions as events and uses parameters to provide additional context.

Businesses can use GA4 to understand:

• Where website visitors come from.

• Which pages and screens they interact with.

• How users engage with website content.

• Which marketing campaigns generate traffic.

• How visitors complete key actions.

• Which channels contribute to leads, sales, and other business outcomes.

GA4 is most useful when its tracking is configured correctly and the collected data is connected to clearly defined business objectives.

2. Understanding the GA4 Event-Based Model

In GA4, an event represents an interaction or occurrence that can be measured.

Examples include:

• page_view – A page is viewed.

• session_start – A session begins.

• first_visit – A user visits the website for the first time on a browser or device recognized by Analytics.

• scroll – A qualifying scroll interaction is recorded when enhanced measurement supports it.

• click – A qualifying click is recorded, such as an outbound click when enhanced measurement is enabled.

• file_download – A supported file download interaction is recorded.

• sign_up – A user completes a registration action when implemented.

• generate_lead – A user completes a meaningful lead-generation action.

• purchase – A purchase event is recorded.

Events may contain parameters that describe the interaction. For example, a purchase event can include transaction information, currency, value, and product details.

Why events matter: They allow marketers to measure meaningful actions rather than relying only on pageviews. However, events must be implemented and tested correctly to ensure they represent the intended user activity.

3. Important GA4 Terminology

Event: An interaction or occurrence recorded by Analytics.

Event parameter: Additional information attached to an event, such as a page URL, link URL, item name, or transaction value.

User: A user identity estimated using the property's reporting identity and available signals. It does not necessarily represent a verified individual.

Session: A group of interactions that begin when a session starts and follow GA4's session rules.

Dimension: A descriptive attribute used to organize data, such as source, medium, country, device category, or page title.

Metric: A numerical measurement, such as users, sessions, event count, engagement rate, or revenue.

Key event: An event identified as important to a business objective, such as a completed purchase or qualified lead submission.

Understanding these terms makes GA4 reports easier to interpret and helps prevent incorrect conclusions.

4. Essential GA4 Dimensions

Dimensions explain the characteristics of traffic and user interactions.

Common dimensions include:

• Session source: The source associated with a session, such as Google or a newsletter.

• Session medium: The medium associated with a session, such as organic, email, or paid advertising.

• Session source/medium: A combined view of the session's source and medium.

• First user source/medium: The source and medium associated with the user's first acquisition.

• Campaign: The campaign associated with the relevant acquisition or traffic record.

• Landing page: The page where a session begins.

• Page path: The path portion of a page URL.

• Page title: The title associated with a page.

• Device category: The device classification, such as mobile, desktop, or tablet.

• Country: The country associated with the reported activity.

• Event name: The name of the recorded event.

Important distinction: First-user acquisition dimensions and session acquisition dimensions answer different questions. First-user dimensions describe the initial acquisition context, while session dimensions describe the current session's acquisition context.

5. Essential GA4 Metrics

Total users: The number of users included under the selected reporting definition.

New users: Users recorded as new according to Analytics' available identifiers and reporting rules.

Sessions: The number of sessions recorded during the selected period.

Engaged sessions: Sessions that meet GA4's engagement criteria.

Engagement rate: The percentage of sessions that qualify as engaged sessions.

Bounce rate: The percentage of sessions that were not engaged. In GA4, bounce rate is the inverse of engagement rate.

Event count: The total number of recorded occurrences of the selected event or events.

Key events: The number of occurrences of events marked as important to the business, subject to the selected report and configuration.

Total revenue: Revenue recorded through supported and correctly implemented measurement.

Always check the reporting scope, date range, and event definitions before comparing metrics.

6. Engagement Rate and Bounce Rate

Engagement rate helps marketers understand how many sessions meet GA4's engagement criteria.

Formula:

Engagement Rate = Engaged Sessions ÷ Sessions × 100

For example, if a website records 1,000 sessions and 600 engaged sessions:

Engagement Rate = 600 ÷ 1,000 × 100 = 60%

Bounce rate is the inverse:

Bounce Rate = Non-Engaged Sessions ÷ Sessions × 100

Using the same example:

Bounce Rate = 400 ÷ 1,000 × 100 = 40%

A high engagement rate can be a useful signal, but it does not automatically mean the website is generating business value. Review engagement alongside conversions, lead quality, purchases, and other relevant outcomes.

7. Understanding Traffic Sources and UTMs

GA4 uses traffic-source information to help marketers understand how visitors arrive at a website.

Common acquisition categories include:

• Organic Search: Traffic attributed to unpaid search results.

• Paid Search: Traffic attributed to paid search campaigns.

• Direct: Traffic for which Analytics attributes the visit to direct entry or lacks sufficient referral information.

• Referral: Traffic attributed to links from other websites.

• Email: Traffic identified as email under the available campaign information and channel rules.

• Organic Social: Traffic attributed to unpaid social activity.

• Paid Social: Traffic attributed to paid social campaigns.

• Display: Traffic classified under display advertising rules.

Campaign URLs can use UTM parameters to identify marketing activity.

Common UTM parameters include:

• utm_source – Identifies the source, such as a newsletter or advertising platform.

• utm_medium – Identifies the medium, such as email or paid social.

• utm_campaign – Identifies the campaign.

• utm_content – Differentiates creative versions or links.

• utm_term – Can identify paid keywords or other term information.

Example campaign URL:

https://www.example.com/?utm_source=newsletter&utm_medium=email&utm_campaign=october_update

Use consistent naming conventions, including consistent capitalization. Avoid including personal or sensitive information in campaign URLs.

Do not add campaign UTMs to internal website navigation links because doing so can interfere with acquisition attribution.

8. GA4 Reports Every Digital Marketer Should Know

Reports overview: Provides a high-level view of the property's measured activity and available reporting summaries.

User acquisition: Helps marketers understand the sources and mediums associated with users' first acquisition.

Traffic acquisition: Helps marketers analyze how sessions are attributed to traffic sources and mediums.

Landing page analysis: Helps identify which pages begin sessions and how those sessions perform.

Engagement reports: Help evaluate pages, screens, events, and user interactions.

Monetization reports: Help analyze purchase activity and revenue when ecommerce measurement is correctly configured.

Events report: Helps review the events collected by the property.

Key events reporting: Helps evaluate important actions marked as key events.

Explorations: Provides more flexible analysis using techniques such as funnels, path exploration, segments, and cohorts, depending on the data and features available.

Report names, layouts, and available metrics may change as Google updates GA4.

9. How to Analyze Website Performance in GA4

Use a consistent process instead of reviewing individual metrics in isolation.

Step 1: Select the date range. Choose a period that matches the campaign or business question.

Step 2: Review acquisition. Identify which channels and campaigns are bringing visitors to the website.

Step 3: Analyze landing pages. Check which pages users enter through and whether those pages match the campaign or search intent.

Step 4: Review engagement. Examine engaged sessions, engagement rate, and relevant interactions.

Step 5: Check key events. Determine whether users complete the actions that matter to the business.

Step 6: Compare segments. Review performance by channel, device, landing page, campaign, or geography where the available data supports meaningful comparison.

Step 7: Investigate changes. Check whether tracking changes, campaign launches, website releases, seasonality, or consent behavior could explain differences.

Step 8: Recommend an action. Use the evidence to propose a specific improvement and define how its effect will be measured.

10. GA4 Tracking and Quality Assurance

Accurate analysis depends on reliable measurement.

Use this checklist when validating a GA4 implementation:

• Confirm the correct GA4 property and measurement ID.

• Verify that the tag is installed on the intended pages.

• Check that expected pageviews and events are collected.

• Confirm that event names and parameters are correct.

• Test key events using the intended user journey.

• Check that important events are not firing multiple times unintentionally.

• Validate purchase values, currencies, and transaction identifiers when ecommerce tracking is used.

• Review cross-domain journeys where visitors move between related domains.

• Check campaign URL parameters and naming conventions.

• Verify consent behavior and applicable privacy requirements.

• Confirm that internal traffic rules and filters are configured as intended.

• Compare GA4 results with relevant CRM, ecommerce, or backend records.

Use GA4 DebugView or other appropriate debugging tools to inspect events during testing. Real-time reports can also help confirm that activity is being received, although they do not replace a full implementation audit.

11. Common GA4 Problems and Troubleshooting

Problem: GA4 is not showing data.

Check the measurement ID, tag installation, consent state, browser restrictions, property selection, and whether the site is sending events.

Problem: Events are recorded twice.

Investigate duplicate tag installations, overlapping GTM triggers, plugins that send the same event, and repeated event dispatches.

Problem: Traffic appears as direct or unassigned.

Review UTM naming, redirects, referral information, campaign configuration, and whether the available source data is sufficient for channel classification.

Problem: GA4 reports fewer conversions than an advertising platform.

Compare conversion definitions, attribution models, lookback windows, time zones, consent behavior, reporting identity, and tag implementation. Different systems may legitimately report different totals.

Problem: Revenue does not match the ecommerce system.

Check purchase-event implementation, transaction IDs, currency, revenue values, refunds, duplicate transactions, and reporting dates.

Problem: Website traffic changes suddenly.

Check the affected pages, traffic sources, devices, countries, tracking changes, consent behavior, website deployments, and possible seasonality before assuming the change is caused by marketing performance.

12. GA4 Metrics and Formulas Quick Reference

For conversion rate, always identify the denominator. A conversion rate calculated from sessions will differ from one calculated from clicks or users.

13. GA4 Best Practices

• Define business goals and key events before implementation.

• Use consistent event names and parameter structures.

• Test tags and events before relying on reports.

• Use UTM naming conventions across marketing teams.

• Keep personal and sensitive information out of analytics events and URLs.

• Document tracking changes and annotate major releases.

• Compare reports using consistent dates, time zones, and definitions.

• Pair traffic metrics with meaningful business outcomes.

• Review tracking regularly, especially after website changes.

• Treat attribution as a measurement model rather than definitive proof of causation.

14. Final Checklist for Digital Marketers

Before using GA4 to make campaign or website decisions, confirm that:

• The correct property is receiving data.

• Important events are configured and tested.

• Key events represent meaningful business actions.

• Acquisition sources and campaign names are consistent.

• Landing pages and engagement metrics are understood.

• Conversion and revenue data are reasonably validated.

• Comparisons use aligned date ranges and definitions.

• Any major changes have been investigated before drawing conclusions.

Conclusion

Google Analytics 4 helps digital marketers understand how visitors discover and interact with websites, but useful insights depend on accurate tracking and thoughtful interpretation. By understanding events, dimensions, metrics, traffic sources, reports, and troubleshooting methods, marketers can make better-informed decisions about campaigns and website performance.

Use this cheat sheet as a quick reference when setting up tracking, analyzing reports, investigating discrepancies, or preparing for digital marketing interviews. Always verify current GA4 settings and reporting features in your property because the platform evolves over time.