Why Dublin businesses lose half their organic traffic in GA4 (and how to get it back)

Why Google Analytics 4 stopped working for SEO in Ireland

Since Universal Analytics was retired in July 2023, marketing teams from IFSC to Sandyford have quietly discovered that GA4 was never designed to answer SEO questions. It exists to log product events and package audiences for Google Ads. Everything Irish marketers actually need to run organic search — sessions per landing page, the exact keyword that drove a visit, behaviour segmented by source, EUR revenue by content — is either broken, hidden behind an anonymisation threshold, or gone entirely.

Any in-house SEO working for a Dublin scale-up like an Intercom, Workday or HubSpot competitor will recognise the pattern. Open GA4, drill into Acquisition → Sessions, and more than half of the organic queries land as the useless placeholder (not provided). Cross-check against Search Console and the totals do not agree. Try to see what someone who arrived on the article “best physiotherapist Ranelagh” actually did — and GA4 hands back an aggregated funnel that refuses to separate channels cleanly. A monthly board report that used to take an hour now eats a full afternoon, and by the time the meeting starts nobody trusts the numbers.

Then there is the legal angle. Ireland’s Data Protection Commission has become one of the most active supervisory authorities in the EU, and the ePrivacy Regulations 2011 (SI 336) require prior consent for any storage on or access to a device. Since the DPC’s 2023 cookie enforcement sweep against Journal.ie, RTÉ, the Irish Times and a slate of retail sites, the “install GA4 and forget it” playbook is indefensible. For a Grafton Street boutique or a South William Street agency, the choice is stark: either invest in a properly configured consent-management platform, or accept that every visitor who taps “Reject All” disappears from your reports.

What Semalt Analytics is and where the data comes from

Semalt Analytics is a data layer for SEO built on three reinforcing sources:

1. Google Search Console API v3 — the newer endpoint that returns up to sixteen months of history with daily granularity, well past the top-1,000 query cap of the UI.
2. Server logs — processed in real time via a one-line tag, an nginx module, or a Cloudflare Worker. This captures the sessions GA4 misses because of blockers, rejected consent or private browsing on iOS 17.
3. Semalt’s own SERP crawl — the rank tracker cross-references your traffic, so every organic hit carries the exact SERP position and features at click time.

That interlock is what nothing else on the Irish market provides in the same shape. GA4 tells you how many sessions arrived. Search Console tells you the average position of a keyword. Semalt tells you, for each individual session, which position the query held at that exact minute, which SERP feature stood above it (People Also Ask, video carousel, Google Business Profile pack for Dublin 2), and how that affected real CTR by device and time of day.

Five things you see in Semalt and never in GA4

1. Real organic traffic per URL, without sampling

GA4 begins sampling the moment you cross two dimensions and pass ten million events per month. For a mid-sized Irish online shop — even one with modest traffic — that threshold is easy to trip once you count scroll, view_item and outbound-click events. Semalt applies no sampling. Every URL sits inside a column-oriented ClickHouse index that resolves queries like “show me the 500 landing pages with the most organic traffic in February compared to the previous year, mobile only, filtered to visitors on Vodafone IE and Three” in under a second.

2. Keywords without (not provided)

The infamous (not provided) does not exist inside Semalt, because the sources are raw Search Console data plus the platform’s own crawl. For every URL you see the fifty keywords driving the most traffic with clicks, impressions, CTR and average position. More importantly, you see the keywords sitting in positions four to ten — the ones a content refresh can push into the top three and double the traffic. This view is called Striking Distance and it is the first thing we open when auditing a new Dublin client. If you want to see it for yourself, sign in to the Semalt dashboard and connect Search Console.

3. Sessions GA4 loses to Irish ad-blockers

In Ireland, desktop ad-blocker adoption sits at roughly 36 % according to GlobalWebIndex Q2 2026 data, and for under-35s on Vodafone, Three or Eir the number climbs to 47 %. Every one of those sessions is invisible to GA4. Semalt’s log-based tracker sees them because it does not depend on JavaScript: the second the server serves the page, the session is counted. Across our Dublin client base we have measured the gap between 16 % and 54 % additional sessions, depending on vertical — higher in B2B SaaS around Barrow Street and the Silicon Docks, lower in traditional bricks-and-mortar retail such as tenants inside Dundrum Town Centre or Blanchardstown Centre.

4. Cross-device journey without Google Signals

GA4 promises cross-device sessions via Google Signals, but only for users signed in to Google on both devices and who have accepted personalised advertising. According to IAB Ireland’s 2025 consent tracker, only 38 % of Irish users click Accept on a standard TCF v2.2 banner. Semalt uses a technique called server-side fingerprint fusion that respects EU GDPR (no ad profiles, no cross-site behavioural graphs) and still shows that someone read your article on mobile on the Luas Green Line and bought on desktop later that evening from their home in Ranelagh.

