GA4 · Google Tag Manager · Setup and debugging

Tracking that you can prove is working

Each guide does one job in GA4 or Tag Manager: install it, fire one event, or find out why an event never arrived. A container file or an event reference downloads with the guide, so nothing has to be retyped from a screenshot.

Latest guides

2026-11-12

Get access to the GA4 demo account: two real properties, Viewer role, no setup

Open the GA4 demo account to learn on real ecommerce and game data in two properties, with the Viewer role and no tag to install.
2026-11-12

Install GA4 on Wix: paste the Measurement ID into Marketing Integrations, no code

Create the GA4 property, turn off two web stream settings, and paste the Measurement ID into Wix Marketing Integrations. No code and no snippet to add.
2026-11-11

Install GA4 with Google Tag Manager: the Google tag, the first page_view, and the check that proves it works

One Google tag on the Initialization trigger sends page_view on its own. No second page_view tag, verified in Tag Assistant Preview, published as a version.
2026-11-11

Your GA4 purchase event never arrives: trace it with Tag Assistant and DebugView

Four checkpoints, in order: Preview, DebugView, the Measurement ID, and the 24 to 48 hour lag plus the custom dimension. Worked with Google's example order at $72.05.
2026-11-11

Install Tag Assistant and read what it says about your tags

Tag Assistant is the first check when GA4 data looks wrong: install it, connect your site, and read the tag list before you touch a single setting.
2026-11-11

Tag Assistant Preview: read Tags Fired and Tags Not Fired like a list of suspects

Preview lists every tag under Tags Fired or Tags Not Fired for each event. A tag under Not Fired names its own reason — read the trigger condition, not the tag.
2026-11-11

DebugView: find your own event in the stream and read its parameters

DebugView shows only devices in debug mode, one event at a time with its parameters. Pick your device, pick the minute, and the event is either there or it is not.
2026-11-11

debug_mode in Tag Manager: turn it on for one tag, then take it off again

In Tag Manager, debug_mode goes in the Google tag for all events or in one GA4 Event tag for a single event. The off switch is removing the field — false does not turn it off.
2026-11-11

debug_mode with gtag: one line in the config, and the line that turns it off

With gtag.js, debug_mode: true goes in the config command for all events or in one event call for a single event. Turning it off means deleting the parameter, not setting it false.
2026-11-11

The Google Analytics Debugger extension: read your hits in the console

The GA Debugger extension prints every Analytics hit to the browser console, with the full payload. It is the fastest way to see what a page actually sent.
2026-11-11

Read the network tab: the collect request is the proof the browser sent it

Every GA4 event leaves the browser as a collect request to google-analytics.com. Filter the network tab for collect, and a missing event shows up as a missing request.
2026-11-11

The Measurement ID does not match the stream: copy it, do not type it

A tag with the wrong Measurement ID fires cleanly and reports cleanly — into someone else's property. Compare the ID in the tag with the ID in the stream, character by character.
2026-11-11

Check the data stream: the stream is where the ID lives and the settings live

A web data stream is the collection point for a site: it holds the Measurement ID, the enhanced measurement switches, and the internal traffic rules. Check it before you blame the tag.
2026-11-11

Check the consent state: Tag Assistant shows what the visitor actually allowed

Tag Assistant has a Consent tab that shows the consent state for each event — granted or denied, per type. Read it before you decide the tag is broken.
2026-11-11

Your ad blocker is eating the GA4 requests: test with it off

Ad blockers stop the collect request before it leaves the browser, so Tag Assistant, the network tab, and GA4 all stay empty at once. The test is simple: turn it off and count again.
2026-11-11

Your own visits are filtered out: check the internal traffic rule and the filter state

GA4 marks your office IP as internal traffic, and an Active filter deletes it from reports permanently. A missing event from your own desk may be a filter doing its job.
2026-11-11

The report is empty because it is too soon: the 24 to 48 hour lag, checked properly

Standard GA4 reports take 24 to 48 hours to process data. An empty standard report ten minutes after a test proves nothing — Realtime and DebugView are the same-day checks.
2026-11-11

The custom parameter is sent but never shows: register it as a custom dimension

GA4 receives every parameter you send, but a custom parameter only becomes a dimension in your reports after you register it — and it only applies to events sent after registration.
2026-11-11

The event is in Realtime but not in the reports: separate arrival from processing

Realtime shows the past 30 minutes; standard reports take 24 to 48 hours. An event in Realtime and missing from the standard report is in processing, not lost — unless 48 hours have passed.
2026-11-11

The same event arrives twice: find the second sender and remove it

Duplicate events come from two senders, not from one tag firing twice. Count the senders — a second tag, a second snippet, or a tag plus gtag — and remove one.
2026-11-11

The event arrives but its parameters are missing: read the payload, then the tag

An event with no parameters is a tag that sends a name and nothing else. Read the payload in the network tab, then the parameter list in the tag, and the missing row will show itself.
2026-11-11

Revenue is in the wrong currency: the currency parameter decides the report

GA4 reports revenue in the property currency, converted from the currency parameter on the event. A wrong currency code turns every order into the wrong amount — check the code, not the total.
2026-11-11

Revenue is wrong by the same amount on every order: the value is not the total

The value parameter is the sum of price times quantity, without tax or shipping. An order total used as the value overstates revenue by tax plus shipping on every single order.
2026-11-11

