Welcome to Tempio
Getting started
Tempio is an AI ads command center. Connect your ad accounts and they land in one normalized, org-scoped workspace. From there your own AI (over MCP) or the in-app agent reads performance, plans spend, and drafts campaign changes as change requests you can read and diff. Every change is a draft on the record before it is a change; it is applied when approved, by you or by a rule you wrote.
New here? Getting started walks the first run: naming a workspace, connecting an account, choosing how much history to pull, and what lands while the first sync runs. It ends on the questions people ask first: who approves a change, what a key can do, and what is recorded.
Running your accounts
- Connections — connecting an ad account, what the first sync does, and what each status means
- Campaigns — what the campaign pages show, what a row can change, and the batch that drafts a campaign, its ad group and its ad together
- Drafts — how a change request is written, batched, guarded, approved and applied, and how it is undone
- Guardrails — the caps a budget change is held to, and the three moments each one is checked
- Plans — media plans, their items and flights, and what materializing one turns it into
- Media — the image and video library, what an upload
records, the one
upload_mediadraft that hands a file to a platform, and what each of the four statuses means - Ad library — the corpus of other people's ads from the public transparency archives, what coverage means, tracking and the swipe file
Reading the numbers
- Metrics — what is stored, what is computed when you look, why a ratio can be blank, and how currencies are handled
- The agent — the chat inside Tempio: what it reads, what it can draft, why it never approves, and how its messages are metered
- Platforms — what each connection reads, writes and refuses: Meta, Google, TikTok
Running the workspace
- Settings — the one home: the workspace, members and seats, billing, approvals, guardrails, access, MCP keys, raw platform requests, your appearance and your account
- Approvals — the rules that clear a change without you, what a rule never approves, and the chains that hold a change until several people have signed
- Account defaults — the values each platform reads off an ad account, changed as a draft like every other change
- Billing — plans and what each includes, what a metered message is, and how the allowance and prepaid packs are spent
- Security — where credentials live, how a workspace is isolated, what is on the record, and what is not true yet
- Troubleshooting — reading a connection's health line, a failed sync, a grant in error, a draft that stops
Connecting your own AI
- MCP reference — the tool surface, scopes, the result envelope and client setup
- MCP keys — minting a key, what each scope unlocks, and revoking one
- Connector OAuth — how a client that cannot send a header signs in instead
- CLI — the same scoped surface from the terminal
For builders
- Design system — tokens, brand and components, rendered
live from the
@tempio/uipackage