# Your First Week With an AI Google Ads Agent

A day-by-day playbook for the first seven days with an AI Google Ads agent: read-only questions, then zero-spend writes, then approved spend changes.

Tutorials · Published 2026-08-10, updated 2026-11-05.

> Spend your first week with an ads agent in three stages: days 1–2 read-only — account overview, wasted spend, search terms; days 3–4 writes that cannot spend — negative keywords, paused campaign drafts; day 5 onward, spend changes with approval — budgets, bids, statuses. By day 7 you know how the agent reasons, and it has earned the level of trust it actually holds.

The first week with an AI Google Ads agent has a right shape: read
everything, change nothing, then make writes that cannot spend, then — only
once you have watched it reason — approve changes that move money. By day 7
you will point a specialist at the account and watch it do expert work in
seconds, on your command — but that trust is earned, not assumed. This
playbook gives you the seven days, the prompts for each, and the checkpoint
that tells you when to advance.

Its first five days fit inside AdCopilot's trial — five days on the full Pro plan for your first workspace — but the staging is not a product limitation. AdCopilot proposes each change first from minute one, and your AI client asks before it runs as long as it is set to ask before AdCopilot's write tools. The staging is how *you* build a
justified opinion of the agent, the same way
[autonomy is earned in levels](https://adcopilot.cloud/autonomous-google-ads-agent) rather than
granted in one leap.

## Day 1 — connect, then only ask questions

Add the connector URL to [the client you already use](https://adcopilot.cloud/mcp-clients) —
Claude, ChatGPT, Copilot, Gemini CLI, Cursor — then sign in with Google.
That is the whole setup; the URL is the same for everyone, and your Google
sign-in is what makes the connection yours.
Then spend twenty minutes asking things you already know the answers to:

```text
List the accounts you can see.
```

```text
In account <account>, what did we spend in the last 30 days, and on which
campaigns?
```

```text
Which campaign has the best cost per conversion this month, and which has
the worst?
```

Day 1 is a calibration exercise. You know this account; check the agent's
readings against your own. When it names your top campaign correctly and its
spend figures match the UI, you have established the thing every later
approval rests on: it reads the account accurately.

End the day with one deliberate refusal:

```text
Delete the worst campaign.
```

Watch it decline. Deletion is not gated behind approval — the capability is
absent from the connector, and a REMOVED status is refused server-side.
Knowing the floor exists changes how freely you experiment above it. The
[security page](https://adcopilot.cloud/security) explains exactly where that floor is built.

## Day 2 — run the audit

Day 2 is the structured read: wasted spend, search terms, disapprovals,
structural gaps. The full half-hour script with what each answer means is
[your first AI Google Ads audit](https://adcopilot.cloud/tutorials/your-first-ai-google-ads-audit)
— run it as written. The short version, if you only have ten minutes:

```text
In account <account>, which search terms spent money in the last 30 days
without converting? Rank by cost, top 25, with the campaign each appeared
in.
```

```text
In account <account>, list disapproved or policy-limited ads, and ad groups
with no enabled RSA.
```

Write down the three worst findings. They are tomorrow's work — and note
that the agent surfaced them in a single pass without being able to change
anything. Two days in, zero approvals granted, and you already have a work
list.

## Day 3 — writes that cannot spend

Today the agent changes the account for the first time — through writes
with no blast radius. [Negative keywords](https://adcopilot.cloud/negative-keywords-automation)
are the canonical first write: pointed at the spend that buys nothing, they
can only *stop* it, never start it.

```text
From yesterday's wasted search terms in account <account>, add the clearly
irrelevant ones as exact match negatives to the campaigns where they
appeared. Show me the full list before the call.
```

Your client now shows its first approval prompt: the tool by name
(the one that adds negative keywords), the account, the campaign, every term. Read it
properly this once — this is the mechanism that will guard every future
write, and it is worth seeing clearly on a change with zero downside. The
[approval loop](https://adcopilot.cloud/blog/why-your-ads-agent-needs-an-approval-loop) is the
whole story of why this prompt exists.

Approve it. Then check Google Ads change history in the UI: the change is
there, attributed to your own Google account, because the connector acts as
you — not as a service account.

## Day 4 — build something paused

Second class of zero-spend write: creation. Campaigns created through the
connector default to paused, and paused things cannot spend.

```text
In account <account>, create a paused search campaign "Test - <theme>" with
a $10/day budget. Add one ad group, ten phrase match keywords for <theme>,
and draft an RSA for <URL> — show me the copy before creating the ad.
Leave everything paused.
```

You will grant a small chain of approvals — campaign, ad group, keywords,
ad — and end with a complete, reviewable draft sitting inert in the
account. Open it in the Google Ads UI and inspect it like a colleague's
work. If it is good, keep it for real use; if not, tell the agent what to
change and watch it revise. The full version of this workflow, brief to
live, is [launch a campaign with AI](https://adcopilot.cloud/tutorials/launch-a-campaign-with-ai).

## Day 5 — the first spend change

Now the agent has four days of demonstrated accurate reading and two days
of clean writes. Time for the class of change that needed the trust:

```text
In account <account>, you flagged <campaign> as budget-limited on day 2.
Show me its last-14-day cost per conversion and lost impression share, and
if the case holds, raise its daily budget by 15%. Wait for my approval.
```

Notice the shape — evidence, threshold, capped change, approval. That is
the template for every spend change you will ever delegate: the agent
argues from data it just pulled, you spend one click on judgement. If the
case is weak, decline and say why; the correction teaches you both what
your bar is.

Keyword-level pauses belong in the same session:

```text
Pause any enabled keyword that spent over $25 in 30 days with zero
conversions. List them first.
```

A paused keyword can be re-enabled, which is what makes pausing delegable on day 5 rather
than day 50.

## Days 6 and 7 — turn it into a routine

The last two days convert exploration into habit. Run the
[20-minute weekly routine](https://adcopilot.cloud/tutorials/weekly-optimization-routine-with-ai)
once, end to end: weekly summary, search-term sweep, budget pacing, ad
health, one improvement proposal. Time it. Then close the week with a log:

```text
Summarise everything you changed in account <account> this week — every
write, in order, with values. I'm keeping this as my week-one record.
```

Cross-check that list against the approvals you remember granting and
against change history in the UI. All three should agree. When they do, you
have verified the property that matters more than any single optimisation:
nothing happened that you did not approve.

## Where you should stand by day 7

By the end of the week you should be able to answer three questions from
experience, not marketing: does it read the account accurately, does it
argue from evidence before proposing changes, and does your AI client ask before each write if it is set to ask before AdCopilot's write tools. You should have real negatives added, a reviewed
draft campaign, one defensible budget change, and a routine scheduled for
Monday.

What you choose to delegate next — and how much evidence you demand per
approval — is now a decision you can make from a week of observed
behaviour. The [prompt library](https://adcopilot.cloud/tutorials/prompt-guidelines-for-google-ads-ai)
covers most jobs you will reach for from here.

If you have not connected an account yet, the first five days of the playbook run inside
the free window: [Start free](https://app.adcopilot.cloud/signup) —
five days on the full Pro plan for your first workspace, no card to start (one is needed after 1,000 operations). Day 1 starts ten minutes
after you sign in.

## Questions

### How much time does the first week actually take?

Under an hour a day, and most days far less. Day 1 is ten minutes of connecting plus twenty of questions. Day 2's audit is half an hour. Days 3 and 4 are twenty-minute sessions ending in a few approvals. Day 5's first spend change takes five minutes because the evidence was gathered on the days before.

### Should I do this on a live account or a quiet one?

A live account you know well. The point of week one is calibration — checking the agent's readings against your own knowledge — and that only works on an account where you can recognise a right answer. Days 1–2 are reads and cannot change anything; by the time writes start, you have seen how it reasons.

### Why not allow spend changes on day one?

Nothing technical stops you — AdCopilot proposes each write first, and a client set to ask before AdCopilot's write tools asks before each write from the first minute. The staging is for you, not the tool: approving a budget change is easy when you have already watched the agent read the account correctly for four days, and hard to judge when its first-ever output is a spend proposal.

---

This is the markdown copy of https://adcopilot.cloud/tutorials/first-week-with-an-ads-agent. The index of the site's pages is https://adcopilot.cloud/llms.txt.