The events are landing in the wrong property: find which property is getting them

When your property is empty but the tag fires, the events are going somewhere — usually a second property, a staging property, or an old one. Find the property that has them.
2026-11-11

Preview shows the draft, not the live site: publish before you judge the fix

Preview runs your workspace as if it were published, and only in the browser where you started it. Nobody else sees it, and the live site does not change until you publish a version.
2026-11-11

The tag is not firing: check the trigger before you rebuild the tag

A tag that never fires is usually a trigger that never matches. Read the trigger's conditions against the event, and Preview will name the one that failed.
2026-11-11

Consent denied means the events are missing by design: prove it, then decide

When a visitor declines analytics cookies, GA4 collects nothing for them in basic consent mode — or only cookieless pings in advanced mode. Missing events from decliners are not a tag fault.
2026-11-11

Events went missing after a site redesign: the tags stayed, the page changed

A redesign changes class names, page paths, and button text — and every trigger that matched the old page stops matching. Check the new page against the old triggers, one condition at a time.
2026-11-11

Events went missing after a GTM publish: the published version is not the one you tested

A publish ships the workspace as it stands — including a half-finished edit, a paused tag, or a change someone else saved. Check the live version, not the workspace.
2026-11-11

Send the purchase event with gtag.js: the order, the parameters, and the DebugView check

Google's own purchase tutorial, traced step by step: the gtag call on the confirmation page, the transaction ID that stops double counting, and the DebugView check that proves it arrived.
2026-11-11

Send the purchase event through Tag Manager: one GA4 Event tag and the data layer behind it

The same purchase, sent through Tag Manager instead of gtag: the data layer push, seven data layer variables, one GA4 Event tag, and a custom event trigger on the purchase event name.
2026-11-11

Send the add_to_cart event: the click, the items, and the value that makes the cart reports work

Add to cart is the event the purchase funnel and the Ecommerce purchases report both depend on: send it on the click, with the items just added and their value.
2026-11-11

Send the remove_from_cart event: the item taken out, and only that item

Remove from cart is the mirror of add to cart: send it when an item leaves the cart, with the removed item only, so the cart reports stop overstating what is still in there.
2026-11-11

Send the view_item event: the product page view that fills Items viewed

A page_view never fills Items viewed. The view_item event does: send it when a product page loads, with the product and its value, or the Ecommerce purchases report stays at zero.
2026-11-11

Send the view_item_list event: the list view that proves which products were shown

Before anyone clicks a product, the list page shows it. The view_item_list event records which products were displayed, in which list, so list performance is measured instead of guessed.
2026-11-11

Send the select_item event: the click on a product in a list

View_item_list says what was shown; select_item says what was chosen. Send it on the click, with the clicked item and its position, so list click-through is measured per product.
2026-11-11

Send select_content for items: the product click that is not a list click

Select_item is for a product in a list. Select_content is for content of a type: send it with content_type product when the click is on a product card outside a measured list.
2026-11-11

Send the begin_checkout event: the first step of checkout, with the cart that is being checked out

Begin_checkout opens the checkout funnel: send it when checkout starts, with the full cart and its value, so the purchase journey and checkout journey both have a starting point.
2026-11-11

Send the add_shipping_info event: the shipping choice, with the tier that fills the Checkout journey

The checkout journey has a shipping step that only this event fills: send add_shipping_info when the visitor picks a shipping method, with the tier in shipping_tier.
2026-11-11

Send the add_payment_info event: the payment choice, with the payment_type that needs a custom dimension to report on

The checkout journey has a payment step that only this event fills: send add_payment_info when the visitor submits payment details, with the method in payment_type.
2026-11-11

Send the refund event: the full refund, the partial refund, and the transaction ID that ties them to the order

Refunds do not happen on the website, so the browser never sees them. Send the refund event from the server with the original transaction ID, or GA4 keeps reporting gross revenue as net.
2026-11-11

Shape the ecommerce data layer: the ecommerce object, the clear, and the seven variables Tag Manager reads

Tag Manager never sees the order unless the site pushes it in Google's shape. The data layer is one ecommerce object per event, cleared before each push, with the same keys every time.
2026-11-11

The items array rules: what each item needs, the 200-item limit, and the 27 custom parameters

Every ecommerce event carries its products in one items array. The rules are short — item_id or item_name, quantity defaults to 1, 200 items at most — and breaking them empties the reports silently.
2026-11-11

The item parameters: item_id, item_name, price, quantity, brand, category, and the rest of the prescribed set

The items array has one prescribed parameter set, and the Ecommerce purchases report is built from it. Send the brand, the category, the variant, and the discount — not just the ID and the price.
2026-11-11

Currency and value: the pair that makes revenue appear, and the rule that breaks it when they split

Value without currency is a number Analytics cannot place. Send the two together, at the event level, in the currency the customer was charged in.
2026-11-11

Tax and shipping inside value: keep them out, and reconcile the charged total separately

Value is the items total. Tax and shipping are their own parameters. Put them inside value and item revenue is overstated by exactly the tax and shipping on every order.
2026-11-11

Check ecommerce in DebugView: debug_mode, the event stream, and what each parameter must read

Standard reports take about 24 hours, so the same-day check for ecommerce is DebugView: turn on debug_mode, trigger each event, and read its parameters and items before anything is published.
2026-11-11

