A CFO does not push back on fan engagement reporting because the numbers are small. They push back because the numbers cannot be traced to a real person. The metrics that survive the meeting are the ones built on a verified audience and tied to a name, not the ones built on impressions.
Every rights holder already has a follower count, a reach figure, and an engagement rate. None of them answer the question a finance team actually asks: who, specifically, is behind this number, and can we check it? This is what a fan engagement report looks like when it is built to survive that question.
Why doesn't finance trust the engagement numbers a club already reports?
Three structural reasons, and none of them are about the CFO being difficult:
- The denominator is unaudited. A follower count includes whatever share of purchased, abandoned or farmed accounts happens to sit in that following, and almost no rights holder has checked. An engagement rate computed over that base inherits the same inflation.
- The numbers describe activity, not people. "2.1 million impressions" or a 4 percent engagement rate tells finance that something happened, not who did it. A metric with no name behind it is not something a finance team can act on.
- The link to commercial value is asserted, not shown. "This drove awareness" or "this justifies the sponsorship rate" is a claim. Finance, and increasingly a sponsor's own analytics team, wants the evidence underneath it.
What does a fan engagement report finance will actually believe contain?
Four things, each answering a question the CFO would otherwise have to ask themselves:
- Real-audience size. Not the follower count - the number that survives authenticity filtering. In the one production scan run to date, 78,181 followers went in and 5,806 real, rankable accounts came out. That was a Web3 project's following, not a sports one; see the note below on why that matters before you use it as a benchmark.
- Who actually engaged. Named, scored, real accounts - the specific supporters worth a club's time, not an anonymous aggregate hiding behind a percentage.
- What they did, with evidence. The reply, the share, the piece of first-party fan data each interaction produced, with a link or a timestamp a reader can check. This is the line item that survives being handed to a sponsor's own team.
- Cost against verified outcomes. Spend measured against actions that demonstrably happened, not against reach that might have been seen by nobody real.
The difference between a report finance funds and one it dismisses is whether the reader can check it. A verified metric invites the audit; an aggregate one has to survive it unaided.
Why does naming the person change the conversation?
Because it moves the burden of proof off the rights holder. A report built on impressions asks finance to trust the platform that generated the number. A report built on named, verified fans hands finance the evidence and lets them check it themselves. That is a different meeting: instead of defending the methodology behind an aggregate rate, the conversation moves to what the verified activity implies for next season's sponsorship inventory or activation budget.
Why does the 90.96 percent number not belong in a sports report?
Because it is not a sports number, and treating it as one would be exactly the kind of unchecked claim this whole approach is supposed to fix. The 78,181 followers scanned, 90.96 percent filtered, and 5,806 real accounts figures come from the one production scan run so far, on a Web3 project's X following. Crypto audiences are farmed harder than almost any category on the platform, so that rate is closer to a worst case than a typical one. A club's following is inflated too, but almost certainly at a different rate. The only way to get a defensible number for a specific team, league or athlete is to run the scan on that property's own following - see how many of a club's followers are actually real for the full method.
How do you start building one of these?
Change the denominator first. Before the next board deck or sponsorship renewal, run the following through an authenticity filter and report the real-audience count, even though it will be smaller than the headline follower number - it is what makes every number after it credible. Then report engagement only for the fans who cleared that filter, with evidence attached to each action. A rights holder's inventory is worth more, not less, once the audience behind it is provable. The full method sits on the methodology page, and what this looks like specifically for a club, league or athlete's following is on the sports page.
Quick answers
What fan engagement metrics does a CFO actually accept?
Ones tied to a real, identifiable person rather than an aggregate. A real-audience count after authenticity filtering, a named list of the fans who did something, evidence for each action, and cost measured against those verified outcomes. A rate computed over an unaudited follower base does not survive the question 'how many of these are real people?'
Why do finance teams distrust reach and impressions from a rights holder's social channels?
Because the denominator is unverified. A follower count includes whatever share of purchased, abandoned and farmed accounts happens to be sitting in that following, and nobody has checked which accounts those are. A rate built on an unaudited base is a rate a finance team cannot defend to a board or a sponsor's own analytics team, so it gets discounted or ignored.
How is fan engagement different from fan intelligence?
Engagement metrics describe activity in aggregate - likes, replies, impressions, reach. Intelligence names which specific people in the following are real and which of those are worth activating. A club can have high engagement numbers and still not be able to name a single fan who drove them. The metrics that survive a CFO come from intelligence, not from aggregate engagement.
What should a fan engagement report contain instead of impressions?
Four things: the real-audience size after bot and farm filtering, who in that real audience actually engaged, what they did with evidence attached, and cost measured against those verified actions rather than against raw reach. Each line should be checkable by the reader, not asserted by the report.
Does the 90.96 percent bot rate apply to a sports following?
No, and citing it as a sports number would be dishonest. That figure came from the first production scan CommunityOS ran, on a Web3 project's X following, and crypto audiences are about as farmed as an audience gets on the platform. A club's following is inflated too, but almost certainly at a different rate - the only way to know a specific team's number is to run the scan on that team's following.