Platforms
Tempio connects six ad platforms. Three are covered in full: Tempio syncs their campaigns, ad groups, ads and daily numbers, and drafts modelled changes on them. Three are connect-only: Tempio holds the sign-in, lists the ad accounts, and carries raw requests to the platform's own API through the escape hatch. Each platform has its own page; this one is the map.
| Platform | Coverage | What Tempio does there |
|---|---|---|
| Meta | Full | Facebook and Instagram through one ad account: entities, daily numbers and modelled drafts |
| Full | One customer account holding campaigns, ad groups, ads, keywords and Performance Max asset groups | |
| TikTok | Full | One advertiser account under a Business Center |
| Connect-only | Ad accounts under your Reddit businesses, and raw requests to the Reddit Ads API | |
| X Ads | Connect-only | X Ads accounts with a funding source, over OAuth 1.0a, and signed raw requests to the X Ads API |
| Microsoft Advertising | Connect-only | Accounts under each customer the login holds a role in, and raw requests to the five service hosts |
A connect-only connection reads no campaigns and no daily numbers, so it adds nothing to Campaigns, Metrics, the planner or the account brief. A raw read runs at once and returns the platform's own answer, unnormalised; a raw change is drafted with a sentence and waits at the gate for a person with approval rights on the connection, because no approval rule can clear one. Raw requests start off, and a workspace owner turns them on in Settings → Raw platform requests.
What is the same everywhere
On the three full-coverage platforms, the shape of the product does not change:
- Connecting is the platform's own sign-in, then a picker of the ad accounts that login can reach, then a choice of how much history to load (Connections). A connect-only platform uses the same sign-in and picker and loads no history.
- Reading lands in one normalised model — campaign, ad group, ad — with daily base counts per entity, and every ratio computed when you look (Metrics).
- Writing is a change request first, whatever wrote it, applied when it is approved — by you, or by a rule you wrote.
- Guardrails are Tempio's, not the platform's, and they are identical on all three (Guardrails).
- Money is integer minor units in the ad account's own currency, stamped from the account rather than read from whatever asked for the change.
An approved change reaches a customer ad account once that platform has granted Tempio write access, and each platform's page says where that stands.
What does change is what each platform can express, and Tempio does not paper over it. A row's menu is the intersection of what the platform implements at that level and what the operation means there — so a Google ad group offers no budget edit, because a Google budget attaches to the campaign. An operation a platform cannot express is not drafted at all, rather than drafted and refused later.
The differences worth knowing
Between the three full-coverage platforms:
| Meta | TikTok | ||
|---|---|---|---|
| Ad group is called | Ad set | Ad group | Ad group |
| Budgets attach to | Campaign or ad set | Campaign only | Campaign or ad group |
| A create lands | Paused | Paused | Disabled |
| Archiving | Yes — and it is undoable | No archive; removal instead | No archive; removal instead |
| Removing | Not offered | Permanent. The entity is gone | Permanent. The entity is gone |
| Renaming an ad | Yes | No — a responsive search ad's name is not settable | Yes |
| A dry run before the change is sent | No | Yes | No |
| Objectives | Meta's own list | Not restricted by Tempio | TikTok's own list |
| Trailing window re-read on every sync | 28 days | 30 days | 14 days |
Two rows there are worth reading twice.
Removal is irreversible on Google and TikTok. It is not an archive under another name: the entity is gone on the platform and nothing in Tempio brings it back, which is why a removal at the gate says so in a sentence before you approve it, and why it has no undo.
Every create lands paused or disabled. Approving a create builds the structure without spending anything. Going live is a second change through the same gate, deliberately — so nothing starts spending on the same click that made it.
Which platform a page is about
The pages above are per platform because that is where the answers differ: which objectives a create accepts, which fields a change may touch, what the platform does with a media asset, how it counts money and time, and which drafts it refuses before they are sent. If a change is being refused and you want to know whether it is Tempio or the platform saying no, that page is the place to look.
Connecting an account on a platform whose card reads Not yet enabled is not possible yet; the card stays visible rather than disappearing, so what is present is legible.