Live Client Report: How to Send One Link That's Always Current

The failure modes are specific, and you've probably lived all of them:

Version sprawl. Report_Final_v3_MARCH_updated.pdf. Your client has six versions in their inbox and can't tell which is current. They forward the wrong one to their boss, who quotes a number you fixed two months ago. Every send creates another file that outlives its own accuracy.

Stale on arrival. A PDF freezes the reporting window at the minute you exported it. If you correct an error or add late-arriving data, every copy you already sent stays stale — and there's no way to update the one sitting in the client's inbox.

No proof of receipt. A normal attachment gives you no reliable evidence the report itself was read. Opened, skimmed, or trashed — you can't tell. You lose one useful engagement signal, so an ignored report can go unnoticed until the next client conversation.

The "can you resend it?" tax. Every month: re-attach, re-email, re-explain which file is the latest. Multiply by your client count. Unbillable admin that scales linearly with your book.

Spreadsheets leak and break. Send a live Google Sheet and the client can see your formulas, sort one column and mis-order everything, or — if permissions slip — glimpse another client's data. Send an XLSX and it renders differently in whatever Excel version they're running.

Deliverability. Big PDFs get stripped by mail filters or bounce on attachment limits. The client never sees it, and you never know.

Now the honest counterpoint, because it matters: PDFs aren't all bad. They're portable, archival, work offline, and some clients — finance, legal, anyone assembling a board deck — want a fixed, dated, signed-off artifact precisely because it can't change under them. "Always current" is a feature for a tracking report and a bug for a contractual one. If the client needs a document they can file and cite in six months, a stable PDF is the right call. Everything below is about the other case: the recurring performance report nobody should have to re-send.

The mechanism, in plain terms: publish once to a permanent URL, then change what lives at that URL instead of sending a new file. Every method below gives you a stable link. They differ on who refreshes the numbers and how much plumbing you own.

Purpose-built agency reporting platforms — AgencyAnalytics and Databox are the two names you'll keep hitting. This is the true Type-1 auto-refresh path: many integrations, white-label dashboards, custom domains, scheduled reports, clients who can log in and slice the data themselves. Best when you report the same platform KPIs across many clients. Tradeoff: pricing is typically per-client or per-source, so it scales up with your book; connectors need maintenance; and the output looks like everyone else's templated dashboard. Overkill for a solo with two or three clients. Both publish current pricing and integration counts on their sites — check the live AgencyAnalytics and Databox pricing pages before you budget, since tiers move.

Google Looker Studio — free, and a strong free route to a genuinely auto-updating dashboard. Connect GA4, Google Ads, Sheets, BigQuery, plus hundreds of partner connectors, and share a viewer link that refreshes on the source's cadence. Tradeoff: the design is generic, white-labeling and sharing controls are limited, non-Google sources usually need a paid third-party connector like Supermetrics, there's no built-in recipient-level read tracking, and the whole thing visibly reads as "a Google report."

Google Sheets "Publish to web" (File → Share → Publish to web) — turns a sheet or range into a web URL that auto-updates a few minutes after you edit the source, showing values not formulas. The poor-man's live link when your data already lives in a sheet. Tradeoff, and it's a real one: publishing may expose the sheet to everyone on the web or a broad organizational audience depending on your account settings — so check the resulting access setting, and never use it casually for confidential client numbers. It's also plain-looking and has no view tracking.

Notion or Coda shared page — both can maintain a report at a stable shared URL, with embedded charts and a public toggle, and both are good if you already live there. Tradeoff: neither is a data pipeline (you paste or sync numbers in), and their publishing, analytics, branding, and access controls differ by product and plan — check those controls on your current plan before you put client data behind a public link.

Hand-built or AI-built HTML report at a stable link — you (or an AI) generate a self-contained HTML report from the month's numbers and publish it to one permanent URL, replacing the content each cycle. This is the Type-2 "always-latest" model, and the refresh can be scripted: a script or an AI agent pulls the numbers, rebuilds the HTML, and re-publishes to the same address. Tradeoff: you own the number-gathering — there's no connector doing it for you unless you build one — and "current" means "as of last publish," not real-time.

The upgrade path most people miss: you don't have to choose one. A common pattern is a Looker Studio or Databox dashboard for the raw live data (for clients who want to poke around) plus a curated, narrated monthly report at a branded link (for the client's boss, who wants the story, not the sea of charts).

A practical recipe:

1. Decide which "live" you need. Monthly retainer story → Type 2 is enough. Client who checks daily → Type 1.
2. Pick the weakest tool that clears the bar. Solo with a few clients → free Looker Studio or a published HTML report. Many clients, same KPIs, white-label required → AgencyAnalytics or Databox.
3. Put it at one permanent URL and never send a file again. Send the link once, then just say "it's updated."
4. Set a recurring publish checklist if you're on Type 2, so "always current" doesn't quietly become "current whenever I remember." Automate the refresh only once you have reliable access to the source data and someone will own the failures.
5. Protect sensitive numbers with a password, not an unlisted URL. An obscure or unlisted link can still be opened or forwarded by anyone who has it — this is exactly where "Publish to web" and open Notion links fall short for confidential figures.

This is a quietly useful capability you may not realize is on the table. A normal attachment gives you no reliable evidence the report itself was read — that's the baseline to beat.

A tracked link tells you whether it was opened, when, how many times, roughly how long the visit lasted, and often the country. That turns reporting from a broadcast into a signal — account-management intelligence, not vanity. Read it as a prompt, not a verdict: repeated non-opens are a reason to check in; repeated opens right before an upsell can justify a conversation. Neither one proves churn risk, interest, or who was on the other end.

Where the tools stand: Looker Studio and Google Sheets "Publish to web" give you essentially no recipient-level read tracking — a genuine gap worth naming if that intelligence matters to you. Document-tracking tools in the DocSend mold give deep read analytics but treat the report as a sent document rather than a living link. Purpose-built link tools with view tracking sit in between.

Now the honest limits, because overselling this backfires. A tracked link tells you the link was opened and for how long — not who opened it. A forwarded link, a shared screen, an assistant opening it for the client, or an email scanner pre-fetching the URL all read as "opened." "Time on page" is approximate; a tab left open all afternoon inflates it. And tracking can be blocked outright. Longer and repeat visits are stronger signals than a single open, but they're still signals, not courtroom evidence.