Read the Monetization overview: total revenue, purchase revenue, and what the cards actually sum

The Monetization overview is the summary cards for revenue: total revenue, purchase revenue, purchasers, and average purchase revenue. Read the cards, then click through to the detail.
2026-11-11

Read the Ecommerce purchases report: items viewed, added to cart, purchased, and item revenue

The Ecommerce purchases report is the item-level table: one row per product, with items viewed, items added to cart, items purchased, and item revenue side by side.
2026-11-11

Create item-scoped custom dimensions: report on the extra fields you send inside the items array

The items array takes up to 27 custom parameters, but none of them can be reported on until you register it as an item-scoped custom dimension — scope Item, locked after save, explorations only.
2026-11-11

Read the Purchase journey funnel: session start to purchase, and where the funnel loses buyers

The Purchase journey is a closed funnel with five steps — session start, view product, add to cart, begin checkout, purchase — built from the ecommerce events you already send.
2026-11-11

Read the Checkout journey funnel: begin checkout to purchase, and which checkout step loses buyers

The Checkout journey is the four-step funnel inside checkout — begin checkout, add shipping, add payment, purchase — fed by the three checkout events and the purchase.
2026-11-11

Ecommerce in multiple currencies: send the currency charged, and let the property convert for its reports

A store that charges in more than one currency sends one currency per event — the one the customer paid in — and the property reports everything in its own reporting currency.
2026-11-11

The coupon on a purchase: the event-level code, the item-level code, and the Order coupons report

A purchase carries two coupon fields that are independent: the event-level code for the order and the item-level code for each item. Send both, spelled the same way every time.
2026-11-11

Read the GA4 Home report: what the first screen actually tells you, and what it hides

The Home report is a summary, not a verdict. Read its cards in order, check the date range, and confirm any surprise in the matching detail report.
2026-11-11

Read the Traffic acquisition report: where each session came from, and why it disagrees with User acquisition

Traffic acquisition counts sessions, not people. Read it by session default channel group, and never compare its numbers with User acquisition as if the scopes matched.
2026-11-11

Read the User acquisition report: which channels first brought your new users in

User acquisition groups each person by the channel of their first visit. Use it to judge what brings new people in — not what brings sessions back.
2026-11-11

Read the Engagement overview: events, pages, and time, before you open any detail report

The Engagement overview is a card summary of events, pages, and conversions. Use it to pick which detail report deserves the next hour.
2026-11-11

Read the Pages and screens report: which pages get the views, and which get the attention

Pages and screens ranks every page by views and engagement time. Read views beside average engagement time — a page can win one and lose the other.
2026-11-11

Read the Events report: which events fire, how often, and for how many people

The Events report lists every event by count and by users. Read count beside users — a high count with few users is one person firing it over and over.
2026-11-11

Read the Conversions report: which key events fired, and how many times each

The Conversions report lists key events only. Read it after the Events report — it shows the outcomes, not the noise around them.
2026-11-11

Customize a standard GA4 report: change its dimensions and metrics without breaking the original

Customizing a standard report means editing its dimensions, metrics, filters, and charts, then saving it as a new report so the original stays intact.
2026-11-11

Create a detail report in the Library: a blank table with your dimensions and metrics

A detail report starts blank or from a template in the Library. Pick dimensions and metrics, save it, then publish it to a collection so anyone can find it.
2026-11-11

Build a free-form exploration: a custom table from any dimensions and metrics

A free-form exploration is a crosstab you build by dragging dimensions to rows and metrics to values. It is the default technique for a new blank exploration.
2026-11-11

Build a funnel exploration: ordered steps, with the drop-off at each one

A funnel exploration defines the steps of a journey and shows where users leave it. Use open steps when the journey can span sessions; use closed steps when every step must happen in one visit.
2026-11-11

Build a path exploration: what users actually do before and after a page or event

A path exploration draws the branching routes users take from a starting point, or backwards from an ending point. Start backwards from purchase to see what converters really did.
2026-11-11

Build a segment overlap exploration: how much your audiences actually share

A segment overlap exploration draws up to three segments as a Venn diagram and counts the users in each overlap. It answers whether two audiences are really two audiences.
2026-11-11

Build a cohort exploration: retention by the week users first arrived

A cohort exploration groups users by when they first visited and tracks how many return in later weeks. It answers whether new users stay or vanish.
2026-11-11

Build a user lifetime exploration: revenue and engagement per user, over their whole life

A user lifetime exploration totals revenue, sessions, and engagement per user from their first visit. Use it to compare which acquisition channels bring users worth the most.
2026-11-11

Compare two groups in a GA4 report: build a comparison and read what actually differs

A comparison splits a detail report into two groups — for example, mobile against desktop — and shows both side by side. Build it from a dimension, not from a hunch.
2026-11-11

Build a segment in Explorations: define a group once, reuse it everywhere

A segment is a saved subset of users, sessions, or events that match conditions you set. Build it in Explorations, then apply it to any technique as a comparison.
2026-11-11

Segments versus audiences in GA4: which one to build, and where each one lives

A segment is a temporary lens for analysis; an audience is a saved group that other Google products can use. Build a segment to ask a question, an audience to act on the answer.
2026-11-11

Export a GA4 report to CSV or PDF: what each format keeps, and what it drops

A standard report exports to CSV, TSV, Google Sheets, or PDF. CSV keeps the data; PDF keeps the picture. Pick the format that matches what the reader will do with it.
2026-11-11

