How to Set Up GA4, Step by Step
Creating a GA4 property takes a few clicks. Setting it up so the numbers it produces are trustworthy takes a bit more - and most of the difference is a handful of settings people skip on day one.
Before You Start
You'll need a Google account with access to (or permission to create) a Google Analytics account, and either direct access to your site's code or a tag manager (Google Tag Manager or your platform's built-in tag settings). If you're migrating from Universal Analytics rather than starting fresh, see the implementation & migration guide instead - the sequence is different when historical continuity matters.
The Setup Sequence
Create the GA4 property and data stream
In Google Analytics admin, create a new property, then add a web data stream for your domain. This generates your Measurement ID (format G-XXXXXXX), which every install method below needs.
Install the tracking code
Either paste the gtag.js snippet directly into your site's <head>, use your platform's native GA4 integration (Shopify, WordPress plugins, etc.), or deploy it through Google Tag Manager if you're already using GTM for other tags.
Confirm enhanced measurement settings
GA4 auto-tracks page views, scrolls, outbound clicks, and a few other events by default. Review which of these are actually useful for your site and turn off any that create noise (e.g. file-download tracking on a site with no downloadable files).
Mark your real conversions as key events
A key event (formerly "conversion" in GA4's own terminology) is what turns raw event data into a business metric. Decide what a conversion actually means for your site - a purchase, a form submission, a signup - and mark those events, not every event GA4 happens to collect.
Exclude internal and developer traffic
Set up an internal traffic rule (by IP or a custom parameter) so your own team's testing and browsing doesn't get counted as real visitor activity. This is one of the most commonly skipped steps and one of the most common causes of inflated numbers.
Set data retention and configure consent
Choose your event data retention window (2 or 14 months), and if you operate in a region requiring cookie/tracking consent, configure Google's Consent Mode so measurement respects the visitor's choice rather than firing regardless.
Test with DebugView before trusting the reports
Turn on debug mode (via a browser extension, a URL parameter, or GTM preview mode) and click through your own site while watching DebugView. Confirm events fire once, parameters populate correctly, and key events register - before you start making decisions from the standard reports.
Common Setup Mistakes
| Mistake | Effect |
|---|---|
| Skipping internal traffic exclusion | Inflated session and conversion counts from your own team's activity |
| Marking every event as a key event | Makes it impossible to tell which number actually represents revenue-driving action |
| Installing GA4 twice (e.g. via plugin and manual snippet) | Duplicate page views and doubled event counts |
| Never opening DebugView before launch | Broken tracking often isn't discovered until someone questions a number weeks later |
| Ignoring consent mode where required | Compliance exposure, and a measurement gap that looks like a traffic drop |
Hypothesis, not a guarantee: the impact of any single mistake above depends on your site's traffic and event volume - we're describing the failure mode, not predicting a specific number for your setup.
If your events are deployed through Google Tag Manager, container-level setup and QA is covered separately at gtm.webclat.com.
Frequently Asked Questions
How long does it take to set up GA4?
Creating the property and data stream itself takes minutes. Getting the setup right - key events, internal traffic exclusion, cross-domain measurement if needed, and consent configuration - typically takes longer, from a few hours to a couple of days depending on how many of those pieces apply to your site.
Do I need Google Tag Manager to set up GA4?
No. GA4 can be installed with a direct gtag.js snippet or through most website platforms' native integrations. GTM is optional but common because it makes managing multiple tags and custom events easier without editing site code each time - see gtm.webclat.com for GTM-specific setup guidance.
What should I configure immediately after creating a GA4 property?
At minimum: mark your real conversions as key events, exclude internal and developer traffic, set the data retention window, and confirm the timezone and currency match your business. These four are the most commonly skipped steps and the most common source of early data-quality complaints.
How do I know if GA4 is tracking correctly after setup?
Use DebugView in GA4 alongside Tag Assistant (or GTM's preview mode) to watch events arrive in real time as you click through your own site. This confirms events fire, parameters are populated, and nothing is duplicated - before you rely on the standard reports, which can take up to 24-48 hours to populate fully.
Want This Done For You, Correctly, the First Time?
We set up GA4 properties daily and validate every one against DebugView before handover.
Get GA4 Set Up ProperlyGet GA4 Set Up Properly
Tell us about your site and platform and we'll scope the setup.