By Mehdi HassanWhat does a correct GA4 setup look like for a marketing website?
A correct GA4 setup for a marketing website is one where you can trust two numbers: how many leads each page produces and how many leads each channel brings. That means one clean property, the tag installed once, consent handled properly, real conversions tracked as key events and nothing inflating the data, such as your own team's visits or payment-provider referrals.
Many startup GA4 properties fail at least one of these. They were set up in a hurry at launch, collect page views and enhanced measurement events, and nobody can answer which landing page brings demo requests. This guide is deliberately narrow: it skips GA4 features a marketing site rarely needs and focuses on the setup that answers founders' questions. Each section links to a deeper guide in this series.
Area | What good looks like | Deep dive |
|---|---|---|
Property and tag | One property, one web stream, tag installed once | |
Events | A written plan with consistent names | |
Conversions | Forms, bookings and signups as key events | |
Consent | Consent Mode v2 set before any tag fires | |
Attribution | Consistent UTMs on every campaign link | |
Reporting | A short weekly dashboard |
Which questions should GA4 answer for a startup?
GA4 should answer a handful of questions that change decisions: which channels bring qualified visitors, which pages turn them into leads, where visitors drop off before converting and whether a redesign or campaign moved the numbers. If a setting, event or report doesn't help answer one of those, it can wait.
- Which channels bring demos and signups? Needs key events and consistent UTMs.
- Which landing pages convert? Needs key events tied to the page they happened on.
- Is the pricing page helping or hurting? Needs page views and the path from pricing to the form.
- Did the redesign or campaign work? Needs stable tracking across the change and long enough data retention.
- Are visitors from AI assistants and search worth the effort? Needs channel groups that separate them.
Writing these questions down before you configure anything is the single most useful step, and it's what a tracking plan formalizes. It keeps the property small, which keeps it understandable.
How do you do a GA4 setup step by step?
Do the GA4 setup in this order: create the property, install the tag, fix the settings that GA4 gets wrong by default, then add events, consent and integrations. Doing settings early matters, because some of them, like data retention, only apply from the moment you change them.
Create the property and web stream
In GA4 Admin, create a property with your reporting time zone and currency, then add one web data stream for your domain. Use one property for the marketing site and app if they share a domain and you want the full journey.
Install the tag once
Add the Google tag directly, through your platform's integration, or through Google Tag Manager. Pick one method; duplicate installs double-count everything.
Extend data retention
Under Data collection and modification, change event data retention from the short default to the longest option, so explorations can look back more than a quarter.
Filter internal traffic
Define your office or VPN IP addresses as internal traffic and activate the data filter, after testing it, so your team's visits don't skew page reports.
List unwanted referrals
Add payment providers, scheduling tools and login domains that visitors bounce through, so a booked demo isn't credited to calendly.com or stripe.com.
Set up consent
Implement Consent Mode v2 with your cookie banner, so defaults are set before tags fire. See our Consent Mode v2 guide.
Track key events
Send events for demo requests, booked meetings and signups on confirmed success, and mark them as key events. Our conversion tracking guide covers embedded forms.
Link Search Console and Google Ads
Link Search Console for query and landing page data, and Google Ads if you run campaigns, so key events can be imported for bidding.
Which events and key events should a marketing site track?
A marketing site should track a small set of events that describe the path to a lead: page views, a few intent signals like pricing views and CTA clicks, and the outcomes themselves. Only the outcomes become key events. Everything else is diagnostic, useful for understanding behavior but not something to optimize for.
Event | When it fires | Key event? |
|---|---|---|
page_view | Every page load, automatically | No |
cta_click (custom) | A primary call-to-action button is clicked, with the button label as a parameter | No |
generate_lead | A demo or contact form is confirmed submitted | Yes |
book_meeting (custom) | A scheduler booking is confirmed | Yes |
sign_up | A trial or account is created | Yes |
newsletter_signup (custom) | An email subscription is confirmed | Optional |
file_download | A PDF or asset is downloaded, via enhanced measurement | No |
Use GA4's recommended event names where they fit, such as generate_lead and sign_up, and snake_case custom names for the rest. Add a form_name or plan parameter so one event can be split by form or plan in reports, instead of creating a new event for every variant. Leave enhanced measurement on for scrolls, outbound clicks and downloads, but turn off its form interactions, which misfire on most sites.
Why we keep key events to three or fewer
Every key event you add becomes a column in acquisition reports and a candidate for ad-platform bidding. With three key events, a founder can see at a glance which channel brought demos. With twelve, the total conversion count mixes newsletter signups, PDF downloads and demo requests into one meaningless number.
If an action matters but isn't a lead, track it as a normal event and build an exploration around it. Promote it to a key event only if you'd change budget or design decisions based on it alone.
How do consent and privacy affect GA4 setup?
Consent decides how much data GA4 can collect, and in the EU, UK and other regions that require it, it's a legal requirement, not an option. With Google Consent Mode v2, GA4 adjusts its behavior to each visitor's choice and can model some of the missing data. Without it, or with it set up wrong, you either collect data you shouldn't or lose data you could have had.
The errors that quietly break data are well known: tags firing before the consent default is set, missing ad_user_data and ad_personalization signals, defaults that don't carry across domains, and duplicate GA4 or Ads tags. Our Consent Mode v2 guide walks through each one. The banner itself is a design problem too: it has to comply without wrecking the first impression, which we cover in cookie banners that comply without wrecking UX.
If consent loss leaves too big a hole, or GA4 is more than you need, cookieless tools are a reasonable alternative or complement. Our comparison of Plausible, Fathom and GA4 covers the trade-offs.
Should you install GA4 directly or through Google Tag Manager?
Install GA4 through Google Tag Manager if you run ads or expect to add more than one or two tracking tools; install it directly if GA4 is the only tag and your developer will add events in code. Tag Manager adds a layer, but it lets marketers add and change tags without a deploy, and one data-layer event can feed GA4, Google Ads and LinkedIn at once.
Pros
- GTM lets non-developers add tags and triggers without changing site code.
- One data-layer event can feed several platforms, so tracking stays consistent.
- Preview mode makes testing and debugging much easier.
Cons
- Containers grow into tag chaos without naming rules and an owner.
- Every extra tag adds script weight and can hurt performance.
- It's another account and another set of permissions to manage.
Whichever you choose, keep script weight in check. Third-party tags are a common reason marketing sites miss their performance targets, so set a performance budget and review tags each quarter. Our guide to a clean Google Tag Manager setup covers naming, folders and ownership.
How do you see which channels bring demos?
You see which channels bring demos by combining key events with clean source data: the Traffic acquisition report, set to session default channel group, with your demo key event as the column. That only works if campaign links carry consistent UTM parameters and if tools like schedulers and payment pages are listed as unwanted referrals.
- Use one UTM convention. Lowercase, fixed values for source and medium, and a campaign naming pattern everyone follows. See our UTM naming convention.
- Tag every paid and owned link, including newsletters, LinkedIn posts and partner links, but never internal links on your own site.
- Consider a custom channel group to split channels GA4 merges, such as AI assistants or partner referrals.
- Read first-user reports for acquisition and session reports for campaign performance; they answer different questions.
For landing page performance, use the Landing page report with your key events added, or an exploration with landing page and session source as rows. Pages that get traffic but no leads are your redesign candidates; pages that convert well deserve more traffic.
Which GA4 reports should founders check every week?
Founders should check three or four views every week: leads by channel, leads by landing page, the trend in key events against the previous period and anything unusual, like a channel that suddenly drops to zero. That's ten minutes, and it catches broken tracking quickly as well as real changes.
Weekly view | Where to find it | What it tells you |
|---|---|---|
Key events by channel | Traffic acquisition with key event columns | Which channels bring leads |
Key events by landing page | Landing page report or an exploration | Which pages convert visitors |
Week-over-week trend | Any report with a comparison date range | Whether something improved or broke |
Search queries and pages | Search Console reports in GA4 | What people searched before arriving |
Put these into a simple dashboard, in GA4's Library, Looker Studio or your BI tool, so nobody has to rebuild them each week. Our guide to a marketing website KPI dashboard lists the eight metrics we'd include. When the numbers tell you a page underperforms but not why, session recordings and heatmaps can show what visitors actually do.
What breaks a GA4 setup most often?
GA4 setups break most often when the site changes and nobody re-tests tracking: a new form tool, a redesigned template, a consent banner update or a platform migration. The second biggest cause is configuration drift, such as a second tag added by a plugin or a filter switched on without testing.
- Key events stop firing after a form is swapped or an embed changes its messages.
- Duplicate tags from a platform integration plus GTM double-count sessions.
- Self-referrals and payment referrals steal credit for conversions from the real source.
- Consent defaults fire late, so tags run before consent or not at all.
- Cross-domain journeys break when the app or checkout sits on another domain without cross-domain measurement.
- Internal traffic filters are left in testing mode, or exclude everyone because of a wrong IP rule.
When numbers look wrong, start with our troubleshooting guide for GA4 not tracking conversions. It's also worth monitoring the site itself: tracking can't record visits while the site is down, and uptime monitoring tells you before your reports do.
How do you keep GA4 working through a redesign or migration?
Keep GA4 working through a redesign or migration by treating tracking as part of the launch checklist: list every event and key event before the move, rebuild them on the new templates, keep the same event names and test each one on staging and again on launch day. Changing event names mid-year breaks every trend report.
Redirects matter too, because a redirect chain that drops UTM parameters erases campaign attribution, and a missing redirect turns paid traffic into 404s. Our guides to 301 redirects in Webflow and redirects in Framer cover the platform steps, and analytics continuity in a migration covers GA4, GTM and conversion tracking end to end. If the move is a rebuild, our Framer to Next.js migration cost guide shows how that work is usually scoped.
Finally, make sure new page types get tracked as the site grows. When marketers add pages or posts through the CMS, they should inherit the tag and events automatically from templates; our guides to CMS setup for marketing websites and blog setup for a startup website cover how to structure those templates.
