Advertising

Read the spend. Never change it without a person

Google Ads is read-only in Aestus. Three operations read campaigns and audience lists; the two that change what an account spends are refused.

Not open yetThe Google Ads integration is not yet available to external organizations. This guide describes the intended experience; availability will be updated when access is ready.

Join the waitlist See the Google Ads example

Google Ads with Aestus

Keep the tool. Change what the team can see.

Advertising is the place where an over-eager agent stops being an annoyance and starts being an invoice. So the position here is narrow on purpose. Nothing in Aestus changes a budget, a bid or a campaign state on its own. Those are writes, every write is held for a named person, and the person sees the value that would be replaced before agreeing to replace it.

Reading is the useful half and it is free of that problem. Yesterday's numbers against a recent baseline, which campaigns account for a move, and what the explanation actually rests on. A morning report built that way is worth having even if nothing it suggests is ever applied automatically, and it should say so plainly on the mornings when nothing changed.

What is not here yet is the built-in workflow. There is no ads use case in the catalog to switch on and no pinned operation list marking which calls are writes. The connection ships first so the pages that depend on it can be truthful, and so a team that wants the daily report before we build it can author the graph themselves.

Good first workflows

Check the account every morning
Report what moved against the recent baseline, and say when nothing did.
Explain a spike before reacting
Name the campaigns behind a change and show the numbers the explanation rests on.
Propose a change, never make it
The workflow writes the recommendation; the budget edit stays a person's approved action.

A complete Google Ads example, from trigger to proof.

The example names the people, task event, tool boundary, returned evidence, and acceptance state. The run row below it is a fixed product example, not customer data.

Example — fictional team and data. Not a live run or customer result.

Inside the connected tool

What the Google Ads connection gives you today

An org-owned account a reporting graph you author can read through. Every spend change stays a held decision.

meridian-ads · connectedConnection only

Runs without an approval

Read campaign performance for a day

Held for a named person

Change a budget, a bid or a campaign state

Not built yet

No Aestus Google Ads workflow and no pinned operation list yet.

Example — fictional team and data. Not a live run or customer result.

Concrete workflow example

Learn why yesterday's spend moved before anyone changes a bid

This is what the connection makes possible. Aestus ships no built-in Google Ads workflow yet, so today the connection is the part that exists.

TriggerA workflow you build reaches Google Ads through the connected account

1
Organization admin
Connects the Google Ads account in Settings, Integrations
The connection belongs to the organization, not to the person who happened to set it up.
connected · org-scoped
2
Aestus agent node
Reads yesterday's campaign performance
Reporting is a read. Nothing about a read can change a budget, a bid or a campaign state.
read-only · no gate
3
Aestus workflow
Compares the day with its own baseline
The comparison is arithmetic over the returned rows, and the rows are cited with the answer.
EXAMPLE-GA-01 · compared
4
Aestus
Keeps every spend change a human decision
Budgets, bids and campaign state are writes with real money behind them; they are gated.
budget · approval required

Example — fictional team and data. Not a live run or customer result.

Illustrative product example — not a production run

Explain yesterday's spend change

Example run		Runtime	Outcome
EXAMPLE-GA-01	Aestus workflow	aestus	Completed	$0.0186	25.9s

Tokens in / out: 8,300 / 580
Failure code: —
Agent: —

Illustrative Aestus workflow; actual costs and results vary

Example run cost

$0.0186 in the illustrative product example

A fixed illustration drawn from comparable Aestus workflow runs, not a measurement of an ads workflow that has run, because none ships yet. It stands for one daily check of 8,300 input tokens.

Set it up in four steps.

Follow the real Google Ads connection path. Provider steps link to the provider documentation. Aestus steps name the contract they follow.

