Google Analytics 4 Setup for Charities (Without the Pain)

Most charities migrated from Universal Analytics to GA4 in a hurry in 2023, ticked the box, and never went back. The result is a property full of default settings, broken events, and reports that nobody opens. GA4 is a perfectly good tool. It just needs about a day of intentional configuration to start answering useful questions for a charity.

What follows is the minimum viable GA4 setup for a typical UK charity site: enough to report on supporter behaviour, donation funnels, and content performance without drowning trustees in noise.

The questions GA4 should be answering

Before configuring anything, agree the questions. The point of GA4 is not to track everything. It is to answer a small number of decisions clearly.

• How many people are reaching our donation page, and how many complete?
• Which channels send the supporters who actually convert?
• Which content drives email signups and donations versus which just gets traffic?
• Are our campaigns producing measurable lift in giving?
• Is our site experience getting better or worse for the people who matter?

Five questions. Everything in the setup below exists to answer them.

Step 1: Get the property and stream right

One property per charity, not one per site

Use a single GA4 property for the charity, with separate data streams for the main site, any subdomain campaigns, and the donation platform if it lives on a different domain. This lets you see the full supporter journey rather than three disconnected views.

Cross-domain measurement

If your donation form lives on a third-party platform (Stripe Checkout, JustGiving, Donorfy Forms, etc.), configure cross-domain tracking so the donation page is not counted as a new session. This is the single most common GA4 mistake on charity sites.

Data retention

Default is two months. Change it to fourteen months. You will want year-on-year comparisons, and the default makes those impossible.

Step 2: Configure the events that matter

GA4 tracks a lot of events automatically. Most of them are noise for a charity. The ones worth configuring properly are:

donation_started

Fired when a supporter lands on the donation page or clicks a donate CTA. Include amount if pre-selected, and source if known. This is the top of your charitable funnel.

donation_completed

Fired on the thank-you page after successful payment. Include amount and frequency (single, monthly). This is the only event your fundraising team actually cares about.

email_signup

Fired on newsletter signup confirmation. Tag the source form so you know which page produced the signup.

content_engagement

Fire after 60 seconds and 75 percent scroll on long-form content. Filters out the bounces and shows you which articles actually held attention.

outbound_resource

Fire when a supporter downloads a PDF or clicks an external campaign resource. Otherwise these high-intent actions are invisible.

Configure these in Google Tag Manager rather than directly in GA4. GTM gives you a clean audit trail and lets non-developers add new tags safely.

Step 3: Set up conversions

Mark `donation_completed` and `email_signup` as Key Events in GA4. This switches on the conversion reports and lets you see which channels and content drive the outcomes that matter, not just the traffic.

Resist the temptation to mark every event as a conversion. If everything is a conversion, nothing is.

Step 4: Channel grouping and UTMs

Tag every campaign

Email, paid social, paid search, partner placements: all need UTM parameters. Without them, GA4 cannot attribute supporters to the campaign that brought them in, and your campaign reporting becomes guesswork.

Standardise the taxonomy

Decide on source, medium and campaign naming conventions and document them in a single shared file. Common patterns: medium for email is `email`, for paid social is `paid_social`, for Google Ads is `cpc`. Consistency beats cleverness.

Custom channel groups

Create a custom channel group that separates paid social by platform, separates owned email from third-party email, and surfaces partner traffic distinctly. The default channel grouping bundles too much.

Step 5: Consent Mode v2

Without proper consent, you are both losing data and exposed under PECR. Implement Google Consent Mode v2 with a CMP (Cookiebot, Iubenda, OneTrust). This gives you modelled conversions for visitors who decline cookies, recovering a meaningful chunk of the data you would otherwise lose.

Step 6: One dashboard, not ten

Build a single Looker Studio dashboard pulling from GA4 with four sections:

1. Supporter funnel: visits, donation page views, donations started, donations completed, conversion rate by channel.
1. Content performance: top pages by engaged sessions, signups produced, donations produced.
1. Campaigns: active UTMs, sessions, key events, cost where available.
1. Site health: page speed, mobile share, top error pages.

Share the dashboard read-only with trustees and the senior team. Update it monthly with a two-paragraph narrative. That single dashboard is more valuable than every GA4 report combined.

Step 7: A quarterly review, not a daily watch

GA4 rewards monthly and quarterly review rhythms. Daily watching produces noise and bad decisions. Set a recurring 60-minute slot once a month to interrogate the dashboard, and a 90-minute slot once a quarter to revisit the configuration itself.

What you do not need

GA4 360

Almost no UK charity needs this. The free version handles charity-scale data comfortably.

BigQuery integration

Useful for very large charities with mature data teams. For everyone else it adds complexity and cost without proportionate benefit.

Custom dimensions for everything

Tempting and almost always counterproductive. Stick to the events above unless a specific question requires more.

GA4 does not need to be impressive. It needs to answer five questions cleanly every month, and stop the fundraising team guessing about what works.

The week-one checklist

1. Confirm one GA4 property covers the whole charity, with cross-domain set up.
1. Set data retention to 14 months.
1. Configure five core events in GTM: donation_started, donation_completed, email_signup, content_engagement, outbound_resource.
1. Mark donation_completed and email_signup as Key Events.
1. Implement Consent Mode v2 with a proper CMP.
1. Build a single Looker Studio dashboard with four sections.
1. Book the monthly review slot in the senior team calendar.

A week of focused work produces a GA4 setup that earns its keep for years. Most charities will recover the time the first month they stop arguing about what the numbers mean.

Further reading

Choosing an Email Platform for Charities in 2026 | Charity Attribution Without Overengineering | Power BI for Charity Reporting (Without a Data Team)