Templates · Queries, not files

Report templates as SQL

A widget set you pin once, not a file that is stale the day it is saved.

Every marketing report template you can download has the same defect: it is a snapshot. A Looker Studio copy, a Sheets tab, a branded PDF — each is correct at the moment it was generated, needs a rebuild for the next client, and hides its reconciliation logic inside a chart nobody can inspect.

If what you want is a file to download and hand over — a Looker Studio copy, a Google Sheets tab, a branded PDF — the vendors ranking on this query have those and TableBI does not. This page is the other kind of template: the queries, and a URL that keeps answering them.

Each template below is the queries: what belongs in that report, what to leave out, and the exact SQL for every widget. tablebi pin turns the set into one public read-only URL that re-runs itself — one is running here.

Why a query beats a file

Three reasons, in the order they bite. A file is stale the moment it is saved, so the first question about it is always "are these current?". A file's logic is invisible — whoever built it decided how to reconcile cost across platforms and that decision now lives inside a chart. And a file does not carry its own caveats, so the reader who notices that Search Console clicks do not equal GA4 sessions emails you instead of reading the note.

A pinned query set fixes all three: it re-runs, the SQL is right there, and every answer carries per-source freshness plus the caveats that apply to it.

Related: the free calculators for the arithmetic, and honest comparisons with the reporting platforms that do have white-label delivery.