Most nonprofits open Google Analytics 4 (GA4), see forty-odd reports, and close the tab. You need six: traffic acquisition, landing pages, a donation funnel exploration, key events, pages and screens, and one free-form exploration you build once. The rest is diagnostic noise until those six are clean.
The short version
- GA4 replaced the old "conversions" label with "key events," so your donation and signup tracking now lives under Key events, not where Universal Analytics used to put it.
- The single most useful report for fundraising is a Funnel exploration built in the Explore section, which shows exactly where donors abandon your giving flow.
- Board reporting needs three numbers, not thirty: sessions by channel, donation-page conversion rate, and key-event completions.
- If a report does not change a decision you will actually make this quarter, ignore it. That rule alone kills most of GA4's surface area.
Why GA4 feels like too much for a small team
GA4 is an event model wearing a reporting suit, and that is the whole source of the confusion. When Google retired Universal Analytics in July 2023, it did not just rename the product. It swapped a pageview-and-session model for one where every scroll, click, and form submit is an "event," and reports are just saved views on top of that firehose. For a five-person nonprofit with no analyst, that means the default interface shows you dozens of reports optimized for e-commerce and app teams, and almost none of them are labeled "did we raise money."
So the work is not learning GA4. The work is deciding what you refuse to look at. I have set this up for a state association and a legal-services nonprofit, and in both cases the winning move was the same: pick six reports, put them on one bookmarked page, and treat everything else as something you open only when a number looks wrong.
The six reports that earn their place
Each of these answers a question a program director or board member actually asks. Skip the ones that do not map to a decision.
1. Traffic acquisition: where did people come from
Path: Reports, then Acquisition, then Traffic acquisition. This is your channel breakdown, organic search versus email versus paid versus direct. It answers the first board question every time: is our audience growing, and from where. If your email channel drives sessions but not key events, your newsletter is busy, not effective.
2. Landing page: which entry pages pull donors
Path: Reports, then Engagement, then Landing page. This tells you which page someone arrived on before they converted, not just which page got traffic. For most nonprofits the highest-intent landing pages are not the homepage. They are a specific program page, a campaign URL, or the donate page linked from an appeal email. Fund the pages that start real sessions.
3. Funnel exploration: where the giving flow leaks
Path: Explore, then the Funnel exploration template. According to Google's own documentation, funnel exploration lets you "visualize the steps your users take to complete a task and quickly see how well they are succeeding or failing at each step," across up to 10 sequential steps. This is the report I build first for any fundraising client. Define your steps, donate page view, amount selected, donor details, payment, confirmation, and GA4 shows you the exact percentage that drops at each one. That is where the money is hiding.
4. Key events: did the thing you care about actually fire
Path: Reports, then Engagement, then Key events. GA4 renamed "conversions" to "key events," which trips up anyone coming from the old interface. A key event is any event you have flagged as mattering, a completed donation, a membership signup, a newsletter subscribe. If this report shows zero, your tracking is broken, not your fundraising. Verify it before you trust any other number.
5. Pages and screens: what content is doing work
Path: Reports, then Engagement, then Pages and screens. This is your content performance view. Sort by engagement, not raw views. A blog post with high views and a two-second average engagement time is a bounce machine. A program page with fewer views but long engagement and downstream key events is quietly building your pipeline. Feed the second kind.
6. One saved free-form exploration you build once
Path: Explore, then Blank, then Free form. Build a single table segmented by whatever matters to your mission, first-time versus returning donors, or traffic by campaign against key-event completions. Save it. This is the one custom report worth the setup time, because it answers the question your default reports cannot: not how many, but who.
The 40 you can ignore, for now
Realtime is a dopamine hit, not a report. Watching live users on GivingTuesday feels productive and changes nothing. The demographic detail reports, the tech and browser breakdowns, the granular events list, the user acquisition versus traffic acquisition distinction most teams never need to untangle, all of it is diagnostic. You open those reports when one of your six shows something strange, and not before. Optimizing your GA4 setup should follow the same logic as conversion work on the site itself: measure what leads to a decision, ignore what only leads to a dashboard.
How I set this up for a nonprofit client
When I shipped this for a legal-services nonprofit last cycle, the donate button was firing a generic click event, so the board had been reporting "clicks" as if they were gifts for two quarters. We defined a real key event on the payment confirmation page, then built a five-step funnel exploration. The funnel showed a 38-percentage-point drop between amount-selected and donor-details, which is a suggested-amounts and form-length problem, not a traffic problem. They had been buying more traffic to fix a leak that lived entirely on one form. Six reports, one afternoon, and the Q4 plan changed from "spend more on ads" to "shorten the donate form."
What this does not cover
This is the reporting layer, not the plumbing. It does not cover installing GA4 or Google Tag Manager, configuring consent mode for GDPR or CCPA, server-side tagging, or matching GA4 data back to your CRM so you can see lifetime donor value. Those matter, especially consent configuration if you have European supporters, but they are separate projects. It also does not cover GA4 360, the paid enterprise tier, which almost no nonprofit needs. If your CRM is the real question, that is a build-versus-buy conversation, not a GA4 one.
Frequently asked questions
Is GA4 free for nonprofits?
Yes. The standard version of GA4 is free for everyone, nonprofit or not, with generous data limits that no small or mid-size nonprofit will hit. The paid GA4 360 tier exists for very high-volume enterprises and is almost never necessary for mission-driven organizations.
What replaced conversions in GA4?
Key events. Google changed the terminology so that "key events" now describes the actions you flag as important inside Analytics, while "conversions" is reserved for the advertising side in Google Ads. If you learned Universal Analytics, look under Key events for the numbers you used to call conversions.
How do I track donations in GA4?
Fire an event on your payment confirmation page, then mark that event as a key event in Admin. A confirmation-page event is more reliable than a donate-button click, because a click only means intent, while a confirmation view means the gift went through. Then build a Funnel exploration to see where people drop before they reach it.
Do I still need Google Tag Manager?
Usually yes. GA4 can capture basic events on its own, but Google Tag Manager gives you clean control over custom events like donation completions and form submits without editing site code every time. For a nonprofit on a small budget, the setup pays for itself the first time you need to change tracking without a developer.
If you want me to build these six reports and a donation funnel for your nonprofit, so your board sees where the giving flow actually leaks, book a 20-minute GA4 read-out and I will walk your site's numbers with you.