UpbuildWritten by Uptimal, the team that builds and operates Upbuild and runs marketing analytics for multinational clients across the globe. Everything below reflects how the product actually works, including the parts that are deliberately boring.
Client reporting has a last-mile problem. The analysis is done, the numbers are right, and then the delivery mechanism is a PDF that was stale at export time, or worse, a platform login shared "temporarily" in 2024 that still works. Sharing is where reporting stacks leak, so Upbuild Enterprise treats it as an architecture question rather than a feature checkbox.
One dashboard, one origin
Every dashboard is served from its own isolated origin, a separate address that carries exactly one page and nothing else. That origin has a locked-down content policy, no cookies, and a viewer reaches it with a short-lived signed token rather than a session. The blast radius of "this link got forwarded" is one page of numbers that were going to be in the client deck anyway, expiring in minutes, not a foothold in your reporting app, and never a platform login.
The page itself is the live artifact: the same self-refreshing dashboard your team sees, with real charts and yesterday-ending windows, not an export frozen at send time. When a refresh fails upstream, the client sees the last good data and a clear state, never a broken chart.
Grants follow accounts, not logins
The quiet unlock is where access control lives. An agency connection is one sign-in that can legitimately reach hundreds of ad accounts across platforms; sharing "the connection" would share the roster. So grants attach to individual ad accounts: this person, or this link, sees dashboards built on these accounts and nothing else. One connection serves many clients without a Chinese-wall spreadsheet, and a departing teammate takes no access with them because connections belong to the organization, not the person.
Dashboards, pipelines and alerts, run by your assistant.
Upbuild Enterprise puts live dashboards, scheduled exports and alerting on top of the same read-only connector: built in chat, governed by your organization, versioned like software.
See Upbuild Enterprise → Book a callWhat the client experiences
A URL that always shows this week. No login ceremony for link viewers, a normal sign-in for named ones; view and edit are different rights, so a client contact can watch without being able to bend the page. Versions mean the Monday review can scroll back to last month’s state instead of relitigating it from memory. And when they ask for a change, the answer is a sentence to the dashboard’s agent, tested and published, not a redesign sprint.
The comparison agencies actually run
Against portal products, the difference is that the dashboards are born from prompts and maintained by conversation, so the cost of a bespoke view per client collapses. Against BI-tool public links, it is the isolation model: purpose-built origins and per-account grants rather than one workspace with carefully crossed fingers. Against PDFs: it is Tuesday, and the page already knows.
Frequently asked questions
How do I share a live marketing dashboard with a client?
In Upbuild Enterprise each dashboard lives on its own isolated web origin. You grant people access, or mint a link token, and the client opens an always-current page. No platform logins change hands and nothing on the page is writable.
Is a shared dashboard a security risk for our ad accounts?
The shared page cannot reach your accounts at all: it is served from a locked-down origin with no cookies, viewers get short-lived signed tokens, and the underlying data access is read-only by construction.
Can clients see accounts they should not?
Access is granted per ad account, not per login. A connection that reaches hundreds of accounts shares only the ones explicitly granted, so one agency sign-in can serve many clients without cross-contamination.