Share a GA4 report link: who can open it, and what they can change

Sharing a report sends a link that opens the report as the reader's own access allows. A shared report is readable; it is not a copy, and it is not editable by the reader.
2026-11-11

Apply a report filter in GA4: isolate one page, channel, or campaign in a detail report

A report filter narrows a detail report to rows that match a dimension condition. Add it from the top of the report, or build it into a custom report so it stays.
2026-11-11

Read the data-quality card: sampling, thresholds, and what GA4 withholds

The data-quality card at the top of a report says whether the numbers are complete. A yellow or red card means sampling or thresholds are in play — read the card before the numbers.
2026-11-11

Read the Landing page report: where each session started, and what the first page did

The Landing page report shows the first page of each session. Read it to find which entry pages engage and which ones send people straight back out.
2026-11-11

Data-driven attribution in GA4: what the model does, and how to check it is the model in use

Data-driven attribution splits credit across touch points using your own converting and non-converting paths. This guide shows where the setting lives and how to read the result.
2026-11-11

The GA4 Model comparison report: read data-driven against last click before you change anything

Model comparison puts two attribution models side by side for one key event, so you can see which channels gain and lose credit before you touch the property setting.
2026-11-11

Default channel grouping in GA4: how every session gets one channel, and why Unassigned appears

GA4 sorts every session into one default channel from its source, medium and campaign. You cannot edit the rules, so the fix for a wrong channel is the tagging you send in.
2026-11-11

Consent mode basic: Google tags stay blocked until the visitor answers the banner

In basic consent mode no Google tag loads and nothing is sent to Google until the visitor interacts with the consent banner. This guide sets that expectation before you build it.
2026-11-11

Consent mode advanced: tags load with consent denied, and send pings instead of setting cookies

In advanced consent mode Google tags load on page open with consent denied by default, then send pings without cookies while consent is denied and full data once it is granted.
2026-11-11

Consent default states: set all four consent types to denied before the first tag loads

A consent default state is the value each consent type holds before the visitor answers. Set analytics_storage, ad_storage, ad_user_data and ad_personalization to denied first, then let the banner update them.
2026-11-11

Consent mode in Tag Manager: the Consent Initialization trigger runs your defaults first

In Tag Manager, consent defaults belong on the Consent Initialization trigger, which fires before every other trigger. Put the default there and the Google tag obeys it.
2026-11-11

Set up a consent banner for GA4: what the banner must do, and what consent mode does not do

Consent mode is not a banner. The banner asks, records the answer and passes it on; consent mode only carries that answer to Google tags. Build the banner first.
2026-11-11

GA4 data retention settings: set 14 months before the 2-month default deletes your history

A new GA4 property keeps user and event data for 2 months by default. Change it to 14 months, the longest a standard property allows, and turn on reset on new activity.
2026-11-11

User data deletion requests in GA4: schedule a deletion, and know what it erases

A data deletion request removes chosen event parameters or user properties from a GA4 property. Schedule it from Admin, note the scope, and check the request after it runs.
2026-11-11

Set user properties in GA4: describe groups of users with a Google tag Event Settings variable

User properties describe groups of users, such as language or membership tier. Set them in Tag Manager with a Google tag Event Settings variable, then assign it to the Google tag.
2026-11-11

Custom user properties in GA4: register a user-scoped dimension so the property shows in reports

Sending a user property is only half the job. Register it as a user-scoped custom dimension in Custom definitions, or it will not appear as a dimension in your reports.
2026-11-11

Create a GA4 audience: build the condition, check the size, and name what it is for

An audience is a group of users defined by a condition on the data you collect. Build it in the audience builder, check how many users match, and name it for its use.
2026-11-11

Predictive audiences in GA4: use the suggested templates only when the property qualifies

A predictive audience has at least one condition based on a predictive metric, such as likely 7-day purchasers. Use the suggested template when it reads Ready to use.
2026-11-11

Event-scoped custom dimensions in GA4: register the parameter so it shows in reports

A custom event parameter is collected but not shown in standard reports until you register it as an event-scoped custom dimension. Register it in Custom definitions.
2026-11-11

Create a custom metric in GA4: turn a numeric event parameter into a number you can report on

A custom metric turns a numeric event parameter into a number you can sum and average in reports. Create it in Custom definitions, and use a dimension instead for text values.
2026-11-11

Custom dimension and metric registration lag: the 24 to 48 hour wait, and how to check it

A custom dimension or metric becomes usable in reports 24 to 48 hours after the data was sent and the definition was created. Plan the check for the second day, not the first hour.
2026-11-11

Property user management in GA4: add a user at the right access level, and remove access cleanly

Access in GA4 is set at account or property level in Access management. Add a user with the lowest role that does the job, and remove access from the same screen.
2026-11-11

GA4 property settings: industry, time zone and currency, set once and checked before you trust revenue

Property details hold the property name, industry category, reporting time zone and currency. Set them at creation, change them rarely, and know that a change applies going forward only.
2026-11-11

Send a GA4 event with the Measurement Protocol: the API secret, the client ID, and the POST

The Measurement Protocol sends events to GA4 from your server with a POST to mp/collect. You need a Measurement ID, an API secret, and the browser client ID so the event joins the right session.
2026-11-11

The Measurement Protocol validation server: check the event before production, and read every message

