Set optimization targets
Give the copilot a spend goal, a ROAS floor, and a CPA band — the inputs that drive the plan and the safe-apply policy.
Targets are the account's objective. They shape the optimization plan, the recommendation feed, the copilot's
strategy, and — critically — the safe-apply policy that decides which changes auto-apply. Set them per account
in Settings → Optimization, or over MCP with gads_set_optimization_targets.
The four fields
| Field | Type | What it does |
|---|---|---|
| Daily spend goal | currency | The daily spend to scale toward. Doctrine: keep the budget roughly 1.2–1.5× your spend goal. |
| ROAS floor | ratio (default 1.5) | Minimum acceptable return on ad spend (150% → 1.5). Gates automatic budget raises — a raise only auto-applies on campaigns already above the floor. |
| CPA band (min) | currency | Informational lower bound on acceptable cost per acquisition. |
| CPA band (max) | currency | Upper bound on acceptable CPA. Gates trims and scaling decisions. |
Money fields are stored in micros (1,000,000 micros = one unit of your account currency); the form takes plain currency and converts for you. When no ROAS floor is set, the system defaults to 1.5.
How targets drive the system
The plan
gads_get_optimization_plan returns your targets, current pacing, and a ranked action feed (scale / improve / protect / reallocate).
The policy
The ROAS floor is a gate: budget raises above bounded limits only auto-apply when the campaign clears the floor.
Free audits are deliberately target-free — a prospect account has no targets, so audit scoring falls back to the 1.5 ROAS default. Targets matter for accounts you actively manage.
Set them over MCP
Ask your MCP client to set the targets, and it will call gads_set_optimization_targets:
Set the optimization targets for this account: €400/day spend goal, ROAS floor 2.0, CPA band €15–€40.Then quote pacing and CPA-vs-band whenever you ask for strategy — gads_get_optimization_plan reports both.