Templates
Every template in @tempio/ui/components/templates/*, rendered from its fixture in @tempio/ui/fixtures/templates inside a container at most 1280px wide (max-w-7xl), with its name and its route pattern above it. A template is a pure function from an entry to a tree of blocks: it reads no manifest, no claims.ts and no route. Entry types live in @tempio/ui/components/templates/types; the four templates that need a client tool take it as a slot, and the fixtures pass a read-only rendering of one. Each stage also has a page of its own at /design/templates/<stage> (/design/templates/T4, for example), where the template fills the width of the window.
T1 HomeTemplate
@tempio/ui/components/templates/home · /
Every ad account you run, open to the agent you already use.
Your agent reads the numbers and drafts the change. It applies when you approve it, or when a rule you wrote does.
Every account, on one sheet
Campaigns
10 campaigns
| Campaign | Spend |
|---|---|
| Spring launch, prospecting | A$4,820.60 |
| Brand search | A$1,298.80 |
| Always-on video | A$2,103.00 |
| Retargeting, last 30 days | A$964.10 |
| Lookalike, top customers | A$1,547.20 |
| Competitor terms | A$613.40 |
| Creator spotlight | A$889.00 |
| Generic search terms | A$721.80 |
| Holiday gifting | A$382.50 |
| Winter clearance | A$0.00 |
Meta
Google Ads
TikTokEvery change is a draft first, and a record after.
The agent drafts. You approve it, or a rule you wrote does. The change request keeps the before, the after and the approval, so you can see what moved your spend.
See how the gate worksAsk, read the draft, approve, then write the rule
Ask for the change you want
Type it the way you’d say it. The agent reads the campaigns it touches and drafts the change as one request.
Read the draft before it applies
The change request lists each change, shows the ad as it will run and names the caps it was checked against.
Approve it, and it applies
The record keeps the before, the after and who approved it.
Write a rule for the changes you always approve
A draft inside the rule applies under it, and the record names the rule that approved it.
Change request drafted · Marlow feed ad · Headline, primary text and image · Awaiting approval
A tab for every account
One workspace for all of them
Each ad manager has its own login, its own numbers and its own idea of yesterday. A budget change happens in whichever tab was open.
- A login and a dashboard per platform
- Spend totals that never quite agree
- Edits made live, straight to the account
- No record of who changed what
Every account you connect reads into one set of numbers. A change starts as a draft and applies when you approve it, or when a rule you wrote does.
- One sign-in for every account
- Numbers counted the same way everywhere
- Drafts checked against your caps first
- Every change on the record
Before Tempio, and with it
With Tempio
Before
- Reporting
- With TempioOne set of numbers across every account.
- BeforeAn export per platform, pasted into a sheet.
- Changes
- With TempioA draft that applies when you approve it.
- BeforeAn edit made live in whichever tab was open.
- Guardrails
- With TempioSpend caps checked before anything applies.
- BeforeA budget alert after the money is spent.
- Rules
- With TempioApprovals you wrote once, applied the same way each time.
- BeforeSomeone remembering to check on Friday.
- The record
- With TempioWho changed what, when, and under which rule.
- BeforeWhatever the change history keeps that month.
What happened while you were out
Guardrails, approvals, pacing and sync report into one feed across every account you connect. Each line is on the record, with the rule or the person that cleared it.
Put your agent in the room
Connect an ad account, mint a scoped key, and let your own AI read the numbers and draft the work. Approve what it writes, or write the rule that approves it.
Request early access- No card. Early access is invite-only while the platform approvals land.
- Read and draft by default; approve is a separate permission you grant.
T2 PillarTemplate
@tempio/ui/components/templates/pillar · /product/{pillar}, /security, /product/mcp, /product/cli
The ads command center
Put frontier AI to work on every ad account you run.
Tempio's MCP hands your AI every account, every number and the tools to run them across Meta, Google Ads and TikTok.
Every change lands as a draft on the record and goes live when you approve it, or when a rule you wrote does.
Change request drafted · Marlow feed ad · Headline, primary text and image · Awaiting approval
No safe zone is drawn for this placement.
What a plan holds
Plans use the same account tree as the rest of the workspace, so a plan’s budgets and the live figures agree.
Timeline
One plan across every connected account. Budgets and dates sit on one timeline whatever channel they run on, each amount in its account’s own currency.
- Meta
- Google Ads
- TikTok
Your agent can draft the plan. Give the client you already use a brief and a scoped key. It writes the flight as drafts, and each one applies when you approve it or when a rule you wrote does.
Questions
Put your agent in the room
Connect an ad account, mint a scoped key, and let your own AI read the numbers and draft the work. Approve what it writes, or write the rule that approves it.
Request early access- No card. Early access is invite-only while the platform approvals land.
- Read and draft by default; approve is a separate permission you grant.
T2 PillarTemplate, from the fields before v3
@tempio/ui/components/templates/pillar · every pillar route until its entry carries featureTabs or twoUp
The ads command center
Put frontier AI to work on every ad account you run.
Tempio's MCP hands your AI every account, every number and the tools to run them across Meta, Google Ads and TikTok.
Every change lands as a draft on the record and goes live when you approve it, or when a rule you wrote does.
Bring your own AI
- Anthropic
- OpenAI
- Gemini
- Grok
- OpenClaw
- Kimi K3
Three dashboards, or one room
- Yesterday's spend lives in three tabs and none of them agree on the day boundary.
- A budget change is six clicks and no record of who asked for it.
- Your AI cannot see any of it, so you paste screenshots into a chat window.
- Currency is whatever each platform decided to show you.
Four surfaces, no ledger.
- One normalised account tree, one timezone, one set of base counts.
- A budget change is a draft with an author, a reviewer and a diff.
- Your AI reads the accounts over MCP and drafts the work in place.
- Money is minor units with its currency; a ratio with no denominator reads as a dash.
One surface, every change on the record.
Three moves from account to draft
- 01
Connect the account
Authorise the ad account once. Tempio pulls the account tree and the last ninety days of base counts into the workspace.
- 02
Point your agent at it
Mint a scoped key and add the MCP server to whichever client you already use. The tools appear; nothing else changes.
- 03
Approve what it drafts
The agent reads and writes drafts. A draft becomes a change when you approve it, or when a rule you wrote approves it.
What the workspace holds
One account tree
Every connected account, campaign, ad group and ad in one normalised shape, on one timezone, with one currency rule.
Base counts only
Impressions, clicks, spend and conversions are stored; CPC, CPM, CTR and ROAS are computed when you read them.
Drafts, not writes
A change is written as a draft against the account it targets, with the current value, the proposed value and the author on it.
Scoped keys
A key carries read, draft or approve. The embedded agent never holds approve, and a key dies with the membership that minted it.
An audit log
Every apply names the authority that cleared it, whether that was a person or a rule the org wrote.
How the gate worksIllustrative exchange
3 accounts · 41 campaigns · spend AUD 4,812.60 · CPC A$1.94 · ROAS —
Questions
Put your agent in the room
Connect an ad account, mint a scoped key, and let your own AI read the numbers and draft the work. Approve what it writes, or write the rule that approves it.
Request early access- No card. Early access is invite-only while the platform approvals land.
- Read and draft by default; approve is a separate permission you grant.
T3 ChannelTemplate
@tempio/ui/components/templates/channel · /channels/{platform}
Meta
Run Meta from whichever AI you already use
Connect your Meta ad accounts once and Tempio's MCP server hands your agent every campaign, ad set and ad in them — on one timezone, with money in minor units and its currency.
Reads are immediate. Writes are drafts: the change lands on the record with its current and proposed values, and applies when you approve it or when a rule you wrote does.
Change request drafted · Marlow feed ad · Headline, primary text and image · Awaiting approval
No safe zone is drawn for this placement.
The same account tree as every other channel. You report on it, plan it and draft changes to it beside the others, with each amount in the account’s own currency.
- Meta
Your own agent over MCP. Point the client you already use at the workspace. It reads this channel’s numbers and drafts changes with a key scoped to what you allow.
What your agent can do in these accounts
Read the account tree
Campaigns, ad sets and ads from every connected account, with up to ninety days of daily numbers.
Pause and resume
Pause an ad set or resume one, as a draft with the current status beside the proposed one.
Change a budget
A new daily or lifetime budget, kept within the spend caps you set.
Swap a creative
Point an ad at a new creative. The draft names the creative it replaces.
Break down by placement
Spend and results per placement, from the same daily numbers as the account totals.
Check the guardrails
Each draft lists the guardrails it passed and any it would break, before it can apply.
Three moves from account to draft
- 01
Connect the account
Authorise the ad account once. Tempio pulls the account tree and the last ninety days of base counts into the workspace.
- 02
Point your agent at it
Mint a scoped key and add the MCP server to whichever client you already use. The tools appear; nothing else changes.
- 03
Approve what it drafts
The agent reads and writes drafts. A draft becomes a change when you approve it, or when a rule you wrote approves it.
Questions
Put your agent in the room
Connect an ad account, mint a scoped key, and let your own AI read the numbers and draft the work. Approve what it writes, or write the rule that approves it.
Request early access- No card. Early access is invite-only while the platform approvals land.
- Read and draft by default; approve is a separate permission you grant.
T3 ChannelTemplate, from the fields before v3
@tempio/ui/components/templates/channel · every channel route until its entry carries twoUp or darkGrid
Meta
Run Meta from whichever AI you already use
Connect your Meta ad accounts once and Tempio's MCP server hands your agent every campaign, ad set and ad in them — on one timezone, with money in minor units and its currency.
Reads are immediate. Writes are drafts: the change lands on the record with its current and proposed values, and applies when you approve it or when a rule you wrote does.
Bring your own AI
- Anthropic
- OpenAI
- Gemini
- Grok
- OpenClaw
- Kimi K3
Also available
Three dashboards, or one room
- Yesterday's spend lives in three tabs and none of them agree on the day boundary.
- A budget change is six clicks and no record of who asked for it.
- Your AI cannot see any of it, so you paste screenshots into a chat window.
- Currency is whatever each platform decided to show you.
Four surfaces, no ledger.
- One normalised account tree, one timezone, one set of base counts.
- A budget change is a draft with an author, a reviewer and a diff.
- Your AI reads the accounts over MCP and drafts the work in place.
- Money is minor units with its currency; a ratio with no denominator reads as a dash.
One surface, every change on the record.
Illustrative exchange
3 accounts · 41 campaigns · spend AUD 4,812.60 · CPC A$1.94 · ROAS —
Illustrative exchange
Three moves from account to draft
- 01
Connect the account
Authorise the ad account once. Tempio pulls the account tree and the last ninety days of base counts into the workspace.
- 02
Point your agent at it
Mint a scoped key and add the MCP server to whichever client you already use. The tools appear; nothing else changes.
- 03
Approve what it drafts
The agent reads and writes drafts. A draft becomes a change when you approve it, or when a rule you wrote approves it.
| Tempio | Other MCP servers | The ad manager | |
|---|---|---|---|
| Your own AI reads the accounts | Yes | Yes | No |
| Your own AI writes campaigns, ad groups and ads | Yes | PartialRead tools, in the ones published so far | No |
| Every write lands on the record first | YesA draft with the current value, the proposed value and the authority that cleared it | No | PartialA change history, which is not an approval |
| Meta, Google Ads and TikTok in one account tree | Yes | No | One platform per login, one timezone per platform |
| Ratios | Base counts stored; CPC, CPM, CTR and ROAS computed at read time, and a dash where the denominator is zero | Whatever the platform returned | The platform's own rounding |
| Where they win | An ad manager carries the platform's newest surfaces the day that platform ships them; Tempio reaches them adapter by adapter, and says on the channel page which state each one is in. | ||
But I heard…
AI tools spend your budget while you sleep.
MCP servers only read; they cannot change anything.
Cross-platform numbers never reconcile.
Fixture copy standing in for a quote nobody has given yet. The block renders a card only when a named person has said it can be published and the page can say where they said it.
Source: fixture
Questions
Put your agent in the room
Connect an ad account, mint a scoped key, and let your own AI read the numbers and draft the work. Approve what it writes, or write the rule that approves it.
Request early access- No card. Early access is invite-only while the platform approvals land.
- Read and draft by default; approve is a separate permission you grant.
T4 IntegrationTemplate
@tempio/ui/components/templates/integration · /integrations/{agent}, /integrations/{agent}/{channel}
Claude Code
Claude Code, pointed at every ad account you run
Add Tempio's MCP server with a scoped key. The tools appear beside the ones you already have, and every connected Meta, Google Ads and TikTok account is there the moment they connect.
Read and draft come with the key. Approve is a separate permission, and the audit log names whichever of you cleared the change.
Bring your own AI
- Anthropic
- OpenAI
- Gemini
- Grok
- OpenClaw
- Kimi K3
Three moves from account to draft
- 01
Connect the account
Authorise the ad account once. Tempio pulls the account tree and the last ninety days of base counts into the workspace.
- 02
Point your agent at it
Mint a scoped key and add the MCP server to whichever client you already use. The tools appear; nothing else changes.
- 03
Approve what it drafts
The agent reads and writes drafts. A draft becomes a change when you approve it, or when a rule you wrote approves it.
Four of the tools the key opens
Each tool reads or writes the workspace you see in the app, so the numbers the agent quotes are the ones in your campaigns table.
Campaigns
10 campaigns
| Campaign | Spend |
|---|---|
| Spring launch, prospecting | A$4,820.60 |
| Brand search | A$1,298.80 |
| Always-on video | A$2,103.00 |
| Retargeting, last 30 days | A$964.10 |
| Lookalike, top customers | A$1,547.20 |
| Competitor terms | A$613.40 |
| Creator spotlight | A$889.00 |
| Generic search terms | A$721.80 |
| Holiday gifting | A$382.50 |
| Winter clearance | A$0.00 |
Claude Code holds a scoped key. It reads and drafts in the accounts the key covers, and approving stays a separate permission you grant.
- Claude Code
Campaigns, ad sets and ads sync in from each connected account. The agent reads them as one account tree, in the same shape as every other channel.
- Meta
Questions
Put your agent in the room
Connect an ad account, mint a scoped key, and let your own AI read the numbers and draft the work. Approve what it writes, or write the rule that approves it.
Request early access- No card. Early access is invite-only while the platform approvals land.
- Read and draft by default; approve is a separate permission you grant.
T4 IntegrationTemplate, from the fields before v3
@tempio/ui/components/templates/integration · every integration route until its entry carries featureTabs or twoUp
Claude Code
Claude Code, pointed at every ad account you run
Add Tempio's MCP server with a scoped key. The tools appear beside the ones you already have, and every connected Meta, Google Ads and TikTok account is there the moment they connect.
Read and draft come with the key. Approve is a separate permission, and the audit log names whichever of you cleared the change.
Bring your own AI
- Anthropic
- OpenAI
- Gemini
- Grok
- OpenClaw
- Kimi K3
Illustrative exchange
3 accounts · 41 campaigns · spend AUD 4,812.60 · CPC A$1.94 · ROAS —
Illustrative exchange
Three dashboards, or one room
- Yesterday's spend lives in three tabs and none of them agree on the day boundary.
- A budget change is six clicks and no record of who asked for it.
- Your AI cannot see any of it, so you paste screenshots into a chat window.
- Currency is whatever each platform decided to show you.
Four surfaces, no ledger.
- One normalised account tree, one timezone, one set of base counts.
- A budget change is a draft with an author, a reviewer and a diff.
- Your AI reads the accounts over MCP and drafts the work in place.
- Money is minor units with its currency; a ratio with no denominator reads as a dash.
One surface, every change on the record.
Three moves from account to draft
- 01
Connect the account
Authorise the ad account once. Tempio pulls the account tree and the last ninety days of base counts into the workspace.
- 02
Point your agent at it
Mint a scoped key and add the MCP server to whichever client you already use. The tools appear; nothing else changes.
- 03
Approve what it drafts
The agent reads and writes drafts. A draft becomes a change when you approve it, or when a rule you wrote approves it.
Fixture copy standing in for a quote nobody has given yet. The block renders a card only when a named person has said it can be published and the page can say where they said it.
Source: fixture
But I heard…
AI tools spend your budget while you sleep.
MCP servers only read; they cannot change anything.
Cross-platform numbers never reconcile.
Who this is for
A good fit if
- You run ad accounts on Meta, Google Ads or TikTok and you already work with an AI assistant.
- You want a change on the record before it is a change on the platform.
- You would rather write the rule that approves a change than approve the same change every morning.
Might not be a good fit if
- You want the platform's newest beta surface the week it ships; Tempio reaches it when the adapter does.
- You want an agent to spend without an approval or a rule behind it. There is no mode that does that.
- You run a single account and the ad manager already does everything you need.
| Tempio | Other MCP servers | The ad manager | |
|---|---|---|---|
| Your own AI reads the accounts | Yes | Yes | No |
| Your own AI writes campaigns, ad groups and ads | Yes | PartialRead tools, in the ones published so far | No |
| Every write lands on the record first | YesA draft with the current value, the proposed value and the authority that cleared it | No | PartialA change history, which is not an approval |
| Meta, Google Ads and TikTok in one account tree | Yes | No | One platform per login, one timezone per platform |
| Ratios | Base counts stored; CPC, CPM, CTR and ROAS computed at read time, and a dash where the denominator is zero | Whatever the platform returned | The platform's own rounding |
| Where they win | An ad manager carries the platform's newest surfaces the day that platform ships them; Tempio reaches them adapter by adapter, and says on the channel page which state each one is in. | ||
What the workspace holds
One account tree
Every connected account, campaign, ad group and ad in one normalised shape, on one timezone, with one currency rule.
Base counts only
Impressions, clicks, spend and conversions are stored; CPC, CPM, CTR and ROAS are computed when you read them.
Drafts, not writes
A change is written as a draft against the account it targets, with the current value, the proposed value and the author on it.
Scoped keys
A key carries read, draft or approve. The embedded agent never holds approve, and a key dies with the membership that minted it.
An audit log
Every apply names the authority that cleared it, whether that was a person or a rule the org wrote.
How the gate worksQuestions
Put your agent in the room
Connect an ad account, mint a scoped key, and let your own AI read the numbers and draft the work. Approve what it writes, or write the rule that approves it.
Request early access- No card. Early access is invite-only while the platform approvals land.
- Read and draft by default; approve is a separate permission you grant.
T5 AlternativeTemplate
@tempio/ui/components/templates/alternative · /alternatives/{competitor}
Tempio as an alternative to Fixture Ads Platform
Both put a layer over your ad accounts. One of them hands that layer to whichever AI you already use, and writes every change down before it happens.
This page is fixture copy for the gallery. The published pages carry figures and behaviour checked against the other product on the date in the strip above.
| Tempio | Fixture Ads Platform | |
|---|---|---|
| Where the work happens | In whichever AI you already use, over MCP | In its own dashboard |
| Your own AI reads the accounts | Yes | No |
| Every write lands on the record first | YesA draft with the current value, the proposed value and the authority that cleared it | PartialA change history, which is not an approval |
| Where they win | Fixture copy standing in for the row where the other side wins. The published page names the real one and sets it in this same type. | |
With Tempio, the AI you already use works in your ad accounts. It reads the numbers and drafts changes over MCP, and each draft applies when you approve it or a rule you wrote does.
Fixture Ads Platform keeps the work in its own dashboard. Someone opens it, reads the reports and makes each change by hand, one account at a time.
- What it is
- An ad management platform with its own dashboard and reports.
Where the two differ
Ratios
Tempio stores the counts and works out CPC, CPM, CTR and ROAS as you read them. Fixture Ads Platform saves each ratio on the day its report ran.
Keys for an agent
A key can read, draft or approve, and stops working when the membership that minted it ends. Fixture Ads Platform gives each person one login.
Rules that approve
A rule you wrote can approve a change, and the record names the rule beside it. In Fixture Ads Platform a change applies when someone with edit access saves it.
Currencies
Fixture Ads Platform converts every account into one reporting currency. In Tempio each account’s amounts stay in its own.
The account tree
Campaigns, ad groups and ads keep the nesting each channel gives them. Fixture Ads Platform lists every ad in one flat table per account.
Spend caps
Fixture Ads Platform sends a warning once a day’s spend passes a threshold. Tempio checks each draft against the caps you set before it can apply.
Where each product fits
Fixture copy for the concession. A page that cannot name a thing the other product does better is a page nobody believes, so the published version names one and sets it here, in body type, where it is read.
Who does the work
Fixture copy. A dashboard asks a person to open it; an MCP server answers whichever agent that person already has open. The difference shows up on the mornings nobody opens anything.
What happens to a change
Fixture copy. A draft carries the current value, the proposed value and the authority that cleared it, which is the part a change history does not have.
Questions
Put your agent in the room
Connect an ad account, mint a scoped key, and let your own AI read the numbers and draft the work. Approve what it writes, or write the rule that approves it.
Request early access- No card. Early access is invite-only while the platform approvals land.
- Read and draft by default; approve is a separate permission you grant.
T5 AlternativeTemplate, from the fields before v3
@tempio/ui/components/templates/alternative · every alternative route until its entry carries twoUp or darkGrid
Tempio as an alternative to Fixture Ads Platform
Both put a layer over your ad accounts. One of them hands that layer to whichever AI you already use, and writes every change down before it happens.
This page is fixture copy for the gallery. The published pages carry figures and behaviour checked against the other product on the date in the strip above.
| Tempio | Fixture Ads Platform | |
|---|---|---|
| Where the work happens | In whichever AI you already use, over MCP | In its own dashboard |
| Your own AI reads the accounts | Yes | No |
| Every write lands on the record first | YesA draft with the current value, the proposed value and the authority that cleared it | PartialA change history, which is not an approval |
| Where they win | Fixture copy standing in for the row where the other side wins. The published page names the real one and sets it in this same type. | |
Fixture copy standing in for a quote nobody has given yet. The block renders a card only when a named person has said it can be published and the page can say where they said it.
Source: fixture
Who does the work
Fixture copy. A dashboard asks a person to open it; an MCP server answers whichever agent that person already has open. The difference shows up on the mornings nobody opens anything.
What happens to a change
Fixture copy. A draft carries the current value, the proposed value and the authority that cleared it, which is the part a change history does not have.
Fixture copy for the concession. A page that cannot name a thing the other product does better is a page nobody believes, so the published version names one and sets it here, in body type, where it is read.
| Tempio | Fixture Ads Platform | |
|---|---|---|
| Meta, Google Ads and TikTok in one account tree | Yes | PartialFixture answer |
| Ratios | Base counts stored; CPC, CPM, CTR and ROAS computed at read time, and a dash where the denominator is zero | Fixture answer |
| Rules that approve a change without you | YesA rule you wrote, named on the record beside the change it cleared | No |
| Scoped keys for an agent | Read, draft or approve, and the key dies with the membership that minted it | Fixture answer |
Questions
Put your agent in the room
Connect an ad account, mint a scoped key, and let your own AI read the numbers and draft the work. Approve what it writes, or write the rule that approves it.
Request early access- No card. Early access is invite-only while the platform approvals land.
- Read and draft by default; approve is a separate permission you grant.
T6 CompetitorPricingTemplate
@tempio/ui/components/templates/competitor-pricing · /alternatives/{competitor}/pricing
How much does Fixture Ads Platform cost in 2026?
Their published plans as they stand on the date above, the costs the plan page does not carry, and where Tempio sits beside them.
This page is fixture copy for the gallery. A published version quotes only what the other party publishes, and says on which day it was read.
| Fixture Starter | Fixture Team | Fixture Scale | |
|---|---|---|---|
| What it costs | As published on their own pricing page on the date above | As published on their own pricing page on the date above | Quoted, not published |
| Seats included | Fixture answer | Fixture answer | Fixture answer |
| Ad accounts included | Fixture answer | Fixture answer | Fixture answer |
| Your own AI reads the accounts | No | No | No |
| Where they win | Fixture copy standing in for the tier where the other side is genuinely the cheaper answer. The published page names it and sets it in this same type. | ||
What the plan table leaves out
Minimum term
The team plan bills a year at a time. The monthly figure on the plan page is that year divided by twelve.
Accounts over the limit
Each ad account past the plan’s limit is a paid add-on, priced on a page apart from the plans.
Fees that follow spend
Above a set monthly ad spend, the fee becomes a share of what you spend, so the bill grows with the budget.
Setup
The scale plan opens with a paid onboarding period before the first account syncs.
Who takes a seat
Anyone who can open a report counts as a seat, a client who only reads included.
Cancelling
Cancelling stops the renewal at the end of the term, with no refund for the months left.
Questions
Put your agent in the room
Connect an ad account, mint a scoped key, and let your own AI read the numbers and draft the work. Approve what it writes, or write the rule that approves it.
Request early access- No card. Early access is invite-only while the platform approvals land.
- Read and draft by default; approve is a separate permission you grant.
T6 CompetitorPricingTemplate, from the fields before v3
@tempio/ui/components/templates/competitor-pricing · every competitor-pricing route until its entry carries darkGrid
How much does Fixture Ads Platform cost in 2026?
Their published plans as they stand on the date above, the costs the plan page does not carry, and where Tempio sits beside them.
This page is fixture copy for the gallery. A published version quotes only what the other party publishes, and says on which day it was read.
| Fixture Starter | Fixture Team | Fixture Scale | |
|---|---|---|---|
| What it costs | As published on their own pricing page on the date above | As published on their own pricing page on the date above | Quoted, not published |
| Seats included | Fixture answer | Fixture answer | Fixture answer |
| Ad accounts included | Fixture answer | Fixture answer | Fixture answer |
| Your own AI reads the accounts | No | No | No |
| Where they win | Fixture copy standing in for the tier where the other side is genuinely the cheaper answer. The published page names it and sets it in this same type. | ||
- Fixture copy. The per-seat line is the one people budget for; the connector fees and the minimum term are the ones they meet later.
- Fixture copy. An annual commitment quoted as a monthly figure is a year of spend written in the smaller of the two numbers.
- Fixture copy. The hours somebody spends moving numbers between the dashboard and the spreadsheet are a cost, and no plan page has ever carried them.
Questions
Put your agent in the room
Connect an ad account, mint a scoped key, and let your own AI read the numbers and draft the work. Approve what it writes, or write the rule that approves it.
Request early access- No card. Early access is invite-only while the platform approvals land.
- Read and draft by default; approve is a separate permission you grant.
T7 CompareTemplate
@tempio/ui/components/templates/compare · /compare/{a}-vs-{b}
Fixture Ads Platform vs Fixture Reporting Suite
One changes the spend and one explains it. This page says which job each does well, and what neither of them does.
Fixture copy for the gallery. A published comparison names both products' behaviour as checked on the date above.
| Fixture Ads Platform | Fixture Reporting Suite | |
|---|---|---|
| What it is for | Running the accounts | Reading what the accounts did |
| Writes to the ad account | Yes | No |
| Meta, Google Ads and TikTok in one view | PartialFixture answer | Yes |
| Priced by | Fixture answer | Fixture answer |
| Where they win | Fixture copy for the row where the first column is plainly the better answer. A comparison that never concedes one is a comparison nobody finishes. | |
Fixture Ads Platform is where the spend changes. Teams set budgets, bids and pauses inside it, one account at a time, and its reports cover only the accounts it runs.
- What it is
- A dashboard for running the accounts, one login at a time.
- Price
- As published on their own pricing page
Fixture Reporting Suite explains last week. It reads every account it is connected to and writes nothing back, so acting on a number still means opening the ad manager.
- What it is
- A reporting layer that reads what the accounts already did.
How the two work day to day
The account tree
Campaigns, ad sets and ads stay nested in the ads platform as each channel builds them, and the reporting suite flattens them into one row per campaign.
How often it syncs
The ads platform shows the live account each time you open it. The reporting suite syncs on a schedule, so its figures trail the account.
Where a change is recorded
In the ads platform’s change history, with the person who made it. The reporting suite shows the figures before and after.
Who can approve
In the ads platform, anyone with edit access applies a change as they make it. The ads platform has no approval step of its own, so a second pair of eyes is a review the team runs outside the tool.
What an agent can read
The reporting suite’s CSV exports, or the ads platform’s API with a developer token.
When the platform refuses
An error from the channel appears beside the field you edited in the ads platform; the reporting suite marks the sync failed and keeps its last figures.
Where both stop and which one fits
Fixture copy. Both of them stop at the browser: somebody still has to open a tab, read the number and decide what to do about it, and neither will hand that job to the AI already open beside them.
Fixture copy. A team changing budgets daily wants the first; a team reporting to somebody else monthly wants the second; a team doing both is buying two subscriptions to answer one question.
Questions
Put your agent in the room
Connect an ad account, mint a scoped key, and let your own AI read the numbers and draft the work. Approve what it writes, or write the rule that approves it.
Request early access- No card. Early access is invite-only while the platform approvals land.
- Read and draft by default; approve is a separate permission you grant.
T7 CompareTemplate, from the fields before v3
@tempio/ui/components/templates/compare · every compare route until its entry carries twoUp or darkGrid
Fixture Ads Platform vs Fixture Reporting Suite
One changes the spend and one explains it. This page says which job each does well, and what neither of them does.
Fixture copy for the gallery. A published comparison names both products' behaviour as checked on the date above.
| Fixture Ads Platform | Fixture Reporting Suite | |
|---|---|---|
| What it is for | Running the accounts | Reading what the accounts did |
| Writes to the ad account | Yes | No |
| Meta, Google Ads and TikTok in one view | PartialFixture answer | Yes |
| Priced by | Fixture answer | Fixture answer |
| Where they win | Fixture copy for the row where the first column is plainly the better answer. A comparison that never concedes one is a comparison nobody finishes. | |
Where the work happens
Fixture copy. One of them is where the spend is changed and the other is where last week is explained, which is why teams end up paying for both and calling it a stack.
What you are actually buying
Fixture copy. A seat in a dashboard and a scheduled report are different purchases, and the invoice is the only place they look alike.
Fixture copy. Both of them stop at the browser: somebody still has to open a tab, read the number and decide what to do about it, and neither will hand that job to the AI already open beside them.
Fixture copy. A team changing budgets daily wants the first; a team reporting to somebody else monthly wants the second; a team doing both is buying two subscriptions to answer one question.
Or point your own AI at the accounts
Tempio is the third answer: Meta, Google Ads and TikTok in one account tree, read by whichever AI you already use, with every write landing on the record as a draft first.
Request early access- Read and draft by default; approve is a separate permission.
Questions
Put your agent in the room
Connect an ad account, mint a scoped key, and let your own AI read the numbers and draft the work. Approve what it writes, or write the rule that approves it.
Request early access- No card. Early access is invite-only while the platform approvals land.
- Read and draft by default; approve is a separate permission you grant.
T8 TermTemplate
@tempio/ui/components/templates/term · /glossary/{term}
Return on ad spend (ROAS)
Return on ad spend is the revenue attributed to a campaign divided by what that campaign cost. A ROAS of 3 means three units of revenue for every unit spent.
ROAS = attributed revenue ÷ ad spend
- attributed revenue
- Revenue the platform or your own analytics assigns to the campaign, inside its attribution window.
- ad spend
- What the campaign cost over the same window, in the account's own currency.
Work it out with the calculator
What the number is telling you
ROAS is a ratio, so it moves when either side moves. A campaign whose revenue held steady while spend fell has a higher ROAS and a smaller business behind it.
Where it goes wrong
A ROAS with no revenue in the window is undefined, not zero. Fixture copy: the rendered pages carry the sourced version.
ROAS depends on how the conversions were counted. A seven-day click window and a one-day view window give the same campaign two different figures, so compare a ROAS only with one counted the same way.
- The attribution window
- Which conversions count
- The currency revenue is reported in
Break-even ROAS comes from your margin. Divide one by your gross margin. At a 40% margin the account needs a ROAS of 2.5 before the spend pays for itself.
Break-even ROAS = 1 ÷ gross margin
More free tools
Questions
Put your agent in the room
Connect an ad account, mint a scoped key, and let your own AI read the numbers and draft the work. Approve what it writes, or write the rule that approves it.
Request early access- No card. Early access is invite-only while the platform approvals land.
- Read and draft by default; approve is a separate permission you grant.
T8 TermTemplate, from the fields before v3
@tempio/ui/components/templates/term · every term route until its entry carries twoUp
Return on ad spend (ROAS)
Return on ad spend is the revenue attributed to a campaign divided by what that campaign cost. A ROAS of 3 means three units of revenue for every unit spent.
ROAS = attributed revenue ÷ ad spend
- attributed revenue
- Revenue the platform or your own analytics assigns to the campaign, inside its attribution window.
- ad spend
- What the campaign cost over the same window, in the account's own currency.
Work it out with the calculator
What the number is telling you
ROAS is a ratio, so it moves when either side moves. A campaign whose revenue held steady while spend fell has a higher ROAS and a smaller business behind it.
Where it goes wrong
A ROAS with no revenue in the window is undefined, not zero. Fixture copy: the rendered pages carry the sourced version.
More free tools
Questions
Put your agent in the room
Connect an ad account, mint a scoped key, and let your own AI read the numbers and draft the work. Approve what it writes, or write the rule that approves it.
Request early access- No card. Early access is invite-only while the platform approvals land.
- Read and draft by default; approve is a separate permission you grant.
T9 CalculatorTemplate
@tempio/ui/components/templates/calculator · /tools/{calculator}
ROAS calculator
Revenue over spend, and the figure the account has to clear before it pays for itself.
Return on ad spend
- ROAS
- 4
- Break-even ROAS
- —
- ROAS is attributed revenue divided by ad spend, inside the same attribution window.
- Break-even ROAS is one divided by your gross margin, which is why the margin input is the one that decides whether the first number is good news.
- A ratio with no denominator is a dash, never a zero.
What each platform counts as revenue
| Platform | What it counts | Where the number comes from |
|---|---|---|
| Meta | Purchases inside the attribution window | The platform's own reporting |
| Google Ads | Conversions at the value you sent with them | The platform's own reporting |
| TikTok | Purchases inside the attribution window | The platform's own reporting |
ROAS is attributed revenue divided by ad spend. A ROAS of 4.0 means the ads brought in four times what they cost, counted inside one attribution window.
ROAS = revenue ÷ spend
It leaves out what each sale cost you. Two accounts on the same ROAS can sit either side of break-even. Break-even ROAS is one divided by your gross margin.
- Cost of goods
- Returns and refunds
- Sales outside the attribution window
Questions
More free tools
Put your agent in the room
Connect an ad account, mint a scoped key, and let your own AI read the numbers and draft the work. Approve what it writes, or write the rule that approves it.
Request early access- No card. Early access is invite-only while the platform approvals land.
- Read and draft by default; approve is a separate permission you grant.
T9 CalculatorTemplate, from the fields before v3
@tempio/ui/components/templates/calculator · every calculator route until its entry carries twoUp
ROAS calculator
Revenue over spend, and the figure the account has to clear before it pays for itself.
Return on ad spend
- ROAS
- 4
- Break-even ROAS
- —
- ROAS is attributed revenue divided by ad spend, inside the same attribution window.
- Break-even ROAS is one divided by your gross margin, which is why the margin input is the one that decides whether the first number is good news.
- A ratio with no denominator is a dash, never a zero.
What each platform counts as revenue
| Platform | What it counts | Where the number comes from |
|---|---|---|
| Meta | Purchases inside the attribution window | The platform's own reporting |
| Google Ads | Conversions at the value you sent with them | The platform's own reporting |
| TikTok | Purchases inside the attribution window | The platform's own reporting |
What this works out
Attributed revenue divided by ad spend, inside one attribution window. The second output is the ROAS the account has to clear before the spend pays for itself, which is one divided by your gross margin.
Why the answer is sometimes a dash
A ratio with no denominator is undefined, and a zero in its place is a number nobody computed. Leave the margin empty and the break-even figure stays a dash rather than becoming a claim.
Questions
More free tools
Put your agent in the room
Connect an ad account, mint a scoped key, and let your own AI read the numbers and draft the work. Approve what it writes, or write the rule that approves it.
Request early access- No card. Early access is invite-only while the platform approvals land.
- Read and draft by default; approve is a separate permission you grant.
T10 SafeZoneTemplate
@tempio/ui/components/templates/safe-zone · /tools/safe-zones/{platform}
Meta safe zones
Upload a creative and see which part of it the interface covers, in every placement it can run in.
TempioAll your ad accounts in one place
Ask where the spend went this week and get the answer with the numbers behind it.
Keep text and logos inside the dashed line. The platform’s interface covers the rest.
| Feed | Stories | Reels | |
|---|---|---|---|
| Top of the frame | The profile row and the menu | The progress bars and the account name | Nothing, on the frame itself |
| Bottom of the frame | The headline and the call to action | The reply bar and the call to action | The caption, the sound row and the call to action |
| Right edge | Nothing | Nothing | The reaction column, top to bottom of the lower half |
Templates for this platform
Questions
More free tools
Put your agent in the room
Connect an ad account, mint a scoped key, and let your own AI read the numbers and draft the work. Approve what it writes, or write the rule that approves it.
Request early access- No card. Early access is invite-only while the platform approvals land.
- Read and draft by default; approve is a separate permission you grant.
T10 SafeZoneTemplate, from the fields before v3
@tempio/ui/components/templates/safe-zone · every safe-zone route until its entry carries placementPreview
Meta safe zones
Upload a creative and see which part of it the interface covers, in every placement it can run in.
Fixture slot. The route renders its own upload-and-overlay checker here.
| Feed | Stories | Reels | |
|---|---|---|---|
| Top of the frame | The profile row and the menu | The progress bars and the account name | Nothing, on the frame itself |
| Bottom of the frame | The headline and the call to action | The reply bar and the call to action | The caption, the sound row and the call to action |
| Right edge | Nothing | Nothing | The reaction column, top to bottom of the lower half |
Templates for this platform
Questions
More free tools
Put your agent in the room
Connect an ad account, mint a scoped key, and let your own AI read the numbers and draft the work. Approve what it writes, or write the rule that approves it.
Request early access- No card. Early access is invite-only while the platform approvals land.
- Read and draft by default; approve is a separate permission you grant.
T11 AdPreviewTemplate
@tempio/ui/components/templates/ad-preview · /tools/ad-preview/{platform}
Meta ad preview
Your creative, your headline and your call to action, rendered in the placement they will run in.
TempioAsk where the spend went this week and get the answer with the numbers behind it.
All your ad accounts in one place
Learn moreNo safe zone is drawn for this placement.
Three moves from account to draft
- 01
Connect the account
Authorise the ad account once. Tempio pulls the account tree and the last ninety days of base counts into the workspace.
- 02
Point your agent at it
Mint a scoped key and add the MCP server to whichever client you already use. The tools appear; nothing else changes.
- 03
Approve what it drafts
The agent reads and writes drafts. A draft becomes a change when you approve it, or when a rule you wrote approves it.
Questions
More free tools
Put your agent in the room
Connect an ad account, mint a scoped key, and let your own AI read the numbers and draft the work. Approve what it writes, or write the rule that approves it.
Request early access- No card. Early access is invite-only while the platform approvals land.
- Read and draft by default; approve is a separate permission you grant.
T11 AdPreviewTemplate, from the fields before v3
@tempio/ui/components/templates/ad-preview · every ad-preview route until its entry carries placementPreview
Meta ad preview
Your creative, your headline and your call to action, rendered in the placement they will run in.
Fixture slot. The route renders its own drag-and-drop preview here.
- Facebook Feed
- Instagram Feed
- Instagram Stories
- Facebook Reels
- Audience Network
Three moves from account to draft
- 01
Connect the account
Authorise the ad account once. Tempio pulls the account tree and the last ninety days of base counts into the workspace.
- 02
Point your agent at it
Mint a scoped key and add the MCP server to whichever client you already use. The tools appear; nothing else changes.
- 03
Approve what it drafts
The agent reads and writes drafts. A draft becomes a change when you approve it, or when a rule you wrote approves it.
Questions
More free tools
Put your agent in the room
Connect an ad account, mint a scoped key, and let your own AI read the numbers and draft the work. Approve what it writes, or write the rule that approves it.
Request early access- No card. Early access is invite-only while the platform approvals land.
- Read and draft by default; approve is a separate permission you grant.
T12 ExamplesTemplate
@tempio/ui/components/templates/examples · /examples/{vertical}, /examples/{vertical}/{channel}
Ecommerce ad examples on Meta
Creative that ran, in the placements it ran in, with the part the interface covers marked on each one.
Fixture slot. The route renders its own format and channel filter here.
Ecommerce ads running on Meta
Meta, single image
ImageOne image, one headline, one destination, with the safe zones drawn on top of it.
Fixture entry
Google Ads, responsive search
Fifteen headlines and four descriptions, and which combinations the platform is allowed to build.
Fixture entry
TikTok, in-feed video
Nine by sixteen, with the caption and the interface chrome overlaid where they land.
Fixture entry, no destination yet
Put your own ads next to these
Every view reads the accounts you’ve connected, so you compare these examples with the ads running now.
Campaigns
10 campaigns
| Campaign | Spend |
|---|---|
| Spring launch, prospecting | A$4,820.60 |
| Brand search | A$1,298.80 |
| Always-on video | A$2,103.00 |
| Retargeting, last 30 days | A$964.10 |
| Lookalike, top customers | A$1,547.20 |
| Competitor terms | A$613.40 |
| Creator spotlight | A$889.00 |
| Generic search terms | A$721.80 |
| Holiday gifting | A$382.50 |
| Winter clearance | A$0.00 |
Questions
Put your agent in the room
Connect an ad account, mint a scoped key, and let your own AI read the numbers and draft the work. Approve what it writes, or write the rule that approves it.
Request early access- No card. Early access is invite-only while the platform approvals land.
- Read and draft by default; approve is a separate permission you grant.
T12 ExamplesTemplate, from the fields before v3
@tempio/ui/components/templates/examples · every examples route until its entry carries featureTabs
Ecommerce ad examples on Meta
Creative that ran, in the placements it ran in, with the part the interface covers marked on each one.
Fixture slot. The route renders its own format and channel filter here.
Ecommerce ads running on Meta
Meta, single image
ImageOne image, one headline, one destination, with the safe zones drawn on top of it.
Fixture entry
Google Ads, responsive search
Fifteen headlines and four descriptions, and which combinations the platform is allowed to build.
Fixture entry
TikTok, in-feed video
Nine by sixteen, with the caption and the interface chrome overlaid where they land.
Fixture entry, no destination yet
What the good ones have in common
Fixture copy. The offer is legible in the first second, the brand is legible in the first frame, and the call to action says what happens next rather than what the company would like.
What the interface covers
Fixture copy. Every one of these was laid out around the furniture the placement puts on top of it, which is the difference between a design and a design that ran.
Other verticals
Questions
Put your agent in the room
Connect an ad account, mint a scoped key, and let your own AI read the numbers and draft the work. Approve what it writes, or write the rule that approves it.
Request early access- No card. Early access is invite-only while the platform approvals land.
- Read and draft by default; approve is a separate permission you grant.
T13 GuideTemplate
@tempio/ui/components/templates/guide · /guides/{slug}, /blog/{slug}, /templates/{artifact}
Running one launch across Meta, Google Ads and TikTok
Anthony Tirrizzi9 min read
One brief, three platforms, one account tree — and the drafts that put the plan into all three without anybody retyping it.
Start with one brief, not three plans
Fixture copy. The plan is the object; the three platforms are where it lands. Writing it once and materialising it three times is the difference between a launch and three launches that share a name.
Budgets and dates in one place
Fixture copy. Money is an integer in minor units with its currency beside it, and a date is a date in the account's own timezone. Both of those are decided once, in the plan, rather than three times in three interfaces.
What happens before anything changes
Fixture copy. Every write lands on the record first, with the current value, the proposed value and the authority that cleared it — you, or a rule you wrote.
One plan holds the budgets and dates for every channel. Each line item becomes a draft in the account it belongs to, so all three channels start from the same numbers.
- Meta
- Google Ads
- TikTok
Each draft is on the record before it applies. It applies when you approve it or a rule you wrote does, and the record keeps who cleared it.
- The current value
- The proposed value
- Who or what approved it
More free tools
Questions
Put your agent in the room
Connect an ad account, mint a scoped key, and let your own AI read the numbers and draft the work. Approve what it writes, or write the rule that approves it.
Request early access- No card. Early access is invite-only while the platform approvals land.
- Read and draft by default; approve is a separate permission you grant.
T13 GuideTemplate, from the fields before v3
@tempio/ui/components/templates/guide · every guide route until its entry carries twoUp
Running one launch across Meta, Google Ads and TikTok
Anthony Tirrizzi9 min read
One brief, three platforms, one account tree — and the drafts that put the plan into all three without anybody retyping it.
Start with one brief, not three plans
Fixture copy. The plan is the object; the three platforms are where it lands. Writing it once and materialising it three times is the difference between a launch and three launches that share a name.
Budgets and dates in one place
Fixture copy. Money is an integer in minor units with its currency beside it, and a date is a date in the account's own timezone. Both of those are decided once, in the plan, rather than three times in three interfaces.
What happens before anything changes
Fixture copy. Every write lands on the record first, with the current value, the proposed value and the authority that cleared it — you, or a rule you wrote.
More free tools
Questions
Put your agent in the room
Connect an ad account, mint a scoped key, and let your own AI read the numbers and draft the work. Approve what it writes, or write the rule that approves it.
Request early access- No card. Early access is invite-only while the platform approvals land.
- Read and draft by default; approve is a separate permission you grant.