Getting started
First run is two screens and one decision. You name a workspace, you connect an ad account, and you tell Tempio how much of that account's history to pull. Everything after that — the dashboard, the account brief, the agent, the gate — reads the rows those three steps put in place.
Before you start
You need a Tempio account and a login that can reach the ad accounts you want to connect. They are usually not the same login, and they do not have to be held by the same person: whoever sets the workspace up can leave the connecting to whoever holds the ad-account access.
Accounts are created by invitation while the site is gated. Two ways in:
- You were invited to an existing workspace. The invitation email carries a link. If you already have a Tempio account, it opens the invitation: who invited you, which workspace, which role. Accept puts you in that workspace and takes you to its dashboard. If you have no account yet, the link opens the sign-up page for the invited address first. Create the account with a password, then confirm your address from the verification email; its link brings you back to the invitation to accept. If you continue with Google, GitHub or Microsoft instead, using the account registered to the invited address, the provider has already confirmed it and you land on the invitation straight away. You skip both first-run screens either way; they only show for someone who belongs to no workspace yet, and your starting point is Connections or the dashboard, depending on what the workspace has already done.
- You asked for early access. When Tempio invites you, an email with the subject "You're in" arrives with a Create your account button. The link works for 14 days and only for the address it was sent to. It opens a sign-up page with that address filled in and locked. Choose a name and a password, or continue with whichever of Google, GitHub or Microsoft the page offers, using the account registered to that address. Either way the address counts as confirmed, so no verification email follows. An expired link tells you to ask whoever invited you for a new one, and a link that was already used points you to the sign-in screen.
Anyone else who tries to create an account, including through a social button on the sign-in screen, is told Tempio is invite-only and pointed at early access. Once you have an account, sign in with email and password, or with whichever social buttons the sign-in screen offers. If two-factor is switched on for your account, the code screen follows the password.
Screen one: name your workspace
A workspace is the room everything else lives in: connections, campaigns, drafts, media, plans, members and billing all belong to one. Nothing is shared between workspaces, and every read and write Tempio does is scoped to the one you are in.
The screen asks for one thing — a name, up to 80 characters. Something a teammate would recognise is the right answer: the business, the client, the brand. The name is also turned into the workspace's slug; if that slug is already taken, Tempio appends a short suffix rather than asking you to think of another name.
You are the owner of the workspace you create, which is the role that can connect ad accounts, invite people, write approval rules and change the plan.
Two things worth knowing about this screen:
- It is strictly first-run. Once you belong to a workspace, opening it sends you to the hub instead. Later workspaces are created from account settings, not from here.
- If your plan has no room for another workspace, the form says so and stops. A different name does not fix that one, so it does not retry into the same refusal. Billing has what each plan includes.
Continue creates the workspace and takes you to the second screen.
Screen two: connect an ad account
The connect screen shows one card per platform Tempio connects, each with a short line on what it covers. Connect opens that platform's own sign-in in the usual way; Tempio never asks you for a platform password.
What you can do here depends on two things:
| What you see | Why |
|---|---|
| Connect | You are an owner or an admin, and the platform is switched on for this deployment. |
| Connect, disabled, with "Ask a workspace owner to connect this" | You are a member. Connecting is a change to the workspace, so it sits with owners and admins. Members still see every card and every status. |
| Connect, disabled, with a Not yet enabled badge | The platform is not switched on. The card stays on the screen rather than disappearing, so what is coming is visible. |
Skip for now is on the screen on purpose. The platform you want may not be the one you are holding a login for today, and the person setting the workspace up is often not the person with ad-account access. The hub works without a connection — it shows you what it is waiting for — and Getting started, at the foot of the sidebar, keeps the step in front of you until it is done.
Connections count against your plan. If the workspace is already at its limit, Connect returns you to Connections with a line saying so rather than starting a sign-in that could not have finished.
Choosing accounts, and how much history
Coming back from the platform, Tempio lists every ad account that login can reach. Each row carries the account's name, its id, its currency and its timezone, so two accounts with similar names are still told apart. Accounts you have already connected are ticked and locked; test accounts sort to the bottom, where they cannot bury the real ones.
Tick the accounts Tempio may read. Each one you tick becomes one connection row, with its own status, its own sync history and its own defaults.
Under the list is the one decision of first run: How much history to pull.
| Choice | What it does |
|---|---|
| Last 90 days — recommended | Gives the agent a real baseline. Large accounts take 10–20 minutes. |
| Last 30 days | Faster. Enough for a first read on the account; trend lines are shorter. |
| Start from today | No history. Numbers begin with the next sync, which still includes the trailing window the platform lets Tempio re-read. |
The choice applies to every account in that submission and is stored on each connection, so a retry loads the same amount rather than quietly loading more.
"Start from today" is not zero data. Every sync re-reads a trailing window — 28 days on Meta, 30 on Google, 14 on TikTok — because that is the span each platform still restates, so even the first run lands the last few weeks. And the choice is not permanent: a connection row shows History from the day its stored history starts and offers Load 90 days of history whenever there is more to fetch. Loading history adds the days before what you have; it never removes anything already stored.
Connect selected writes the connections and starts the first sync. Connections covers the whole of this — the statuses, the weekly deep re-read, reconnecting, and adding accounts later.
While the first sync runs
The first sync pulls structure first — campaigns, ad groups (ad sets on Meta) and ads — then the daily numbers for the history you chose. On a large account with 90 days asked for, that is a lot of rows and 10–20 minutes is normal. 30 days takes a few minutes. Every sync after it walks the same entities over a shorter window.
You do not have to watch it. The connection row reports itself while it runs: how long it has been going, what stage it is in, how many campaigns, ad groups and ads it found, and how many rows of daily numbers have landed. The page refreshes itself every half minute, so the counts move without a reload, and Sync now stays disabled until the run finishes.
What lands when it finishes
Two things appear on the dashboard.
The numbers. Spend, impressions, clicks, conversions and the ratios drawn
from them, over the range and platform filter you choose, with a chart and a
per-channel table under them. Tempio stores base counts and computes every
ratio when the page is drawn, so a rate with nothing to divide by shows as —
rather than as zero. Metrics is the whole rule.
The account brief. When the first sync lands, Tempio reads back what it stored and writes one page of facts per ad account: how much history there is, the totals, where the money goes, what is working and what is not, and the weekly rhythm once there are four weeks to judge by. An account needs at least seven days with spend before it gets one. The brief is what the agent knows about your account before you ask it anything, which is why "is a $40 cost per conversion good?" gets answered against your own history.
How much history you asked for shows in that first brief. Ninety days fills the window straight away; the shorter choices give a shorter brief that fills out as the weekly re-read catches up.
The Getting started card
Until it is finished, the foot of the sidebar carries Getting started: four steps, each a link to where it is done, under a bar with one segment a step.
| Step | Where it goes | Counts as done when |
|---|---|---|
| Connect an ad account | Connections | The workspace has at least one connection |
| Ask the agent something | The agent | The workspace has used the agent at least once |
| Invite a teammate | Account settings | There is a second member, or a pending invitation |
| Choose a plan | Account settings | The workspace is on a paid plan |
Nothing about the steps is stored except the dismissal: each step is read from the rows themselves, so it cannot claim something is done that is not. It disappears on its own when all four are done, and an owner or an admin can dismiss it before then. Anyone can shrink it to its header with its minimise button; that choice is kept in the browser you made it in.
Your first change
Nothing in Tempio writes to an ad platform directly. A row action, an agent instruction and a call from your own AI all produce the same thing: a change request waiting at the gate, with its guardrails checked, its currency stamped and its author on the record. It is applied when it is approved — by you, or by a rule your workspace wrote.
The short path from here:
- Open Campaigns, find a row, and open the menu beside its name. The dialog's button reads Create draft.
- Open Drafts and read what it would change. Approve applies it; reject closes it.
- When you are tired of approving the small ones, Approvals is where you write the rules that clear them without you.
Connect your own AI
Your own assistant can read the workspace and draft changes into the same gate over MCP. Mint a key in Settings → MCP, point your client at the endpoint, and the scope on the key decides what it may do. The MCP reference has the surface, the scopes and the client setup, and Connector OAuth has the sign-in flow a Claude or ChatGPT style connector uses instead of a key.
Questions people ask first
What does Tempio do?
It connects your ad accounts into one org-scoped workspace. An agent, the one in Tempio or your own over MCP, reads performance, plans spend and writes each change as a change request. Nothing reaches a live account until the request is approved.
Do I have to use the built-in agent?
No. The same tools are served over MCP, so your own AI client can do the work from wherever you already run it. The agent in Tempio is there if you would rather not wire anything up.
Who approves a change?
You, or a rule you wrote. Both are recorded the same way, with the authority that cleared the change on the change request, so the record still answers the question months later. Drafts has the whole lifecycle.
What can an MCP key do?
What its scopes allow. Read, draft and approve are separate scopes, and a read-only key never sees the approve tools. You choose the scopes when you mint the key, the key is bound to the workspace you minted it in, and it stops working when the membership that made it ends. MCP keys covers minting and revoking.
Which AI clients can connect?
Any client that speaks MCP. You mint a key, point the client at your workspace, and the tools it sees are the scopes you gave the key. The MCP reference has the endpoint and the setup for each client.
Can a rule approve a change instead of me?
Yes, inside the limits you set for it, and the record says the rule cleared the change rather than a person. A rule never clears a change that creates something new; that one waits for a person. Approvals is where rules are written.
What is recorded about what an agent did?
Every draft, plan and connection action, scoped to your workspace. A change request keeps what was sent, what came back and which authority cleared it, so whether a change applied, and who cleared it, is answered on the change itself. Security says what else is logged.
Where to go next
- Connections — statuses, syncs, history and reconnecting
- Campaigns — what the campaign pages show and what a row can change
- Drafts — the gate, guardrails and the audit trail
- Plans — media plans, flighting and materialising a plan as drafts
- Settings — members, roles, invitations and per-connection permissions
- Troubleshooting — a connection that stops, a sync that fails, a grant in error