New Business Websites logo
HomeOur WorkServicesPricingHow It WorksBlogAboutContact
Request a Website Plan WhatsApp Niall
Back to blog

Google Analytics 4 Basics: Realtime Checks and GDPR for Irish SMEs

Small business owner checking website analytics

Google Analytics 4 is Google’s event-based analytics property that tracks both websites and apps in one place. If you are starting from scratch, the first practical step is to create a GA4 property, add a web data stream, switch on enhanced measurement and confirm data is arriving using Realtime or DebugView.

TL;DR:

  • Set the property’s time zone and currency carefully; neither can be changed retroactively, and data may take 30 minutes to appear after tag installation.
  • Mark only three to five business outcomes, such as completed bookings or purchases, as key events; tracking low value actions can dilute conversion reports.
  • For Irish and wider EU audiences, do not load GA4 before informed consent, and provide an equally clear way to decline or later withdraw permission.
  • Use Google Tag Manager if you expect to add advertising or chat tags later; a CMS field is adequate for a simple site.
  • When visitors decline consent, GA4 reports may use statistical modelling, but BigQuery exports contain only recorded events, so totals may not match exactly.
Newbusinesswebsites
Build a Website That Supports Your Goals
NewBusinessWebsites.ie creates practical websites for Irish businesses, with enquiry features designed to help turn visitors into potential customers.
Explore website services

Table of Contents

What Google Analytics 4 is and how it differs from Universal Analytics

GA4 replaced Universal Analytics with a fundamentally different way of recording activity. Instead of grouping visits into sessions first, GA4 records everything as an event: a page load, a scroll, a click, a purchase. Sessions still exist as a way of grouping events together, but the event is the basic unit, and that changes how reports are built and read.

The practical effect for a beginner is that GA4 reports feel less rigid than the old Universal Analytics screens. You are not stuck with predefined session metrics; you can look at any event and the parameters attached to it. GA4 collects event-based data from websites and apps, supports cookieless measurement and uses predictive metrics, and tailors its default reports depending on how the property is set up.

A few other differences matter early on:

  • GA4 can measure a website and a mobile app inside a single property, which Universal Analytics never did well.
  • It relies less on third-party cookies and fills gaps with statistical modelling when consent or tracking signals are missing.
  • Universal Analytics stopped processing standard property data from July 1, 2023, so any site still quoting UA numbers is looking at historical figures, not live ones.
  • Google can export UA history and offers a GA4 Setup Assistant to carry over key configurations.

If your business still has an old Universal Analytics account, there is nothing to migrate forward technically: UA cannot be switched back on. The practical task is simply making sure a GA4 property exists and is collecting data going forward.

Step-by-step setup: property, data stream and tag installation

Setting up GA4 is mostly a sequence of short forms. None of the individual steps are difficult, but missing one (usually the tag installation) is the most common reason sites show no data weeks later.

  1. Go to analytics.google.com and sign in with the Google account you want to manage the property with, then select “Start measuring” if this is a new account.
  2. Create an account (this is the top-level container for your business) and give it a sensible name, such as your company name.
  3. Create a GA4 property underneath that account, choosing your reporting time zone and currency carefully, since these cannot be changed retroactively without affecting historical consistency.
  4. Add a web data stream and enter your website’s URL and a stream name.
  5. Leave enhanced measurement switched on. This auto-collects common events like scrolls, outbound clicks and file downloads without extra tagging, according to Google’s setup guidance.
  6. Copy the Measurement ID shown for the stream, which starts with “G-”.
  7. Install the tag using whichever method suits your site: paste the Measurement ID into a CMS analytics field (WordPress plugins and Shopify both offer one), add the gtag.js snippet directly to your site’s header, or configure a GA4 tag inside Google Tag Manager if you already use it.
  8. If a property was created automatically for you (Google does this for some accounts), open it and check the data stream and Measurement ID match what is actually installed on your site, rather than assuming it is correct.
  9. Open the Realtime report and browse your own site in another tab. You should see yourself as an active user within a few minutes.
  10. If nothing appears, wait: Google notes that data collection can take up to 30 minutes to fully appear, even when the tag is firing correctly.

Pro Tip: Keep a plain-text note of your Measurement ID, account name and property name somewhere outside Analytics itself; it saves time when a developer or a third party needs to confirm installation later.

Google Tag Manager is worth the extra ten minutes of setup if you expect to add more tracking later (ads conversion tags, Hotjar, a chat widget), because every future addition after that is a few clicks rather than another code edit. For a simple brochure site with no immediate plans to add more scripts, pasting the Measurement ID directly or using a CMS plugin field is perfectly adequate and slightly less to maintain.

One thing worth clarifying before you move on: enhanced measurement is not the same as custom event tracking. More specific actions for your business (a quote request, a WhatsApp click, a booking confirmation) needs its own event, which we cover in the conversions section below.

GA4’s data model: events, parameters and user properties

Everything in GA4 reporting traces back to four building blocks, and understanding them makes every report screen easier to read.

An event is a single recorded action. page_view, click, scroll and purchase are standard examples; enhanced measurement generates most of these for you automatically.

