It would be cool to have more precise numbers and neat stats on more specific attacks but as long as I'm protected I don't really care.
Regardless of that...
I'd argue the reality is it's nearly impossible, expensive, or just plain risky to host any high-profile website without Cloudflare today (using their campaign offering or not). Between security and random traffic spikes it's simply an awesome / killer / the absolute best deal. All clients must go on Cloudflare for me.
The only other option is to go 100% static - ultimate security and speed - which also has its trade-offs.
Cloudflare actually doesn't offer a pure static option even with their election protection program. The ability to just go "pure static" doesn't exist to my understanding.
E.g.: You can try to mimic "fake static" by turning on 100% HTML Page Cache on, Firewall rules to block non GET/HEAD requests. This still subjects you to cache busting techniques to hit origin (/?fbid=1, /?fbid=2, /?fbid=3, etc...). This is because ignoring query strings and pure HTML cache only would only be possible using Workers or an Enterprise plan with Custom Cache Keys - both which are not offered under their campaign program.
The best work-around would be rate-limiting but that still exposes origin and has it's trade-offs.
Google offers an election program [1] which is more the pure cache = pure security philosophy. Way, way less flexible though. Just some thoughts.