5. Organic revenue per keyword, in real EUR

The crown jewel: connect your CRM or shop (WooCommerce, Shopify, Magento 2, BigCommerce, HubSpot, Salesforce, Pipedrive) via webhook and Semalt links every order to the first organic keyword that brought the user. You can see that “chartered accountant Dublin 4” produced €31,600 in organic revenue last month, and that a fatter head keyword generated €0. With that in hand, you stop chasing vanity metrics and prioritise content by actual EUR revenue.

Case study: Temple Bar restaurant group, 22,000 sessions/month

A client running four Temple Bar restaurants — the kind of independent group with covers to fill on a Six Nations Saturday and a St Patrick’s Day festival week — came to us in February 2026 with this picture:

• GA4 reported 22,400 organic sessions and 74 online bookings for the month (0.33 % CVR).
• Search Console showed 51,200 clicks in the same window.
• The gap — more than double — had no internal explanation. The team blamed GTM, Cloudflare’s bot fight mode, and the CookieYes banner in rotation across the four sites.

We connected Semalt Analytics in fifteen minutes. First numbers landed the next morning:

Real organic sessions: 41,800 (87 % more than GA4). Bookings correctly attributed to first organic touch: 193 (2.6×). Verified organic pipeline value based on average cover: €214,000 versus the €50,000 the owners had been estimating — a difference of €164,000 that was invisible in the monthly report.

The most valuable insight arrived when we cross-referenced keywords with pipeline value: eight long-tail terms (each between 110 and 590 searches/month, all mentioning Temple Bar or specific cuisines) drove 66 % of pipeline, while the head keyword “restaurants Dublin” with 18,100 searches/month drove only 4 % of bookings. Content strategy was re-prioritised inside a fortnight. By May, organic pipeline was up 76 % and the marketing manager was quietly promoted.

EU GDPR, ePrivacy and the DPC position on Google Analytics

The reason so many Dublin and Cork agencies are switching to Semalt is legal defensibility. The Irish ePrivacy Regulations 2011 (SI 336) require prior consent for any storage of information on, or access to information from, a user’s device — that covers cookies, localStorage, IndexedDB and similar. Server-log tracking accesses none of that. It uses only the information the browser sends anyway as part of the HTTP request (IP, user-agent, referrer). These are processed server-side under Article 6(1)(f) EU GDPR, with IP truncated within milliseconds (last octet removed) and never persisted.

This gives Dublin marketers a rare advantage: Semalt Analytics counts users who reject the banner too. For a mid-sized Irish shop with a 42 % consent rate, that alone represents a 138 % more accurate reach measurement, without straying into DPC enforcement territory. Semalt provides an EU-law DPA that can be signed with one click per account, plus a TOM document aligned with the DPC’s 2025 accountability framework and ENISA hardening guidance.

Setup in under fifteen minutes

Semalt Analytics vs. GA4 vs. Matomo vs. Search Console

More in this series: Ship SEO changes in 3 minutes, not 3 weeks, Watch your Dublin competitors quietly, Why keyword volume lies in Ireland.

FAQ for Dublin marketers

Does Semalt replace GA4 completely?

If your focus is purely SEO and content, yes. If you also run Google Ads and need to export audiences to Google, keep GA4 in parallel — Semalt does not replace the native Ads connector. For eight in ten Dublin clients we keep GA4 as an Ads source and use Semalt as the SEO source of truth. Connect both from the Semalt dashboard.

Is it compliant with EU GDPR and the Irish ePrivacy Regulations?

Yes. Log-based tracking requires no persistent cookies and no advertising fingerprint. Server-side fusion works on pseudonymised data, and sessions anonymise after 26 months by default (configurable down to six). Semalt provides an EU-law DPA, a TOM document and a DPIA template aligned with DPC guidance.

Does it run on typical Irish stacks?

Yes. The tag exists as a WordPress plugin, a Shopify app, an Umbraco package (still widely used by Irish councils and Section 38/39 charities), a Magento 2 module and SDKs for Node.js, PHP, Symfony, Laravel and .NET. For cloud-native setups it is two lines in a Cloudflare Worker deployed from your Blacknight or Digiweb environment.

How fast do you see value?

Historical Search Console data is visible in five minutes. Live tracking shows full data after 24 hours. The Striking Distance insight (keywords in positions four to ten) is actionable on day one.

Does it work for small websites?

Yes. A single-location Rathmines cafe with 1,800 sessions/month uses Semalt the same way an IFSC B2B portal with two million does. For small sites the value is in seeing which article is about to reach page one and optimising it before Google cements the position.

Does it integrate with Semalt AutoSEO?

Yes — that is the real synergy. Analytics identifies URLs with striking-distance keywords, and AutoSEO executes the fixes on those URLs without a developer in the loop. Details in the AutoSEO guide.