Google Analytics 4 Tutorial: Setup, Events, and Testing for Beginners

Ishant

Ishant

Published : May 19, 2023 at 8:54 am

Updated : September 29, 2026 at 10:35 am

Google Analytics 4 -A comprehensive guide

Google Analytics 4 (GA4) helps you measure what people do on your website or app. To make it useful, create the right property and data stream, install one intended tagging setup, define meaningful events, and test the information before using it to judge marketing performance.

This beginner guide takes you from an empty account to a checked measurement setup for leads or ecommerce. It explains the questions that commonly cause confusion: what GA4 tracks automatically, how key events differ from advertising conversions, why reports can look empty, and how to find duplicate purchases.

Universal Analytics migration deadlines are historical. If you are setting up measurement now, build and verify a GA4 implementation. For deeper channel analysis once collection works, continue with our GA4 for marketing guide.

Quick Summary

  • Start with the business outcome: a successful lead submission, paid order, booking, or another clearly defined action.
  • Install the tag once through your chosen approach. Check existing plugins, integrations, and Google Tag Manager before adding another installation.
  • Automatic tracking is a starting point. Recommended business events often need additional implementation.
  • Test in Tag Assistant, DebugView, and Realtime. Then allow standard reports time to process data.
  • A GA4 key event is not automatically a complete Google Ads conversion setup. Check the linked account, conversion action, and intended campaign goals.
  • Validate against your order system or CRM. An event firing does not prove that its value, timing, or business meaning is correct.

Jump to: GA4 basics, measurement plan, installation, events and key events, lead tracking, ecommerce, testing, troubleshooting, reports, or FAQs.

What is Google Analytics 4, and what can it tell you?

GA4 organizes measurement around events. A page loading, a visitor requesting information, and an order being completed are different events. Parameters add context, such as the page location, form type, product, value, or currency.

That information can help answer practical questions: Which channels bring visitors? Which pages help people act? Where do shoppers drop out? Are the leads associated with a campaign becoming qualified customers?

GA4 only knows what the implementation and available signals tell it. It does not automatically understand whether a lead is genuine, whether a customer received an order, or whether a sale was profitable. Your CRM, ecommerce platform, and finance records remain important checks.

What is the difference between an account, property, and data stream?

  • Account: the administrative container for your Analytics setup.
  • Property: the reporting environment where the relevant data is collected and analyzed.
  • Data stream: a source sending data to that property, such as a website or an app.
  • Measurement ID: an identifier for a web stream, commonly beginning with G-, used when connecting measurement.

Keep a simple setup record with the business owner, property name, property ID, stream URL, measurement ID, and installation method. This small document helps prevent a future developer or agency from unknowingly creating a second setup.

Is GA4 free, and do you need Analytics 360 or BigQuery?

GA4 has a no-license-fee Standard offering and a paid Analytics 360 offering. Implementation, consent tooling, maintenance, and specialist support can still cost money. Most beginners should first define the measurement they need rather than selecting a paid tier by default.

BigQuery export is available for Standard properties. It is not limited to Analytics 360. Google’s BigQuery Export documentation explains the available export modes, quotas, and separate BigQuery costs. You do not need BigQuery to complete the beginner workflow below.

What should you track before installing GA4?

Write a measurement plan before adding tags. Choose a small set of actions that answer a business question, define the exact success condition, and identify the system that can confirm it.

Starter measurement plan: adapt these examples to your business
Business questionCandidate eventTrigger condition to verifyIndependent check
Are visitors viewing key pages?page_viewThe relevant page or virtual page view loadsPage URL and navigation test
Are forms producing real submissions?generate_leadThe form succeeds, not just a button clickSubmission record or CRM entry
Are people starting checkout?begin_checkoutThe store’s defined checkout-start action occursCheckout behavior and platform event
Are orders completed correctly?purchaseA completed order is confirmedOrder ID, items, value, and currency
Are refunds represented?refundThe selected refund workflow is processedRefund record tied to the order

These names use Google’s recommended event vocabulary where appropriate. Recommended events require implementation and context; listing a name in a plan does not make the event fire.

Should every click become a key event?

No. Treat browsing actions and business outcomes differently. A click on a phone number may show intent but does not prove that a call connected or became a qualified lead. A form-start event helps diagnose a funnel but should not be reported as a completed inquiry.

For a small service business, begin with a verified lead submission. For an online store, prioritize a correctly measured purchase. Add supporting actions when they help explain those outcomes.

How do you set up Google Analytics 4 on a website?