The validation server at debug/mp/collect checks your Measurement Protocol event and returns a list of validation messages. An empty list is the pass; anything in it is a fix.
2026-11-11

Delete a GA4 property: move it to Trash, use the 35-day window, and restore it if you meant another property

Deleting a GA4 property moves it to Trash, where it stays for 35 days before permanent deletion. Restore it from Trash inside that window if the deletion was a mistake.
2026-11-11

GA4 account settings: the account name, country and data sharing choices that sit above every property

Account settings hold the account name, country of business and data sharing choices for every property under the account. Edit them at account level, not property level.
2026-11-11

Create a Tag Manager account and a web container: one container per website, five container types

One Tag Manager account holds one container per website. Pick Web, name the container after the site's top-level URL, and the install step comes next.
2026-11-11

Install the Tag Manager container snippet: one block high in the head, one right after the body tag

Two code blocks on every page: the loader as high in the head as possible, the noscript iframe right after the opening body tag. Both carry the same container ID.
2026-11-11

Workspaces and folders in Tag Manager: one workspace per job, folders by purpose

A workspace is a draft copy of the container: one per job, never shared across jobs. Folders group tags, triggers and variables by purpose inside it.
2026-11-11

Save, name and restore container versions: the snapshot that lets you roll back

A version is a dated snapshot of the whole container. Name it after the change it carries, and Set as Latest Version is how a bad publish gets undone.
2026-11-11

Enable the built-in variables: the click, page and form values your triggers already use

Built-in variables sit switched off until you enable them. Click Text, Page URL and Form ID are the values your triggers compare against — enable the set your triggers need.
2026-11-11

Create a data layer variable: read a value the site pushed to the data layer

The data layer is where the site hands Tag Manager its values. A data layer variable names one key — ecommerce.value, for example — and returns what the site pushed.
2026-11-11

Create a constant variable: one place to change a value every tag shares

A constant variable holds a string that never changes at run time — a Measurement ID, an account number. Change it once and every tag that references it follows.
2026-11-11

Create a lookup table variable: map one value to another without a new tag per case

A lookup table turns one variable's value into another: the thank-you page URL becomes the right conversion ID. One variable replaces a tag per case.
2026-11-11

Create a URL variable: pull one part of the page address out of the URL

A URL variable splits the page address into its parts — hostname, path, query, fragment — so a trigger can fire on one section, or one order number.
2026-11-11

Create a regex table variable: match a pattern, not a list of exact values

A regex table is a lookup table with patterns: three patterns cover nine pages where a lookup table would need nine rows. The first matching pattern wins.
2026-11-11

Use the All Pages trigger: one trigger that fires on every page load

All Pages is a built-in trigger that needs no configuration. Attach it to a tag and the tag fires on every page — the default for anything site-wide.
2026-11-11

Build a click trigger: fire a tag when a button or link is clicked

A click trigger watches for clicks and filters on what was clicked — Click Text, Click ID or Click Classes. One trigger, one button, no code on the page.
2026-11-11

Build a form submission trigger: fire a tag when a form is sent

A form submission trigger fires when a form is submitted — filtered by Form ID so the newsletter form and the checkout form are measured separately.
2026-11-11

Build a scroll depth trigger: fire a tag when a reader reaches a depth

A scroll depth trigger fires at the percentages you set — 25, 50, 75, 90. On a 4,800-pixel page those are 1,200, 2,400, 3,600 and 4,320 pixels down.
2026-11-11

Build a history change trigger: fire a tag when a single-page app changes view

A single-page app never reloads the page — it changes the browser history instead. A history change trigger fires on pushState, replaceState and popState.
2026-11-11

Build a custom event trigger: fire a tag on a named event from the data layer

A custom event trigger fires when the data layer carries an event with an exact name. The site pushes {event: 'signup_complete'} and the trigger waits for that name.
2026-11-11

Build a timer trigger: fire a tag on a schedule, not on a click

A timer trigger fires every interval you set, up to a limit: 30,000 milliseconds, 10 times, is 300,000 milliseconds — 300 seconds, 5 minutes of measurement.
2026-11-11

Build a YouTube video trigger: measure starts, progress and completions

A YouTube video trigger fires at the progress points you pick — 10, 25, 50 and 75 percent of a 240-second video are 24, 60, 120 and 180 seconds in.
2026-11-11

Tag sequencing and firing priority: the order tags fire in, under your control

Firing priority is a number — higher fires first, 0 is the default. Sequencing is a promise: this tag fires before that tag, and the second waits for the first.
2026-11-11

Add a tag exception: stop a tag firing on one page without touching the tag

An exception is a blocking trigger: the tag fires wherever its firing trigger says, except where the exception says. All Pages minus the checkout page fires on 5 of 6 pages.
2026-11-11

Test a workspace in Preview mode: see what fires before anyone else does

Preview mode loads your workspace draft as if it were published — only in your browser, only for you. Tag Assistant shows which tags fired, in which order, on each event.
2026-11-11

Publish a Tag Manager version: Submit, check the changes, name it, publish

Publishing is Submit, then Publish and Create Version, then a name and a description. Nothing is live until that click — Preview tests the draft, the published version is what visitors load.
2026-11-11

Resolve a workspace conflict: pick the workspace side or the latest side, one item at a time

A conflict is one item changed in two places: your workspace and the latest version. The tool shows both side by side — pick one per item, never both.
2026-11-11

