Writing on ads and agents
A post here takes a position and gives you what you need to disagree with it. Some of them explain a decision inside the product and why the alternative was rejected; some take a phrase that gets used loosely in advertising software and say what it would have to mean to be true.
What you will not find is release notes dressed as thinking, or a number without the page it came from. Every post carries the date it was published, the date it was last changed, and a byline that resolves to somebody accountable for it.
Every post
A week of ad changes on the record
What a week looks like when every change carries its own before state and authority: five questions that become lookups instead of investigations.
An agent with your ad account
The useful question is not what an agent can do with your accounts. It is what it cannot do, and whether that limit is a policy or a property of the system.
MCP is a contract, not a feature
Supporting a protocol is a line on a comparison table. What makes it useful is what the server refuses, what it derives, and what a caller cannot name.
Reading a change request like a diff
The habit that makes review fast is borrowed from code: read what it changes from, not what it changes to, and read the group before any single row.
The case against the autopilot toggle
A switch with two positions asks the wrong question. Autonomy is not a level to set once; it is a property of each change, with a direction and a distance.
The cost of three dashboards
The cost is not the tab-switching. It is that no number in one is comparable with a number in another, and the reconciliation lives in somebody's head.
The numbers your dashboard rounds off
Five roundings that happen before you see a figure: a blank turned into a zero, reach summed, currencies added, a partial day, and a restated week.
What a media plan is for
Not for predicting the quarter. For being wrong about it cheaply, in a document where a line costs a keystroke instead of a day of spend.
What an approval policy should say
Most approval policies name people and hope. A useful one names a direction, a ceiling and a distance, and refuses to be written any wider than that.
What we refuse to claim, and why
A list of things this site will not say, enforced by the build rather than by good intentions, and the argument for making refusals mechanical.
Why ratios belong at read time
A stored rate can disagree with the numbers underneath it, and nothing will tell you which one is wrong. Computing at read time removes the failure entirely.
Why every change is a draft
A change request is the smallest unit that carries an authority, a before state and an inverse. That is the argument for making it the only unit.
Who writes these
Questions
Put frontier AI to work on every ad account you run.
Tempio connects your ad accounts into one workspace and hands your own AI the numbers and the tools. Every change it writes is a draft until you approve it, or until a rule you wrote does.
Request early access- Read and draft by default. Approve is a separate permission you grant.