Step 1: How do you create the property and web stream?

  1. Sign in to Analytics with an account the business can retain access to.
  2. In Admin, create or select the appropriate account and create a property.
  3. Choose the reporting time zone and currency intentionally.
  4. Complete the business information and objectives requested.
  5. Add a Web data stream for the correct website and record its measurement ID.

Follow Google’s current property and stream setup instructions. Labels and available options can vary by account. Before creating anything new, check whether the business already has a working property.

Step 2: Should you use a CMS integration, Google Tag Manager, or direct code?

Use an approach you can maintain and test. A supported CMS integration can simplify a basic setup. Google Tag Manager is useful when you need to manage multiple tags and event rules. Direct Google tag installation can work when a developer maintains the site.

The main risk is layering methods without understanding what each sends. For example, a store app may send purchase events while a second GTM setup sends the same orders again. Inventory current tags and integrations before installing another one.

Step 3: How do you install the Google tag through GTM?

If you choose GTM and the web container is already correctly installed:

  1. Open the intended container and create a new tag.
  2. Select Google tag and enter the tag ID connected to your intended GA4 destination.
  3. Use the Initialization – All Pages trigger for the base tag, following your consent implementation.
  4. Save, preview, and verify the destination and consent behavior.
  5. Submit and publish the tested container version.

See Google’s GTM setup guide. Consent Initialization is a separate stage for setting consent defaults; it is not a substitute name for the base tag’s Initialization trigger. Do not change consent behavior just to make a test event appear.

Step 4: What should you check in enhanced measurement?

Review the options available in your web stream and test the interactions you intend to use. Enhanced measurement can collect common interactions, but it is not a complete business measurement plan. A recorded form interaction is not automatically proof of a valid lead, and ecommerce needs appropriate product and transaction data.

Google distinguishes automatic, enhanced-measurement, recommended, and custom events in its events overview. Avoid adding another implementation for an interaction until you know whether an existing one already records it.

What is the difference between an event, key event, and conversion?

An event records an interaction. A key event is an event marked as important to the business. A conversion created from an Analytics event supports advertising measurement and, when configured appropriately, campaign optimization.

For example, a successful inquiry can produce generate_lead. Marking it as a key event makes it available for business-outcome reporting. Creating the relevant Google Ads conversion is a further step when that outcome should support advertising measurement.

Use Google’s key-event and conversion explanation rather than assuming older tutorials use today’s terminology. Some conversion-management features roll out gradually, so interfaces can differ.

How do you mark an event as a key event?

First confirm that the intended event arrives with the correct name and meaning. In Admin, use the Events or Key events controls available in your property to mark or create the relevant key event. Check your permissions if the control is unavailable.

Do not mark every page_view as a business outcome just because a thank-you page receives page views. If you create a new event from a confirmation-page visit, constrain it to the intended condition. Google’s create-or-modify guidance distinguishes creating a separate event from overwriting an existing one.

How should you name events?

Use a recommended event when it matches the action. For a necessary custom event, choose a stable, descriptive name and document it. Google treats event names as case-sensitive, so generate_lead and Generate_Lead are different names. Follow the current event naming rules.

Keep a single event dictionary shared by marketing and development. A row should state the name, trigger condition, parameters, owner, and validation date. Avoid making one new event name for every campaign when a parameter can describe the useful difference.

How do you track form submissions and qualified leads in GA4?

Measure successful submission rather than the visitor’s attempt to submit. Depending on the form, that can be a reliable success event from the form system or a controlled confirmation-page workflow.

Why is a submit-button click not enough?

A visitor can click Submit with missing fields, encounter a server error, or click repeatedly. If every click creates a lead event, Analytics can report inquiries that the sales team never received.

For a test, submit one valid form, one invalid form, and one failed or interrupted attempt where practical. The valid submission should create the intended outcome. The invalid attempt should not be counted as a successful lead. Compare the event with the actual submission record.

How should a thank-you page trigger be checked?

Confirm that the page is reached only after the intended action. Then test refreshing it, revisiting it, and opening it directly. If those actions create extra leads, improve the trigger or use a success signal from the form system.

A simple page-based rule can be useful, but its assumptions need testing. Document those assumptions so a future site redesign does not silently break the measurement.

How do you distinguish a lead from a qualified customer?

Use the CRM to record qualification and sales outcomes. A form submission is an inquiry, not automatically an accepted lead or revenue. Connect the systems through an appropriate implementation when you need downstream measurement, and keep event definitions consistent.

