Google Analytics 4 connector

The GA4 connector pulls session-level engagement and conversion data so audit findings carry real business impact. A page with low organic traffic and an audit issue is a lower-priority fix than the same issue on a page that drives thousands of engaged sessions and converts. GA4 is the connector that tells VisibilityIQ which findings move money.

What you’ll need

• A Google account with Viewer access (or higher) to the GA4 property — Viewer is sufficient for read-only pulls.
• The GA4 property that matches your project domain. If you run multiple properties, pick the one whose data stream covers the site you’re auditing.
• A minute to click Sign in with Google and choose the property. As with Search Console, VisibilityIQ owns the Google OAuth application — there’s no Google Cloud project to create and no credentials to paste (see Connectors overview).

Connect

On the Google Analytics 4 card under Settings → Connectors, click Sign in with Google, choose an account with Viewer access, approve the read-only (analytics.readonly) access, then pick your property from the picker that appears. If Google shows a brief “this app isn’t verified” caution during its review of VisibilityIQ, expand Advanced and choose Go to VisibilityIQ — it’s our own application and safe to proceed.

Pick your marketing-site property, not an app or auth property

The most common GA4 mistake is choosing an app, login, or admin-dashboard property instead of the one for the marketing/content site you’re auditing. Accounts often hold several GA4 properties; the wrong one weights your findings with app or auth traffic that has nothing to do with the crawled pages, so priorities look off. If the landing pages in your traffic data don’t match the URLs in your crawl, you picked the wrong property — disconnect and reconnect the right one.

What’s pulled

• Landing page sessions — organic sessions by landing-page URL, daily. This is the primary weighting signal: traffic per page.
• Engaged sessions — sessions where the user interacted meaningfully rather than landing and leaving. Engagement separates pages that draw traffic from pages that actually hold attention.
• Conversions — goal completions attributed to each landing page, so a defect on a high-converting page outranks the same defect on a high-traffic but non-converting one.
• Revenue — for e-commerce properties, revenue attributed to organic landing pages. This lets the engine express finding priority in dollars, not just sessions.

Data syncs daily and normalizes into the internal TrafficObservation model. The raw GA4 schema never reaches scoring or the UI; OAuth tokens are stored encrypted and refreshed transparently, never logged.

How GA4 changes prioritization

Without GA4, a broken internal link is just a broken internal link. With GA4 connected, VisibilityIQ knows whether that link sits on a page earning 10,000 engaged sessions and $40k in monthly revenue — which promotes a Medium technical finding to a High business priority — or on a page no one visits, which keeps it Low. The technical severity doesn’t change; the priority does. This is the difference between a checklist tool and a triage tool.

Data differences from GSC

GSC counts impressions and clicks in Google Search. GA4 counts sessions that arrived at your site. The two numbers legitimately differ:

• Some clicks bounce before the GA4 tag fires.
• GA4 sampling affects smaller properties.
• Privacy tooling and ad blockers suppress a portion of analytics hits.
• Consent-mode and cookie banners can withhold events until the user accepts.

Neither number is “more correct” — they measure different things. Use GSC for what Google’s index and SERP do; use GA4 for what happens after the click. If analytics suppression in your audience is heavy enough to distort weighting, consider the privacy-friendly Plausible connector as a cross-check.

Reconnect

If GA4 shows an Error status, the OAuth token has likely expired or the GA4 permission was revoked:

1. Go to Settings → Connectors.
2. Click Disconnect next to Google Analytics 4.
3. Click Connect and re-authorise with an account that still holds Viewer access.

Historical data is retained across reconnects — you don’t re-pull from scratch.

Next steps

• Connectors overview — how traffic weighting and reconciliation work
• Google Search Console connector — pair sessions with impressions and selected canonical
• Plausible Analytics connector — a privacy-first traffic alternative