Event parameters add context to an event. A purchase event typically carries parameters like value, currency and item_id, which is what lets you later see revenue by product rather than just a count of purchases.

User properties describe the person rather than the action: things like device category, language or a custom attribute you define (such as “customer type”). They persist across a session and across visits, unlike event parameters, which only describe a single moment.

This distinction explains a question beginners often get stuck on: why does “Active Users” not match “Total Users” in a report? Active Users counts people who triggered at least one event within the selected date range. Total Users is a running count of everyone who has ever been recorded, including people who have not returned recently. For most day-to-day reporting, Active Users is the more useful number.

Practical points worth remembering:

  • Enhanced measurement auto-collects the common events, so you rarely need to build page_view or scroll yourself.
  • Custom events are for anything specific to your business goals: a quote form submission, a click on a phone number, a newsletter signup.
  • Keep event names short, consistent and lower-case with underscores (contact_form_submit, not “Contact Form Submission!”), which matters later when building Explorations or connecting to Google Ads.
  • A parameter like value only produces meaningful revenue reporting when it is actually populated with a real number, not left blank.

Getting this model straight early avoids a lot of confusion later: most “GA4 doesn’t show the right numbers” complaints trace back to a misunderstanding of what an event, a parameter and a user property each actually represent.

Which GA4 reports should a beginner check first?

You do not need to learn every report in GA4 to get useful answers. Five sections cover almost everything a small business needs in the first few months.

  • Realtime shows who is on your site right now, which pages they are viewing and which events are firing, making it the fastest way to confirm tracking is working after any change.
  • Acquisition breaks traffic down by source and medium, showing whether visitors arrived through organic search, paid ads, social or direct traffic, and how each channel compares.
  • Engagement covers events, pages and screens, and average engagement time, replacing the old “bounce rate” concept with a more useful picture of what people actually do once they land.
  • Monetization tracks purchases and revenue where ecommerce tracking is configured, useful for any site that sells directly online.
  • Explorations is a free-form report builder for ad hoc questions, such as comparing conversion rates across two landing pages or segmenting by device type.

A simple first habit: open Realtime immediately after any website change to check the tag still fires, then check Acquisition and Engagement once a week to see where visitors are coming from and what they are doing once they arrive. DebugView, covered in more detail below, displays events logged in the last 60 seconds, which makes it the natural companion to Realtime when something looks off.

A good first Exploration to try: a free-form table comparing Sessions and Engagement Rate by Landing Page, which quickly shows which pages hold attention and which ones visitors leave immediately. This kind of simple comparison answers a question that the standard Engagement report cannot show on its own, and it is a good introduction to how flexible Explorations can be once you are comfortable with the basic reports.

Measuring conversions: choosing and marking key events

Not every event deserves to be treated as a conversion. The goal is to pick the handful of actions that actually represent business value, then mark those specifically so reports and Google Ads can use them.

A key event, in GA4’s terms, is any event that represents a meaningful outcome: a form submission, a phone number click, a completed booking or a purchase. Marking too many events as key events dilutes the signal and makes conversion reports harder to interpret.

To mark an event as a key event, go to Admin, then Events, find the event in the list and toggle it on as a key event. Once marked, it appears in conversion-focused reports and becomes available to import into Google Ads if the accounts are linked.

  • contact_form_submit for enquiry form completions.
  • phone_click for clicks on a tel: link.
  • booking_confirmed for completed bookings or appointments.
  • purchase for completed transactions, including the value and currency parameters.

Pro Tip: Start with three to five key events maximum. It is far easier to add another one later than to untangle a conversions report cluttered with a dozen low-value actions.

Sensible, consistent naming matters more than it looks: an event called Button Click 2 tells you nothing six months from now, while quote_request_submit is self-explanatory in every report it appears in.

Verifying your setup: Realtime, DebugView and common fixes

Checking that data is actually arriving correctly takes a few minutes and saves weeks of guessing later.

  1. Open the Realtime report and look at “Event count by Event name” while browsing your own site, confirming the events you expect (page_view, scroll, your custom events) appear within a couple of minutes.
  2. Enable DebugView by installing the Tag Assistant Companion extension or adding a debug_mode parameter to your tag, which lets you inspect events and their parameters as they fire, updated roughly every 60 seconds.
  3. Use DebugView to select your specific device or browser session so you are not reading mixed traffic from other visitors.
  4. If an event does not appear, check the Measurement ID matches what is in the GA4 stream, preview the tag in Google Tag Manager if that is how it was installed, check the browser console for script errors, and confirm a consent banner is not silently blocking the analytics script.
  5. Exclude your own visits and any developer or staff traffic using an IP filter or the “internal traffic” rule in Admin, so testing activity does not distort real reports.

Most setup problems trace back to one of these four causes: a wrong or duplicated Measurement ID, a tag that never fires because of a Tag Manager trigger error, a browser extension blocking analytics scripts during testing, or a consent tool blocking the tag before a visitor accepts cookies.