Manage Tag Manager users and permissions: two account levels, five container levels

Account access is User or Administrator. Container access is No access, Read, Edit, Approve or Publish. Give the lowest level that lets the person do their job — and keep two administrators.
2026-11-11

Export and import a container, and watch its size: merge versus overwrite, and the reported 200 KB limit

Export is Admin, then Export Container, then Download. Import is Overwrite or Merge. The container is widely reported to cap at 200 KB — Google warns at 70 percent, 143,360 bytes.
2026-11-11

Create a GA4 account and property: the account name, the property name, and the two roles that gate the clicks

Create the Analytics account, then the GA4 property inside it, with the reporting time zone and currency set before the first event arrives.
2026-11-11

Add a web data stream: the stream that turns your website into a source of events

Add a web data stream to the property, enter the website URL and a stream name, and the property gains its Measurement ID.
2026-11-11

Find your Measurement ID: the G- ID that ties the tag to the property

Open the web stream details page and copy the Measurement ID from Stream details — never retype it from memory.
2026-11-11

Turn on scroll tracking: the 90% depth event in enhanced measurement

Keep the Scrolls toggle on in enhanced measurement so GA4 fires a scroll event the first time a visitor reaches 90% of a page.
2026-11-11

Turn on outbound click tracking: the click event that leaves your domain

Keep the Outbound clicks toggle on so GA4 fires a click event with the link URL every time a visitor leaves your domain.
2026-11-11

Turn on site search tracking: the five query parameters that trigger view_search_results

Keep the Site search toggle on and add your search parameter if the site uses a non-standard one, so every search lands as view_search_results.
2026-11-11

Turn on video engagement tracking: start, progress, and complete for embedded YouTube video

Keep the Video engagement toggle on so embedded YouTube videos send video_start, video_progress at four thresholds, and video_complete.
2026-11-11

Turn on file download tracking: the extensions that trigger file_download

Keep the File downloads toggle on so every click on a PDF, spreadsheet, or zip sends a file_download event with the file name.
2026-11-11

Install the Google tag with gtag.js: the snippet that goes right after the opening head tag

Copy the Google tag from the stream's installation instructions and paste it immediately after the opening head tag on every page.
2026-11-11

Configure your web data stream settings: enhanced measurement, tag settings, and the Measurement ID in one place

Open the web stream details page once and work through its settings: the Measurement ID, enhanced measurement, and the tag settings underneath.
2026-11-11

Install GA4 on WordPress with Site Kit: Google's official plugin places the tag

Install Site Kit by Google, connect the Google account that can use the property, and let the plugin place the Google tag on every page.
2026-11-11

Install GA4 on Shopify: the Google & YouTube channel connects your property

Install the Google & YouTube channel in Shopify, connect the GA4 property, and the channel sends the shop's ecommerce events to GA4.
2026-11-11

Define internal traffic: tag your office IP addresses so the filter can exclude them

Define an internal traffic rule for the office IP addresses so GA4 tags the team's own visits with traffic_type internal.
2026-11-11

Filter developer traffic: keep debug_mode events out of your reports

Create a developer traffic data filter so events sent with debug_mode on never reach the reports.
2026-11-11

Set up cross-domain measurement: one user, one session across two domains

List the second domain in the stream's Configure your domains settings so GA4 passes the same IDs across it with the _gl parameter.
2026-11-11

Track subdomains in GA4: one property, one Measurement ID, no cross-domain setup

Put the same Measurement ID on every subdomain and GA4 tracks the whole domain as one journey — no cross-domain setup needed.
2026-11-11

GA4 account and property structure: how accounts, properties, and data streams fit together

Learn the four levels — organization, account, property, data stream — and the limits at each level before creating anything.
2026-11-11

Add users to a GA4 property: five roles, two levels, and the lowest role that works

Add a user in Property access management, pick the lowest of the five roles that lets them do the job, and never share a login.
2026-11-11

The GA4 setup checklist: twelve checks before you call the property done

Work through twelve checks — property, stream, tag, toggles, retention, filters, users — and the property is set up rather than half set up.
2026-11-11

Enable enhanced measurement: seven automatic events, no code changes

Slide the enhanced measurement switch on in the web stream settings and GA4 starts sending seven automatic events right away.
2026-11-11

Set a property's time zone and currency: the two choices that shape every report date

Set the reporting time zone and currency when creating the property — and change the time zone no more than once a day afterwards.
2026-11-11

Use the GA4 Setup Assistant: the checklist that finishes a new property

Open the Setup Assistant in Admin after creating the property and work its list — data collection, settings, and links — until nothing is left.
2026-11-11

Confirm GA4 is collecting data: Realtime now, standard reports in 24 to 48 hours

Browse the site, open Realtime, and see the visit within minutes — then wait 24 to 48 hours before judging the standard reports.
2026-11-11

Track logins with the recommended login event: method, the GA4 Event tag, and the check in DebugView

Send login with its method parameter through a GA4 Event tag, so every sign-in counts once and the split by method shows in the reports.
2026-11-11

Track sign-ups with the recommended sign_up event: method, the GA4 Event tag, and the thank-you page trap

Send sign_up with its method parameter on the account-creation success, so new accounts count once and the split by method shows in the reports.
2026-11-11

Track site search with the recommended search event: search_term, the GA4 Event tag, and the empty-query trap

