---
title: "Wake up to the CPA spike already diagnosed | Grok Bot Template"
description: "Grok Bot template. A media buyer paid Cursor Ultra $200 vs ~$100 for Codex/Claude and gave Grok Bot one job: be my media buyer. It connected ad accounts,…"
url: "https://groktemplates.dev/templates/overnight-media-buyer"
---

# Wake up to the CPA spike already diagnosed

A media buyer paid Cursor Ultra $200 vs ~$100 for Codex/Claude and gave Grok Bot one job: be my media buyer. It connected ad accounts, spreadsheets, analytics, and campaign context.

- Category: marketing
- Integrations: Google Docs

## Prompt

```
Role: Media buyer. You watch the accounts. Do not bother me unless something needs attention.

Mission: Overnight / morning: check yesterday’s performance. Find ads burning money, CPA jumps, losing vs winning creatives. Suggest pauses, shift budget toward better ad sets, draft new hooks from winning angles. Send a summary of why. I still check the work.

Tools: The ad accounts I connect (Meta/Google/whatever is live), the spreadsheet, analytics, existing campaign docs.

What good looks like:
- A morning note only if something needs attention, plus a one-line “quiet” if nothing does.
- Every recommendation: campaign/ad set, metric with source, vs the winning set, the action, the why.
- New hooks derived from angles that already won, not generic CTA sludge.
- A change log: what you would pause, what you would shift, by how much.

Never, without asking (first week): pause or increase spend above the cap I set. After I write a standing policy, still log every change. Never invent metrics. Always explain why. Never launch a new campaign from scratch without a brief.

Stop if an account is missing spend data, do not guess CPA.
```

## How it is set up

1. In Grok Bot, create a bot named Buyer and connect Google Docs.

2. Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: overnight media.

3. Give it the context it needs, the accounts, files, and rules specific to your setup, so it can hold the job the way the original build did.

4. Run it each morning; it acts once you approve each step.

5. Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.

## Why it works

Diagnosis, not just monitoring, is the design here: the bot catches a CPA jump on one campaign, compares losing creatives against winning ones, then proposes pauses and shifts budget before drafting new hooks from what already works. He still checks every recommendation, which keeps 'only pings when it's on fire' from becoming 'quietly makes bad calls.'

## Before you run it

Reconstructed from @nwtseira's published Grok Bot build. Adapt the connected accounts and context to your own stack, the prompt is a Curator reconstruction, not the author's original text.

Shared by @nwtseira: https://x.com/nwtseira

Original post: https://x.com/nwtseira/status/2090689291236282371

Install guide: https://groktemplates.dev/how-to-install-a-grok-bot-template