Analytics cookies are not automatically exempt from consent requirements in Ireland or the wider EU. Irish Data Protection Commission guidance states that analytics cookies generally require informed, specific consent before they are set, and that consent cannot be bundled into an “all or nothing” choice.

Consent choice controlling analytics cookie setting

Analytics cookies generally need informed, affirmative consent under Irish ePrivacy rules, and that same DPC guidance confirms that withdrawing or changing consent must be just as easy as giving it in the first place. In practice, that rules out pre-ticked consent boxes and cookie banners with only an “Accept” button and no equally visible way to decline or adjust preferences.

Points worth building into any GA4 setup from day one:

  • Do not load the GA4 tag (or fire it through Tag Manager) until a visitor has given consent, not after.
  • Give visitors a visible, working way to withdraw or change their consent choice at any time, not just on first visit.
  • Avoid “all or nothing” cookie banners: analytics consent should be separable from strictly necessary cookies.
  • Consider Google’s Consent Mode, which adjusts how the GA4 tag behaves based on a visitor’s consent signal and allows some modelled measurement without full tracking.
  • Keep a simple record of what your cookie banner asks for and when it was last updated, so you can show how consent is actually being collected if ever questioned.

When consent is declined, GA4 does not simply lose that visitor entirely: standard reports can fill some of the gap using statistical modelling, though raw exports such as BigQuery contain only the actual recorded events and will not reconcile exactly with modelled report totals. For most small business sites, the safer and simpler route is a clear, compliant consent banner and accepting that declined visitors will not appear in reports at all.

Practical next steps and where to learn more

Once the basics are in place, a short weekly routine keeps GA4 useful rather than ignored.

  • Confirm the tag is still firing correctly after any website or CMS update, since plugin changes are a common cause of silent tracking failures.
  • Settle on three to five key events that genuinely matter to the business and resist the urge to track everything.
  • Check Realtime and Acquisition weekly rather than letting months pass between logins.
  • Link Google Ads to GA4 if you run paid campaigns, so conversion data flows both ways.
  • Work through Google’s own Analytics Academy courses and the official GA4 setup documentation for anything beyond the basics covered here.
  • Consider BigQuery export only once you need raw, unmodelled data for custom analysis; most small business sites never need it.

If the weekly routine above feels like one more task competing for attention alongside running the actual business, that is usually the point where a managed setup or a periodic check-in from someone else makes more sense than trying to keep it all in your own head.

What usually goes wrong when beginners set up GA4

The same handful of mistakes come up repeatedly: the Measurement ID pasted into the wrong CMS field, a Google Tag Manager trigger that fires on the wrong page, and consent banners that block the tag entirely because nobody tested what happens after a visitor clicks “Accept”.

A short onboarding checklist, covering tag placement, consent configuration and a Realtime check immediately after launch, catches most of these before they cost weeks of missing data. A quick site audit against that checklist, done once at launch and again after any major redesign, tends to be far more effective than troubleshooting after the fact once a client notices three months of empty reports.

Hands-on support matters most in the gap between “the tag is technically installed” and “the data is actually trustworthy”. That gap is where most beginner frustration with GA4 comes from, not from the reports themselves.

— niall

How we help with GA4 setup and ongoing website care

We include GA4 tracking in new websites we design, so tag installation, consent configuration and key event tracking are handled correctly from launch rather than bolted on afterwards. For an existing site, we can check the current setup, fix tag or consent issues, and configure the key events that matter for your business: enquiry forms, phone clicks, bookings or online sales.

Newbusinesswebsites

Our ongoing Website Care plans include monitoring and minor updates, which covers checking that analytics tracking keeps working as your site changes over time rather than quietly breaking after a plugin update.

  • Tag installation and verification as part of every new website build.
  • Consent banner setup that meets Irish requirements for analytics cookies.
  • Key event tracking configured for the specific actions your business needs to measure.
  • Ongoing monitoring through our Website Care plans, starting at €29 per month.

If you already have a website and are not sure whether GA4 is tracking correctly, get in touch for a straightforward check, or browse our website and local SEO services to see what a full setup includes.

FAQ

How do I set up Google Analytics 4?

Sign in at analytics.google.com, create an account and a GA4 property, then add a web data stream for your site. Copy the Measurement ID and install it through your CMS, a gtag.js snippet, or Google Tag Manager, then confirm it is working in the Realtime report.

Is Google Analytics 4 hard to learn?

The basic setup (creating a property, adding a data stream and installing the tag) is straightforward and can be done in under an hour by following Google’s own guidance. The reporting side takes longer to feel comfortable with, mainly because the event-based model is unfamiliar to anyone used to the older Universal Analytics reports.

What is the current version of Google Analytics?

Google Analytics 4 is the current version, having replaced Universal Analytics after standard UA properties stopped processing data from July 1, 2023. There is no newer version beyond GA4 at present.

How much does Google Analytics 4 cost to use?

The standard version of Google Analytics 4 is free to set up and use for most websites and small businesses. A paid enterprise tier exists for very high-traffic sites, but it is not something a typical small business website would need.

Sources

Back to blog
WhatsApp