Your year-end board report needs five website numbers: how much money the site raised, how well the donation page converted, whether the right people reached the pages that matter, where your search visibility is trending, and one honest risk flag. Everything else is noise you can cut.
The short version
- Report outcomes, not activity. Online revenue and donation-page conversion rate tell your board more than raw traffic ever will.
- Use engagement rate, not bounce rate. Google defines an engaged session in GA4 as one that lasts longer than 10 seconds, has a key event, or has two or more page views.
- Show a trend, not a single month. Boards make budget decisions on direction, and Q4 giving is too seasonal to read one month in isolation.
- Include one risk metric so the report reads as honest rather than a highlight reel.
- Cut the vanity numbers: raw pageviews, social follower counts, and bounce rate as a headline.
Why this lands on your desk right now
Most nonprofits close their fiscal year on December 31, board meetings cluster in November and December, and GivingTuesday falls on December 1 in 2026. So the year-end website report is being drafted right now, in the same weeks the site is doing its heaviest lifting of the year. That timing is the trap. When traffic and gifts are spiking, it is easy to hand the board a page of green arrows that says nothing about whether the website is actually built to convert.
I have sat in enough of these meetings to know what happens next. A director pulls a default GA4 dashboard, screenshots forty metrics, and the board glazes over by the third chart. Nobody leaves the room knowing whether to invest in the site next year. The fix is not more data. It is deciding, before you open Analytics, which five numbers answer the only question a board actually asks: did the website move the mission and the money.
Start with the money the website actually moved
The first number on the page should be online revenue, because it is the one metric your board already knows how to read. Report total online gifts, the number of gifts, and the average gift, and compare each to the same period last year rather than last month. Year-over-year is the honest comparison in Q4, because a month-over-month view during giving season will always look inflated.
One caution from experience: your donation processor is the source of truth for dollars, not GA4. Analytics tracks a donation as a key event, but ad blockers, consent banners, and cross-domain checkout redirects all cause GA4 to undercount. When I reconciled a state association client's numbers last year, GA4 was reporting roughly a fifth fewer gifts than the processor because the thank-you page sat on a separate donation subdomain and the tag never fired there. Always cross-check the two before a single figure reaches the board.
Report donation-page conversion rate, not just visits
Conversion rate is the number that tells the board whether the website is doing its job or just being looked at. Calculate it as completed gifts divided by donation-page sessions. A page with fewer visits and a higher conversion rate is healthier than a high-traffic page that leaks donors at the form.
When I rebuilt the donation flow for a legal-services nonprofit, sessions to the page barely moved, but completed gifts rose sharply after we cut the form from eleven fields to five and removed a redirect between the ask and the payment step. If I had reported traffic, the board would have seen a flat line and concluded the work failed. Reporting conversion rate showed exactly what the investment bought. That is the difference between a metric that defends your budget and one that quietly undermines it.
Use engagement rate, and know what Google means by it
Swap bounce rate for engagement rate, because bounce rate as a headline misleads a non-technical board. Google Analytics 4 (GA4) defines an engaged session as one that lasts longer than 10 seconds, includes a key event, or has two or more page or screen views, and engagement rate as the percentage of sessions that qualify. You can read the official definitions in Google's Analytics Help.
Report engagement rate for your highest-intent pages, the donation page, key program pages, and the contact or volunteer page, rather than a sitewide average. A sitewide figure buries the pages that matter under blog posts and press releases. If your donation page has a low engagement rate, that is a five-alarm signal the board should see, and it is invisible in an aggregate number.
Show the search and AI-visibility trend, not one month
Boards fund direction, so show the trajectory of how people find you, and include AI answer engines now that they shape discovery. Pull the clicks and impressions trend from Google Search Console over the trailing 6 to 12 months, and note that Google has begun surfacing AI Mode and AI Overviews performance in Search Console reporting. Keep it to one line the board can absorb: are we more or less findable than we were a year ago, in both classic search and AI answers.
This is also where you connect the website to the fundraising story. If organic visibility is climbing, your cost per acquired donor is quietly falling, which is a stronger argument for web investment than any traffic chart. If you want the deeper method behind earning citations in AI answers, I wrote about that in GEO for nonprofits.
Add one risk flag so the report stays honest
Every board report should carry one thing that is not working, because a report with no bad news is not a report, it is marketing. Pick the risk with the clearest legal or revenue exposure and name it plainly. The three that usually qualify are accessibility, page speed, and a broken conversion path.
Accessibility is the one I flag most often. Web Content Accessibility Guidelines (WCAG) failures are legally actionable under the Americans with Disabilities Act (ADA), and they cost you donors who use assistive technology. A donation form that a screen reader cannot complete is both a compliance problem and a fundraising leak. You do not need a full audit for the board, just an honest sentence: here is our biggest known risk, here is what it would take to fix it. If you want the fast version of that check, my 30-minute nonprofit accessibility audit covers the failures that carry the most exposure.
What this does not cover
This is a board-reporting framework, not a full analytics audit. It does not cover GA4 setup or tag configuration, multi-touch attribution modeling, email and customer relationship management (CRM) metrics, or program-level impact measurement. Those belong in an operating review with your staff, not in a board deck. The point of the board report is ruthless selection: five numbers that map to money and mission, and the discipline to leave everything else out.
Frequently asked questions
How many website metrics should a nonprofit board report include?
Three to five. A board meeting is not an analytics review, and every metric past the fifth one lowers the odds that any of them get discussed. Choose the numbers that tie directly to revenue, conversion, and risk, and move the rest to a staff-level operating report.
Should we report bounce rate to the board?
No. Bounce rate is easy to misread and invites the wrong conclusion from a non-technical audience. Report engagement rate instead, which GA4 defines as the percentage of sessions that last longer than 10 seconds, include a key event, or have two or more page views. It measures the same idea in a direction that is harder to misinterpret.
What is a good donation-page conversion rate?
The honest answer is that it depends on your traffic mix, and chasing a published industry benchmark will mislead you. Warm email traffic converts very differently from cold search or social traffic. The comparison that matters is against your own prior period on the same page, which is why the board report should show your trend, not someone else's average.
How often should the board see website numbers?
Quarterly is enough for most nonprofits, with a fuller year-end read tied to the annual report and next year's budget. More frequent reporting pulls the board into operational detail that belongs to staff. The year-end report is the one that should argue explicitly for or against web investment in the coming year.
Where do the AI Overviews and AI Mode numbers come from?
From Google Search Console, which has begun including AI-surface performance in its reporting rather than hiding those visits inside general organic data. Treat it as a trend line for now, not a precise attribution number, and frame it for the board as a directional signal about whether AI answer engines are sending you traffic.
If you want a second set of eyes on your year-end website report before it goes to the board, book a 20-minute read-out and I will tell you which numbers to keep, which to cut, and which risk flag belongs on page one.