Do not place names, email addresses, phone numbers, or form message text in ordinary GA4 event parameters or page URLs. Google’s PII guidance explains common leakage points. Dedicated user-provided-data features have separate requirements; they are not permission to send personal information in arbitrary fields.

How do you set up GA4 ecommerce purchase tracking?

A working base tag does not by itself prove that ecommerce reporting is complete. Your store integration or developer must supply the relevant events and product data. Validate a real checkout path, including any off-site payment step, against your order system.

Which purchase values should you inspect?

Purchase validation checklist
Field or behaviorWhat to verify
Event nameThe completed order sends the intended purchase event
transaction_idA non-empty order identifier that is unique to that transaction
value and currencyNumeric value and the correct currency, using Google’s documented definition
itemsProducts, identifiers or names, prices, and quantities match the order
Tax, shipping, and discountsHandled consistently without being counted twice
Refresh and revisit behaviorThe order confirmation does not create unintended extra transactions
Refund workflowRefund data can be reconciled with the original transaction

Use Google’s ecommerce implementation documentation for the exact parameter format. It requires currency when sending value and explains the item data used by ecommerce events.

What does a useful test-order record look like?

Illustrative test record: order TEST-1042, two units of one item at $30 each, USD currency, $60 item value, and separately recorded shipping and tax where applicable. Compare those fields in the order system, the outgoing event, and Analytics. This example is a QA worksheet, not code to paste into production.

Record the test time, browser, consent choice, event name, destination property, order ID, and observed result. Then repeat the test on a second order with a different ID. One successful event is not enough to prove that the ID changes correctly.

Why does GA4 show duplicate purchases?

Check for overlapping store integrations and GTM tags, repeated confirmation-page triggers, or client/server implementations sending inconsistent identifiers. Google documents purchase deduplication using transaction IDs for web streams. IDs must be unique per order, non-empty, and free of personal information.

Follow the transaction-ID guidance, but also fix the source of unintended duplicate sends. A changing ID for the same order can make one purchase look like several different transactions.

How do you test GA4 with Tag Assistant, DebugView, and Realtime?

Use the three tools to answer different questions. Tag Assistant helps inspect tagging behavior. DebugView helps inspect a debugging session and its event parameters. Realtime gives a short-window check that activity is arriving in the selected property.

What should you verify before publishing a GTM change?

  1. Open GTM Preview and connect it to the intended test page.
  2. Check that the correct container and Google tag are present.
  3. Perform the actual action, such as submitting the form or completing checkout.
  4. Inspect which tags fired and the values they sent.
  5. Find the corresponding event in GA4 DebugView with debugging enabled.
  6. Compare event parameters against the original submission or order.
  7. Publish the tested container, then repeat the essential check on the live site.

Google’s DebugView documentation describes debugging requirements and notes that consent or client-side privacy controls can affect visibility. Use an appropriate consented test session while separately confirming that refusal is respected.

What does a pass/fail check look like?

TestExpected evidenceFailure to investigate
Open a pageCorrect destination and intended page viewWrong property or duplicate installation
Submit an invalid formNo successful-lead outcomeA click or attempted submission counted as a lead
Submit a valid formMatching lead event and submission recordMissing event or missing backend record
Complete two test ordersTwo correct order IDs and matching valuesStatic IDs, wrong currency, or repeated sends
Change consent choiceBehavior follows the intended consent setupTags ignore the choice or testing assumes all visitors consent

Why is GA4 not showing data or key events?

Work from collection toward reporting. Randomly creating a new property or reinstalling tags can hide the original cause and introduce duplicates.

Why is there no activity in Realtime or DebugView?

Check the property and stream first, then the installed tag ID, published container, trigger conditions, consent state, and browser blocking. For DebugView specifically, confirm that debugging is enabled and that you selected the relevant device. An ordinary visit is not necessarily a debugging session.

Why does an event appear in debugging but not in standard reports?

Check the report date range, filters, event-name spelling, and whether the live container has been published. Then allow processing time. Google says data processing can take 24–48 hours, and reports can change during that period. Waiting does not fix a tag that never sent the correct data.

Why does GA4 show a key event but Google Ads shows no conversions?

Confirm that the intended Analytics property and Ads account are linked and that the correct conversion action was created. Check auto-tagging, attribution eligibility, date ranges, reporting delay, and the conversion goals used by the campaign. A test from unrelated traffic should not be treated as proof of an ad-attributed conversion.

Google’s conversion creation guide covers linking and setup. This question also appears in Analytics community discussions; use those discussions to identify symptoms, and official documentation to check the configuration.