Send search with its search_term parameter on every submitted query, so the words visitors actually type become a list in the reports.
2026-11-11

Track search results pages with the view_search_results event: search_term, the GA4 Event tag, and the search-vs-results split

Send view_search_results with its search_term parameter when the results page loads, so searches and result views stay two separate counts.
2026-11-11

Track shares with the recommended share event: method, content_type, item_id, and the GA4 Event tag

Send share with its method, content_type, and item_id parameters on the share action, so each channel's shares show per piece of content in the reports.
2026-11-11

Track leads with the recommended generate_lead event: value, currency, and the GA4 Event tag

Send generate_lead with its value and currency parameters when a form or request lands, so every lead carries a monetary value into the reports.
2026-11-11

Track content picks with the recommended select_content event: content_type, item_id, and the GA4 Event tag

Send select_content with its content_type and item_id parameters when a visitor picks a piece of content, so the most-picked items show in the reports.
2026-11-11

Track onboarding with tutorial_begin and tutorial_complete: the two recommended events that make a completion rate

Send tutorial_begin when a visitor starts the onboarding tutorial and tutorial_complete when they finish, so the completion rate is one subtraction and one division.
2026-11-11

Track form submissions with the recommended form_submit event: form_id, the GA4 Event tag, and the submit-vs-accepted split

Send form_submit with its form_id, form_name, form_destination, and form_submit_text parameters when a form is submitted, so each form's submissions show in the reports.
2026-11-11

Track video watches with video_start and video_complete: the two recommended events that make a watch rate

Send video_start when playback begins and video_complete when it ends, with the video parameters, so the watch rate is one subtraction and one division.
2026-11-11

Create a custom event in the GA4 interface: no code, from an existing event, with the 50-event limit

Build a new event from one GA4 already collects — for example thank_you from page_view on the confirmation URL — without touching the site or the tags.
2026-11-11

Create a custom event with a GA4 Event tag in Tag Manager: any name, any trigger, no interface limit

Build a custom event as a GA4 Event tag on its own trigger, so an action GA4 does not already measure gets a name and parameters of your own.
2026-11-11

Add an event parameter to a GA4 Event tag: one row, one variable, and the registration that makes it visible in reports

Add a parameter to an existing GA4 Event tag — a data layer variable, one row in the tag, Preview, publish — then register it so the reports can use it.
2026-11-11

The 25-parameter limit per event: count the parameters, keep the useful ones, drop the rest

An event can carry at most 25 parameters, and the 26th is dropped silently — audit the tag, count what it sends, and cut before the limit cuts for you.
2026-11-11

Modify an event in the GA4 interface: change what an existing event measures, without touching the tags

Edit a created event's conditions or parameters in the GA4 interface, so an event that nearly measures the right thing starts measuring it — with the warning that the change overwrites the original.
2026-11-11

Rename an event in GA4: there is no rename button — the supported path is Modify, and history stays under the old name

GA4 has no rename button for an event. The supported way to change a name is to modify the created event or build a new one from it — and the old name's history is never renamed.
2026-11-11

Mark an event as a key event: the star, the counting method, and the 30-event limit

Mark generate_lead as a key event from the Events page, pick the counting method, and set a default value — so the action that matters gets counted as a key event from that day on.
2026-11-11

Give an event a value: the value and currency parameters, and what they do in the reports

Add the value and currency parameters to any event — not only purchases — so GA4 can sum it, report revenue from it, and pass it to Google Ads.
2026-11-11

Event naming rules: 40 characters, letters numbers and underscores, and the names you must never reuse

Name an event with lowercase letters, numbers, and underscores, starting with a letter, under 40 characters — and never reuse a reserved name or prefix for a different meaning.
2026-11-11

Event count versus event users: the ratio that tells you whether an event fires once or all the time

Divide event count by total users to get event count per active user — the number that says whether people trigger an event once or again and again.
2026-11-11

See events in Realtime: the Event count by Event name card and the last 30 minutes

Open the Realtime report after firing an event, read the Event count by Event name card, and click the event to check its parameters — the check that works within minutes.
2026-11-11

Unmark a key event in GA4: remove the star, and what happens to the numbers

Unmark a key event from the Key events tab in Admin, and read the reports knowing the change is forward-only.
2026-11-11

The default key events GA4 creates: purchase, and what is already marked for you

GA4 marks purchase as a key event on its own. Check the Key events tab before you mark anything twice.
2026-11-11

Key event counting method: once per event against once per session, and which to pick

Keep once per event for purchases. Use once per session only when one count per visit is the definition you want.
2026-11-11

Sessions with key events in GA4: what the metric counts, and how to read it

Sessions with key events counts visits with at least one key event. It is the numerator of the session key event rate.
2026-11-11

Session key event rate in GA4: the formula, and why it is not the key event count

Session key event rate is sessions with a key event divided by sessions. Quote the rate with its denominator.
2026-11-11

User key events in GA4: users who triggered a key event, and the user key event rate

User key events counts people, not visits. One user with three sessions and two purchases still counts once.
2026-11-11

Key events in GA4 advertising reports: Conversion performance, and what stays out

Google Ads conversions from key events appear in Advertising, under Conversion performance. They do not appear in standard reports.
2026-11-11

Create a key event from an existing event in GA4: the Create event step, then the star

