AI Growth Marketer
Approvals and Limits
Every change to a live account is staged as a proposal and waits for a person. This page is the complete list of what that covers. For how that boundary is enforced, and how you will be able to set it per class of action, see write permissions.
What needs an approval
| Change | Example |
|---|---|
| Creating campaigns, ad groups or ads | Launching a new search campaign |
| Budgets and bids | Raising a daily budget, changing a target CPA |
| Keywords and negatives | Adding negatives from search terms |
| Audiences and targeting | Building a remarketing audience |
| Creative going live | Uploading and publishing new ads |
| Turning things on or off | Pausing a tired ad |
| Tracking changes | Publishing a tag container, marking a key event |
| Store changes | Creating products, collections or pages |
Video is past its saturation point while TikTok prospecting sits on the steep part of its response curve. This shifts the budget across five campaigns — net weekly spend unchanged.
Video_Prospecting_NAcampaign-25%- Video_Prospecting_EUcampaign-25%
- Video_Retargeting_NAcampaign-50%
Prospecting_Broad_NAcampaign+40%- Prospecting_Interest_EUcampaign+40%
- Net weekly budget change$0
What does not need an approval
Work that changes nothing outside Maxma: reading accounts, joining and analysing data, writing reports, drafting copy, generating creative that has not been published, and preparing proposals.
Three things change something outside Maxma without a proposal, so they are worth knowing about:
- Sending a message. Slack messages and emails go out when the work is done. Recipients come from the workflow or the run, never from the model.
- Publishing a campaign page in your store. Products and collections are proposed, but a landing page is built and published directly.
- Writing to Google Drive. Creating a folder and exporting a finished asset into your workspace folder.
What a proposal contains
- The exact change, at the level the platform applies it.
- Why it is being proposed, with the numbers behind it.
- What is expected to happen, and what the agent will do if that does not happen.
Rejecting
Rejecting stops the change. The agent does not re-propose the same change automatically, and the rejection informs later work. Nothing executes because time passed; a proposal that is never answered is never applied.
Who can approve
Access is per workspace, and each brand, account or client gets its own. Anyone who is a member of a workspace can approve its proposals. If two people answer the same proposal at once, the first wins and the second is told it has already been handled.
A proposal can also be approved in part: you can accept some of the changes in it and leave the rest.
Limits worth knowing
- The agent works only in the accounts you connect, and only through the platform APIs.
- Read-only connections stay read-only: if a connection has no write access, the agent can analyse that platform but not change it.
- Every proposal is validated against the platform before you see it, so an approval applies a change the platform has already accepted as valid.
- If one change in a proposal fails while applying, the ones already applied are rolled back.
- A proposal carries a snapshot of what it expects to find. If the account has moved on since, the change is not applied blindly.
- There is no spend ceiling enforced in the product itself. What limits spend is that every budget change waits for a person, and the budgets you set on the platform.