01
Connect the advertising account
An organization admin connects it in Settings, Integrations, so the account belongs to the organization rather than to an individual.
Read the provider docs
02
Read Google's authorization model first
Google documents how access to an ads account is granted and which account the grant covers. Budgets make that worth reading before connecting.
Read the provider docs
03
Gate the toolkit at the organization
Whether a workflow may use the connection is a separate decision from whether somebody connected it, and it is set by policy.
Aestus product guide
04
Write the reporting graph
No ads use case ships in the catalog. Author the graph and seed it with the same loop every other workflow uses.
Aestus product guide

The boundary stays visible while the work moves.

See what Google Ads can do, where a person still decides, and what Aestus records for every governed run.

Where control lives

Reporting carries no risk

Pulling yesterday's performance cannot alter a bid, a budget or a campaign state, so it runs without holding anybody up.

Money cannot move at all

The two Google Ads operations that change an audience, and so change what an active campaign spends, are refused rather than held. An approval is a decision somebody makes in a hurry, and an ads account is the wrong place to learn that.

A recommendation is not an action

A workflow that writes down what it would change, and stops, is the honest shape for this until somebody agrees to more.

What Aestus records

The rows the conclusion rests on

An explanation of a spend change names the campaigns and figures behind it, so it can be checked rather than believed.

A quiet day said out loud

When nothing moved, the report says nothing moved. A watch that only speaks up on a spike is indistinguishable from one that has stopped.

Run economics

Tokens, latency, cost and failure code stay with the run, keeping the reporting bill visible next to the spend it reports on.

Questions teams ask

Could a workflow spend our money?

Not without somebody approving it. Budget, bid and campaign-state changes are writes, and a write is held for a named person who sees the value it would replace.

Is there a daily ads check we can enable?

Not yet. The connection is here so a page can name it and so you can build the graph; the built-in use case and its pinned tool list are still to come.

Why publish a guide before the workflow exists?

Because a use-case page may only name a connection a reader can go and set up, and because saying what is missing is more useful than leaving the gap unexplained.

See all integrations See the security controls

Start with one Google Ads run.

Bring one real run. Map its actors, boundary, evidence, cost, and acceptance step.

Talk to us

Read the spend. Never change it without a person

Google Ads is read-only in Aestus. Three operations read campaigns and audience lists; the two that change what an account spends are refused.

Not open yetThe Google Ads integration is not yet available to external organizations. This guide describes the intended experience; availability will be updated when access is ready.

Example — fictional team and data. Not a live run or customer result.

Concrete workflow example

Learn why yesterday's spend moved before anyone changes a bid

This is what the connection makes possible. Aestus ships no built-in Google Ads workflow yet, so today the connection is the part that exists.

TriggerA workflow you build reaches Google Ads through the connected account

1
Organization admin
Connects the Google Ads account in Settings, Integrations
The connection belongs to the organization, not to the person who happened to set it up.
connected · org-scoped
2
Aestus agent node
Reads yesterday's campaign performance
Reporting is a read. Nothing about a read can change a budget, a bid or a campaign state.
read-only · no gate
3
Aestus workflow
Compares the day with its own baseline
The comparison is arithmetic over the returned rows, and the rows are cited with the answer.
EXAMPLE-GA-01 · compared
4
Aestus
Keeps every spend change a human decision
Budgets, bids and campaign state are writes with real money behind them; they are gated.
budget · approval required

Example run

Runtime

Outcome

EXAMPLE-GA-01

Aestus workflow

aestus

Completed

$0.0186

25.9s

Questions teams ask

Could a workflow spend our money?

Not without somebody approving it. Budget, bid and campaign-state changes are writes, and a write is held for a named person who sees the value it would replace.

Is there a daily ads check we can enable?

Not yet. The connection is here so a page can name it and so you can build the graph; the built-in use case and its pinned tool list are still to come.

Why publish a guide before the workflow exists?

Because a use-case page may only name a connection a reader can go and set up, and because saying what is missing is more useful than leaving the gap unexplained.

Read the spend. Never change it without a person