For the next layer of detail, see our Google Ads conversion tracking guide. Avoid counting the same business outcome twice through overlapping primary conversion actions.

Why does GA4 revenue differ from the store’s revenue?

Compare the same dates, time zones, order statuses, and revenue definition. Inspect refunds, tax, shipping, discounts, currency, missing orders, duplicate sends, and consent-related gaps. Reconcile a small set of order IDs before comparing a whole month.

GA4 is an analytics system, not a replacement for the accounting ledger. For advertising-platform differences, continue with our guide to differing Google Ads, Meta, and GA4 ROAS figures.

Which GA4 reports should beginners use first?

Start with a question and choose the report that can answer it. Report collections vary with property configuration, so use the report name or search if your navigation differs.

QuestionWhere to startWhat to do with the answer
Is collection working now?Realtime and DebugViewValidate the setup before analyzing performance
Where are sessions coming from?Traffic acquisitionCompare relevant traffic and outcomes by source
Which entry pages need attention?Landing page reportingInspect pages with visits but weak intended outcomes
Are important actions being recorded?Events and key-event metricsCheck volume and business meaning against source records
Which products are selling?Ecommerce purchasesCompare recorded product sales with the store

How can you turn a report into one useful action?

Suppose a service landing page receives relevant visits but few verified inquiries. First test its form and tracking. If both work, inspect the offer, page experience, and traffic intent. Do not conclude that the page needs more visitors before checking whether existing visitors can complete the action.

For a store, compare a few product pages with their checkout and purchase paths. A weak result can reflect pricing, availability, delivery terms, traffic quality, or measurement. Use the data to narrow the question and then inspect the real customer experience.

What should a completed GA4 setup include?

  • A record of the account, property, stream, IDs, and responsible business owner.
  • A documented installation method and list of overlapping integrations checked.
  • An event dictionary with success conditions and parameter definitions.
  • A list of key events and any related Google Ads conversion actions.
  • Evidence from valid, invalid, repeat, and consent-related tests.
  • A simple reconciliation with orders or lead records.
  • A named owner for checking the setup after website, checkout, or form changes.

A useful setup is one your team can explain and maintain. For a visual introduction, Analytics Mania’s 2025 beginner video covers installation, reports, and event tracking; use the current Google documentation linked above for interface details that may have changed.

If you want help checking a setup, contact Hustle Marketers with the business outcome you need to measure and the symptoms you are seeing. For more advanced reporting and channel decisions, use the GA4 marketing guide.

What else do beginners ask about GA4?

Do I need Google Tag Manager to use GA4?

No. You can use a supported website integration or direct Google tag installation. GTM is useful when you need to manage tagging and event rules, but the right choice is the one you can maintain, document, and test.

Does GA4 automatically track purchases and form leads?

Do not assume it does. Automatic and enhanced measurement cover some interactions, but a reliable lead or purchase setup needs the correct success condition and supporting data. Test against the actual submission or order.

How long does GA4 take to show data?

Realtime can show activity relatively quickly, while standard reporting requires processing and may take 24–48 hours to settle. If no correct event is being sent, waiting longer will not solve the installation problem.

Can GA4 show data from before it was installed?

A new website tagging setup does not recreate visits that it never collected. Keep any existing historical reports and exports separate, and avoid presenting a new setup as if it had always been active.

Can GA4 tell me which leads became customers?

Only when the necessary outcome data and connections are implemented. A website form event alone does not reveal later qualification, sales, cancellations, or profitability. Use CRM records to validate those stages.

Will fixing GA4 make my website rank higher?

Installing or correcting GA4 does not itself guarantee better search rankings. Its value is helping you understand behavior and outcomes so you can make better decisions about content, campaigns, and the website.

Editorial note: Updated September 29, 2026. This is a beginner setup and validation guide. Example events, order IDs, and test records are illustrative. Technical details were checked against the linked Google documentation; menu labels and feature availability can vary.

Ishant

Ishant Sharma is the Founder and CEO of Hustle Marketers, a Google Partner digital marketing agency. With 12+ years of experience in Google Ads, Meta Ads, SEO, and e-commerce PPC, he has helped 2,500+ brands generate $780M+ in trackable sales. Upwork Top Rated Plus with 100% Job Success Score. Ishant Sharma is the digital marketing specialist, not the Indian cricketer of the same name.

I hope you enjoy reading this blog post. If you want my team to just do your marketing for you, click here.
Scroll to Top