When the connector doesn't exist
Whatagraph's strength is breadth across sources that play nicely with connectors. But a connector can only fetch from an API, and many sources don't offer a usable one. They're export-only, login-only, or carrying an API too thin to report from. For those, a connector-based tool has nowhere to plug in. reportr reads the already-rendered page in the tab you're logged into, and uses the official API where a good one does exist, so it covers both ends.
Because the read happens client-side in your session, reportr can reach a carrier portal that no marketing connector can touch. It doesn't log in for you, doesn't bypass access controls, and doesn't warehouse your data centrally. Host permissions are narrow and consent is per source. A capture health signal distinguishes a clean read from an empty or layout-drifted one, so a portal that changes gets you a warning rather than a blank report.
Different problems, not a feature race
If your reporting lives entirely in connectable marketing platforms, Whatagraph may be the better fit, and reportr isn't competing for that work. The two solve different problems. reportr is the alternative when the data you need is stuck behind a no-API login, where connector-based reporting can't go at all.
reportr's first vertical is insurance commission reconciliation: it compares your book of business against what carriers actually paid and flags the gaps. The engine itself is vertical-agnostic, so other no-API sources are future adapter packs. Both tools produce branded, white-label reports, and the real distinction is which sources each one can actually reach.
Whatagraph vs. reportr
| Whatagraph | reportr | |
|---|---|---|
| How it gets data | Connectors to platform APIs | Reads the portal tab you're already logged into; API where one exists |
| Sources covered | Marketing platforms with connectors/APIs | No-API, export-only, and login-only sources |
| Insurance carrier portals | Out of reach, no connector | Supported, and the first vertical |
| Where data is processed | Hosted cloud platform | Client-side, in your own browser session |
| White-label | Yes | Yes: your logo and brand colors, mark removed on paid plans |
| Best for | Multi-source marketing reports over connectors | Reporting and reconciliation for data behind a no-API login |
frequently asked
Should I switch from Whatagraph to reportr?
Only if your problem is the one reportr solves. Whatagraph is built for multi-source marketing reports over connectors, and if that's your whole need, stay with it. reportr is for the sources it can't reach: data behind a login with no usable API, starting with insurance carriers.
Why can't Whatagraph report on a carrier portal?
Its connectors fetch from APIs. A carrier commission portal doesn't expose a usable one, so there's no connector to build. reportr instead reads the rendered portal in your authenticated session, which is how it reaches sources connector-based tools can't.
Where does reportr process my data?
Client-side, in the browser tab you're already logged into. It doesn't log in for you, doesn't bypass access controls, and doesn't centrally warehouse scraped data; permissions are narrow and consent is per source.
Are reportr's reports white-label like Whatagraph's?
Yes. Each report carries your logo, brand and accent colors, and a footer note. Paid plans remove the 'Powered by reportr' mark, enforced server-side; the free tier keeps it.
Last updated June 8, 2026