GA4 for SEO agencies
Connect your clients' organic search performance to conversions and revenue
Casient reads Organic Search data from Google Analytics 4 — sessions, a key event you choose, and revenue — next to Search Console clicks and impressions. When a client's organic performance turns into a business outcome, you get a result you can show, with each source kept separate and no causal claims.
Read-only analytics.readonly access · Organic Search only · Aggregated data, never visitor-level
Google Analytics 4 · Organic Search
Organic lead growth
Lead form submissions
74 → 129
+74%
- Organic sessions
- +41%
- Period
- 90 days
Casient uses completed Google Analytics data through a stable date. "Lead form submissions" is a label you provide for the GA4 key event, not a result Casient verifies.
What Casient reads from GA4
One channel, three metrics, aggregated. Everything else in your analytics account is left alone.
Organic Search sessions
Filtered to the Organic Search channel group. Not all traffic, not paid search, not social or referral — the sessions your SEO work is responsible for.
One key event you choose
Pick a single GA4 key event per property — a lead form, a demo request, a signup. Casient keeps the exact technical event name and lets you add a readable label for the client.
Revenue, in the property's currency
Where GA4 records revenue for Organic Search, Casient reports it in the property's own currency. It never converts currencies and never calls revenue "sales" unless the metric supports it.
It does not read visitor-level data, audiences, advertising identifiers, or any other channel. See the privacy policy for exactly what is processed.
Three kinds of result, ranked by what they mean
Casient creates one consolidated result per property and period — not a card per metric — and leads with the strongest signal.
Qualified growth in Organic Search revenue or in the key event, with organic sessions shown as context. These are prioritised above traffic-only results — this is the number a client's finance team cares about.
Organic Search sessions grew with enough volume to be worth publishing. Eligible for a case study, but never presented as "business impact" on its own.
A big percentage move on a smaller number. Visible in your results, never featured, never emailed automatically, and it asks for an explicit confirmation before you draft a case study from it.
If a relevant metric moved the other way in the same period, Casient shows it plainly in the review rather than hiding it. More on the method in connecting SEO to business outcomes.
How it fits with Search Console
01
Connect GA4
A separate, read-only connection from your Search Console one. A problem with either never disconnects the other.
02
Map property to property
Link one GA4 property to one Search Console property — the same client site. Mapping a GA4 property does not use a plan property slot.
03
Casient compares stable data
Every few days, 90 days against the prior 90, ending at least two weeks ago in the property's timezone. Sampled or incomplete data is skipped, not published.
04
Publish, sources separate
Turn a result into a case study. GA4 and Search Console figures appear as distinct blocks, locked when published.
Already using Casient for Search Console alerts? GA4 business-impact results flow into the same portfolio monitoring — the monthly summary now separates SEO opportunities from business-impact ones.
Built to hold up in front of a client
Sources stay separate. GA4 Organic Search and Search Console are always shown as their own blocks on a case study. Casient never merges or adds their numbers.
Stable by design. Comparisons only use completed data through a visible date. The figure behind a published result does not move afterwards.
No causal language. Casient reports what changed over a defined period. It does not claim your agency caused it, and it does not claim sessions caused conversions.
Verified vs context. The metrics are first-party Google data. The key-event label and any narrative you add are marked as agency-supplied context, not verified claims.
Locked on publish. Every metric shown on a public case study is frozen into an immutable snapshot. A later data change creates a new revision you publish deliberately — nothing updates silently.
Read more
Connecting SEO to business outcomes
The method for reporting SEO impact without overclaiming causation.
Search Console vs GA4 for SEO
What each source actually measures, and why agencies need both.
Building an organic search report in GA4
Sessions, key events and revenue for the Organic Search channel, and the pitfalls.
Questions agencies ask
- Does connecting GA4 give Casient access to my whole analytics account?
- No. Casient requests a separate read-only scope and only ever queries aggregated Organic Search reporting for the properties you map — session counts, key-event counts and revenue totals. It does not read visitor-level data, audiences or advertising identifiers, and it cannot change anything in GA4.
- Why does Casient not use the most recent GA4 data?
- Analytics figures for the last two weeks are still settling. Casient only compares completed data through a visible date, so the numbers behind a result do not change once you have reviewed it. Every result and case study shows that date.
- Does Casient claim my agency caused the growth?
- No. It verifies the source metrics and the comparison period, and keeps your context separate from the figures. It never states that your work caused a change, and it never says more sessions caused more conversions or revenue.
- Can a GA4 result become a case study without Search Console?
- Yes. A qualifying Organic Search result can be published on its own. If the mapped Search Console property has metrics for the exact same period, they are offered as an optional second source block — always shown separately.
- Which plans include the GA4 Business Impact Finder?
- The GA4 integration is on the Agency plan and the 14-day trial. Search Console monitoring is on every plan.