Build the new event from the old one with a condition, then mark it. The key event only counts from creation.
2026-11-11

Mark a key event through Tag Manager: the GA4 event tag, then the star in GA4

Send the event with a GA4 event tag in Tag Manager, confirm it in DebugView, then mark it as a key event in GA4.
2026-11-11

Key event attribution in GA4: data-driven credit, and the 90-day lookback window

GA4 credits key events with data-driven attribution by default. The lookback window decides how far back a touch can reach.
2026-11-11

Key event reporting lag in GA4: the 24-hour wait, the 24 to 48 hour standard reports, and 7 days of updates

A key event marked today can take up to 24 hours to show in standard reports. Attributed key events can update for up to 7 days.
2026-11-11

Key event for a form submit in GA4: generate_lead, the success signal, and the rate

Send generate_lead only when the form succeeds. Mark it as a key event, and count submissions against the business inbox.
2026-11-11

Key event for a phone-number click in GA4: the tel link, the click event, and the rate

Send a click event when a visitor taps the phone number, and mark it as a key event. A tap is interest, not a booked call.
2026-11-11

Key event rate by channel in GA4: compare organic, paid, and direct on the same key event

Read the session key event rate per channel in Traffic acquisition, with the same key event and the same dates on every row.
2026-11-11

Conversion against key event in GA4: the same action, two names, and which report holds each

A key event measures the action in GA4. A conversion is that key event shared with Google Ads to measure campaigns and bid.
2026-11-11

Purchase as a key event for ecommerce: the key-event side of the order, not the tag

Purchase is a key event by default in GA4. Read the key-event side: count, rate, and value, without rebuilding the tag.
2026-11-11

Key event for file downloads in GA4: file_download, the file name, and the rate

Mark file_download as a key event only when every download matters. Otherwise build a new event for the one file that does.
2026-11-11

Key event for video plays in GA4: video_start, video_complete, and which one to mark

Mark video_complete for a video that must be watched, and video_start only when starting is the outcome. Check the 10% progress marks.
2026-11-11

Key event for newsletter sign-ups in GA4: sign_up, the confirmed subscriber, and the rate

Send sign_up when the subscription is confirmed, and mark it. A sign-up form shown is not a subscriber.
2026-11-11

Key event for outbound link clicks in GA4: outbound_click, the partner link, and the rate

Mark outbound_click as a key event only for the links that earn the business something. Otherwise build a narrow event for one link.
2026-11-11

Key events in GA4 Explore reports: build a free-form exploration on one key event

Build a free-form exploration with Event name as rows and Key events as the value. Filter to the key event before you read it.
2026-11-11

Read the Tech details report: browser, device, operating system and screen resolution

The Tech details report shows the technology your visitors used — browser, device, operating system and screen resolution — one row per technology, ranked by users.
2026-11-11

Read the Search terms report: the queries behind your clicks, once Search Console is linked

The Search terms report shows the Google queries that brought people to your site — clicks, impressions, click-through rate and average position — but only after Search Console is linked.
2026-11-11

Delete a user's data with the User Deletion API: one POST, one identifier, and the 63-day wait

The User Deletion API deletes one user's data by programmatic request — one POST, one identifier, and the analytics.edit scope — where the Admin screens handle one request at a time.
2026-11-11

The events GA4 collects on its own: first_visit, session_start and user_engagement — and why you never recreate them

GA4 collects first_visit, session_start, user_engagement and the rest of the automatic events with no code of yours — know which ones arrive on their own before you build a tag for one.
2026-11-11

Link GA4 to Google Ads: the Product links step, the 400-link ceiling, and the 48-hour wait

Linking a Google Ads account to a GA4 property puts Ads data in GA4 reports and lets Ads import GA4 key events — up to 400 links per property, data within 48 hours.
2026-11-11

Set up the BigQuery export: the Cloud project, the link, and the 1-million-event daily ceiling

The BigQuery export sends every raw GA4 event into BigQuery tables — one dataset per property, one table per day — once the Cloud project is ready and the link is made in Admin.
2026-11-11

Send a custom event with gtag.js: one gtag call below the tag snippet, and the check in Realtime

A custom event in gtag.js is one gtag call with the event name and its parameters, placed below the Google tag snippet — Google's own example sends signup_newsletter with a method parameter.
2026-11-11

The recommended events reference: the ten events for every property, and the online-sales set

Recommended events are the standard events Google defined for common actions — ten for every property, plus the online-sales set — each with parameters that unlock prebuilt reporting.
2026-11-11

The GA4 event limits reference: 25 parameters, 40-character names, and the 100,000-a-day ceiling

GA4 drops what exceeds its collection limits and refuses what exceeds its configuration limits — 25 parameters per event, 40-character names, 100,000 events per user per day.
2026-11-11

Mark a key event with the Admin API: one POST, the counting method, and the default value

The Admin API marks a key event with one POST to the property's keyEvents collection — eventName, a required counting method, and an optional default value and currency.
2026-11-11

List your key events with the Admin API: the inventory check, and the slots you have left

One GET returns every key event in a property — name, event name, counting method, default value, and whether it is custom — so you can count the custom slots used against the 30-event limit.
2026-11-11

Find your key events in the BigQuery export: filter by event name, because there is no key-event column

The BigQuery export has no flag that marks a row as a key event — the export is raw events, one row each — so you bring your own key-event list and filter event_name against it.