Upbuild
Upbuild / AI Dashboards
AI marketing dashboards
Describe the dashboard you would have briefed an analyst to build. Upbuild writes the data requests, draws the page, and refreshes it on the cadence you set. Your client opens it with a link: no Upbuild account, no platform login.
Every platform on one subscription
Will it still be right in six weeks
A dashboard here is two things kept together: a page, and a plan of the data requests behind it. Upbuild replays that plan on its own cadence, every 30 minutes, hourly or once a day, and writes the fresh rows into the page at serve time. The page itself never fetches anything, which is why it cannot half load, rate limit, or quietly show last quarter.
If a good refresh has not landed within twice its own cadence, the hub row flips from FRESH to STALE and the page carries the moment it was last right. Nobody presents a number that stopped moving three days ago.
Every change is a numbered version stored with its author and its note. Restoring an old one is itself a new version, so a rollback can be rolled back, and the live version is never the one pruned.
Built with your assistant, refreshed by Upbuild on their own cadence. Every version stays restorable.
| Dashboard | Version | Refresh | State | Last refresh |
|---|---|---|---|---|
| Northwind Retail | Executive Overviewd-om2ggxzfce | v33 | 60 min | FRESH | 20:46 |
| Harbour Group | Market Pacingd-4dwjov2m4v | v25 | 30 min | FRESH | 20:51 |
| Meridian Markets | Search & Shoppingd-gnk6eaao2w | v32 | 1440 min | FRESH | 06:00 |
| Lumen | Paid Social Weeklyd-tkwjlv5cti | v12 | 60 min | STALE | yesterday |
Can my client open it
Set a dashboard's general access to "Anyone with the link" and it gets one address that does not expire. The person you send it to needs no Upbuild account, no seat on your plan, and no login on Google Ads, Meta or GA4. They see the title, the published version and the line saying when the data was last right. Turning the link off is permanent for that link: switching sharing back on mints a new one, so a link you took back can never be brought back.
One connection is one sign-in, and one sign-in usually reaches dozens of clients. Upbuild hands out the individual ad accounts inside it, so a person working on Northwind cannot read Harbour Group, and a dashboard they build can only read what they hold.
Pages are served from their own subdomain with a locked policy: no cookies, no outbound connections except back to themselves, no forms, and framing permitted only by Upbuild. An escape from one dashboard reaches nothing else.
view only · as of 09/09/2026 20:46 UTC
When it needs to change
The edit panel is a conversation, not a settings form. You describe the change in the words you would use to a colleague, and Upbuild applies it on top of the version that is live, then hands back a draft to open. The model doing the work is named on screen, Claude Opus 5 today, and the edits left in your monthly allowance sit under the composer, so the cost of a change is never a mystery.
The change arrives as the next numbered version with an "Open v32" button beside it. The live dashboard keeps serving the old one until you publish, and link holders only ever see what is published.
Paste the complete HTML into Upbuild and it lands as a draft on a new dashboard, ready to be wired to live data. Outside libraries are highlighted and swapped for the pinned in-house copies before anything is created.
Describe the change, for example: put the campaigns in order of spend.
Changes applied on top of version 31. Have a look before you publish it.
Getting one running
There is no modelling layer to define first and no connector to buy per platform. The accounts you already reach are the accounts a dashboard can read, on the day you sign in.
Sign in with Google or Microsoft. Access is per user, so you reach exactly the accounts your own login already reaches and nothing more. One live organisation reaches 859 of them across three connections, which is the shape this was built for.
Three doors, all from the New dashboard menu, all landing the same object: build it with Upbuild AI in the app, paste a page you made in a web chat, or ask your own assistant through the MCP connector in Claude, ChatGPT, Copilot Studio or Gemini Enterprise.
Pick 30 minutes, hourly or daily, then pick who opens it: only the people you name, everybody in your organisation, or anyone with the link. People inside get viewer or editor, with an optional end date on the grant.
Who this is for
One brand with two ad accounts does not need this. An operation where the same dashboard has to exist per client, per market or per region, and be right on a Monday morning, does.
One dashboard per client, each on its own cadence, each opened by the client through a link with no seat and no platform login to chase. One organisation in Upbuild runs 101 of them today. Because grants are per ad account, an account manager on one client cannot read another, and neither can a dashboard they build.
The same dashboard per market, drawing from Google Ads, Meta, TikTok, DV360, CM360, GA4 and Adobe Analytics inside one page, so the group view and the market view come from the same request rather than two spreadsheets that disagree. The served page carries your organisation's timezone, so dates read the way your team reads them.
Fifty versions deep, each with the person who made it and the note describing what changed. Whoever inherits the account can read that history and restore any of it without knowing how the thing was built, because the plan of data requests travels with the page.
Every tool that touches an advertising platform is read-only. Dashboards are served from a per-dashboard origin with no cookies, a content security policy that permits nothing but the page, and their chart libraries pinned by hash and served immutable. Data is injected at serve time; the page issues no requests of its own.
Get in touch