3 Measurement Mistakes We See Constantly

September 28, 2026•4 min read

3 Measurement Mistakes We See Constantly

Most nonprofit analytics problems aren’t underinvestment. They’re not a missing tool or a budget line that never got approved. They’re basic setup and mindset issues that quietly undermine an otherwise solid analytics effort, and they show up across organizations of every size and budget. Here are the three we see most often, and none of them requires a new platform to fix.

Tracking Activity Instead of Outcomes

Pageviews, likes, and impressions share one trait that makes them tempting to report: they’re easy to pull and they almost always trend upward. A busier website and a growing social following will generate more of all three, regardless of whether either one is actually funding the mission. That makes them comfortable numbers to put in a report, and it’s exactly why they’re rarely what a funder or board member actually wants to know.

The fix isn’t to stop tracking activity metrics entirely; they’re still useful for understanding what content resonates. The fix is making sure they never stand in for outcome metrics in a report meant to demonstrate impact. In GA4, that distinction is built into the platform itself: the system tracks dozens of events automatically, but nothing is treated as a meaningful outcome until it’s explicitly marked as a key event. Google’s own documentation is direct about the purpose of this step: it lets you “evaluate the marketing channels that lead users to take those actions” (Google Analytics Help, “Mark events as key events”), meaning a

completed donation, a signed petition, or a submitted volunteer form. Without that step, a page view and a completed gift look identical in the data, which is a large part of how activity metrics end up standing in for outcomes in the first place.

Never Setting a Baseline Before Launching Something New

It’s a common pattern: a new campaign, a redesigned donation page, or a new channel launches, and only afterward does anyone think to ask, “compared to what?” Without a documented baseline captured before the change, there’s no honest way to say the new version actually improved anything. Results might look good in isolation and still represent a decline from what was already working, or look flat and actually represent a real improvement against a worse starting point that nobody wrote down.

This is a five-minute habit, not a research project: before changing a donation page, a campaign, or a channel strategy, record the current numbers. Conversion rate, average gift, cost per donor, whatever the relevant metric is for that specific change. GA4’s reporting only goes back to when tracking and key events were configured, and it doesn’t retroactively reconstruct what “before” looked like if nobody captured it. A baseline costs nothing to collect and makes every future comparison actually mean something instead of relying on impression or memory.

Treating the Dashboard as the Finish Line

Building a dashboard feels like the hard part, and after weeks of pulling data together into something clean and presentable, it’s easy to treat its completion as the end of the project. It isn’t. A dashboard that gets built, reviewed once, and then quietly ignored has produced no more value than not building it at all. The value only shows up when someone actually uses what it says to change a decision: shifting budget toward a channel with a lower cost per donor, adjusting a campaign after seeing a weak trend line, or flagging a retention dip early enough to act on it.

This is often a process gap more than a tooling gap. A dashboard without a recurring review, even a short monthly check-in where someone asks “what does this tell us to do differently,” tends to calcify into a report nobody opens except right before a board meeting.

Fixing These Usually Costs Nothing

None of the three requires new tools or a bigger budget. They require a different starting question when you sit down with the data: not “what can I show,” but “what does this tell us to actually do.” Marking real outcomes as key events, capturing a baseline before every change, and building a habit of actually using the dashboard are all free, and all three compound the value of everything else in your analytics setup.

If any of these sound familiar, you’re not alone, and fixing them is usually faster than it looks. DC Clicks helps nonprofit teams turn existing analytics setups into something that actually gets used; if that would help, book a strategy call.

Sources

Google Analytics Help, “Mark events as key events”

Back to Blog