Grok Bot paid-ads prompts that recommend, then wait
Pull spend, compare to budget and target CAC, draft the update. Official docs: do not change budgets or send the message. Keep campaign changes behind approval even after the analysis is a routine.
In short: This page contains 21 copy-paste ready prompts, organized into 5 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.
The weekly read
4 promptsSpend vs plan vs CAC
1/21✨ What it does
The Bot pulls current spend and performance by campaign from [ADS], compares it to [MONTHLY BUDGET] and [TARGET CAC], and drafts a Slack update with recommended reallocations. You send the message and you change the budgets.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Pull current spend and performance by campaign. Compare with [MONTHLY BUDGET] and [TARGET CAC]. Recommend reallocations with numbers. Draft a Slack update. Do not change budgets or send the message. Sources: [ADS], [ANALYTICS], [BUDGET SHEET]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not change bids, budgets, or status. Do not send Slack. Deliverable: What moved, math, draft Slack, links. Review point: I send. I change budgets.
Pro tip: Name the source of truth for CAC. Three dashboards will disagree.
Broken tracking hunt
2/21✨ What it does
The Bot checks live ads in [ACCOUNT] for broken URLs, missing tracking codes, and landing pages that do not match the ad, with a screenshot of each issue. You fix the tracking.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Check live ads in [ACCOUNT] for broken URLs, missing UTM, and landings that do not match the ad. Sources: [ADS MANAGER], cloud browser. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not pause or edit ads. Deliverable: Ad, issue, screenshot, suggested fix. Review point: I fix.
Pro tip: A Bot that "optimizes" on broken tracking will spend you into a hole.
Geo or daypart anomaly
3/21✨ What it does
The Bot finds country or time-of-day anomalies in [ACCOUNT] for [WINDOW] versus [BASELINE] and labels each as hypothesis or fact, with a chart link. You decide what to do.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Find geo or daypart anomalies in [ACCOUNT] for [WINDOW] vs [BASELINE]. Sources: [ADS], [ANALYTICS]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not change targeting. Deliverable: Anomaly, chart link, hypothesis vs fact. Review point: I decide.
Pro tip: Ask for the window. "This month" hides a one-day spike.
Budget memo for a human
4/21✨ What it does
The Bot writes a one-page reallocation memo for [MONTH] from [SOURCE OF TRUTH], with current versus proposed, risk, rollback, and report links. You take it to finance.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Reallocation memo for [MONTH] from [SOURCE OF TRUTH]. Sources: [ADS], [BUDGET], [TARGET CAC]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not change platforms. Deliverable: Current, proposed, risk, rollback, links. Review point: I take it to finance.
Pro tip: Every number needs a report URL.
Prompts get you started. Tutorials level you up.
A growing library of 300+ hands-on AI tutorials. New tutorials added every week.
Creative
4 promptsFatigue report
5/21✨ What it does
The Bot lists creatives in [ACCOUNT] that hit [FATIGUE RULE] and suggests five replacement angles, without pausing or uploading anything. You brief design.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Creatives in [ACCOUNT] that hit [FATIGUE RULE]. Suggest 5 replacement angles. Do not pause or upload. Sources: [ADS], [BRAND BRIEF], last 14 days. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not pause or upload. Deliverable: Creative, frequency, CTR trend, angles. Review point: I brief design.
Pro tip: Write the fatigue rule or everything older than a week gets flagged.
Hook vs landing mismatch
6/21✨ What it does
The Bot compares the hook on your top [10] ads to the first screen of the landing page and flags mismatches, with screenshots of both. You align the ad and the page.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: For top [10] ads, compare hook to landing above-the-fold. Flag mismatches. Sources: Ads manager, landings in the browser. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not edit ads or pages. Deliverable: Ad, landing, mismatch, screenshots. Review point: I align them.
Pro tip: Screenshot both. Argument without pictures is a fight.
Winner autopsy
7/21✨ What it does
The Bot writes an autopsy of [AD ID] across audience, hook, offer, and landing, and lists what to copy and what to leave alone. You brief the next batch.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Autopsy of [AD ID]: audience, hook, offer, landing, what to clone vs not. Sources: [ADS], [ANALYTICS], [LANDING]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not scale it automatically. Deliverable: Four-part autopsy and a "do not clone" list. Review point: I brief the next batch.
Pro tip: Ask for audience, hook, offer, and landing. All four.
Asset pack staged, not uploaded
8/21✨ What it does
The Bot stages [N] assets for [CAMPAIGN] in [FOLDER] from [BRIEF] and [BRAND], and does not upload them to the ads manager. You upload the winners.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Stage [N] assets for [CAMPAIGN] in [FOLDER] from [BRIEF]. Do not upload to ads manager. Sources: [BRIEF], [BRAND], [FOLDER]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not upload. Do not generate real-person likeness without my ok. Deliverable: Paths, naming, what needs a human pass. Review point: I upload winners.
Pro tip: Brand and likeness rules. No real-person spicy leftovers.
Accounts and structure
4 promptsNaming and structure lint
9/21✨ What it does
The Bot checks campaign names in [ACCOUNT] against [CONVENTION] and recommends renames, without renaming live campaigns. You rename them in a quiet hour.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Lint [ACCOUNT] names vs [CONVENTION]. Recommend renames. Do not rename. Sources: [ADS], [CONVENTION DOC]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not rename live campaigns. Deliverable: Off-convention, suggested name, risk of renaming live. Review point: I rename in a quiet hour.
Pro tip: Give it the convention. Otherwise it invents one.
Overlapping audiences
10/21✨ What it does
The Bot finds audience overlap in [ACCOUNT] that likely bids against itself, using the overlap evidence the platform actually shows. You split the audiences.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Find audience overlap in [ACCOUNT] that likely self-competes. Sources: [ADS]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not change targeting. Deliverable: Pair, evidence, suggested split. Review point: I split.
Pro tip: Ask for the overlap evidence the platform actually shows.
Policy or disapproved ads
11/21✨ What it does
The Bot lists disapproved or limited ads, cites the policy line, and drafts an appeal or a do-not-appeal note, without submitting anything. You submit the appeal.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: List disapproved or limited ads. Draft appeal notes with the policy cite. Do not appeal. Sources: [ADS], [POLICY CENTER]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not submit appeals. Deliverable: Ad, reason, cite, draft appeal or "do not appeal". Review point: I submit.
Pro tip: Do not let it appeal with a story. Use the policy line.
Incrementality honesty
12/21✨ What it does
The Bot reports what incrementality evidence exists for [CAMPAIGN] and says none if there is no holdout or geo test, without inventing return on ad spend. You brief leadership.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: For [CAMPAIGN], what incrementality evidence exists? If none, say none. Do not invent ROAS. Sources: [ADS], [ANALYTICS], [TEST DOC IF ANY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not change bids based on last-click alone in this write-up. Deliverable: Evidence, missing tests, claims we must not make. Review point: I brief leadership.
Pro tip: If there is no geo test or holdout, say so.
Like these prompts? There are full tutorials behind them.
Learn the workflows, not just the prompts. 300+ easy-to-follow tutorials inside AI Academy — and growing every week.
Routines
3 promptsMorning spend pulse
13/21✨ What it does
The Bot writes a daily pulse format for spend versus pace, tracking breaks, and any 3x spike, and does not change campaigns or Slack the pulse. You turn the routine on.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Daily pulse: spend vs pace, any tracking breaks, any 3x spike. Do not change campaigns. Do not Slack it. Sources: [ADS], [BUDGET PACE]. If ads are down, fail closed. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not change campaigns. Deliverable: Routine card and pulse format. Review point: I enable.
Pro tip: Cap it. If spend is normal, three lines.
Weekly Slack draft
14/21✨ What it does
The Bot writes a Monday routine that drafts last week's growth Slack from [ADS], [ANALYTICS], and [BUDGET], without sending it. You send the message.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Mondays, draft the growth Slack from last week's numbers. Do not send. Sources: [ADS], [ANALYTICS], [BUDGET]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send Slack. Do not change budgets. Deliverable: Draft plus links. Review point: I send.
Pro tip: Same time every week. Growth will look for it.
Cap and kill-switch
15/21✨ What it does
The Bot writes an alert that fires here if daily spend exceeds [X] and then stops recommending scale, without touching platform caps. You set the platform caps yourself.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: If daily spend exceeds [X], post an alert here and do not recommend scale. Do not change platform caps (I set those). Sources: [ADS]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not raise platform caps. Do not pause everything in a panic unless I wrote that rule. Deliverable: Alert format and the platform-cap reminder. Review point: I set platform caps myself.
Pro tip: The Bot cannot be your only kill switch. You still set platform caps.
Make the ads Bot durable
6 promptsAds Bot description
16/21✨ What it does
The Bot writes a paid-media Bot description named [NAME] covering [ACCOUNTS], [BUDGET], and [TARGET CAC SOURCE], with never change bids and never send Slack. You create the Bot.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write a paid-media Bot description named [NAME]. Sources: [ACCOUNTS], [BUDGET], [TARGET CAC SOURCE]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Never change bids, budgets, or status. Never send Slack. Deliverable: Description and weekly format. Review point: I create it.
Pro tip: Write the CAC source of truth in the description.
What ads Bots never do
17/21✨ What it does
The Bot writes a twelve-item list of things ads Bots must not do, including changing bids, pixels, audiences, appeals, uploads, and scale. You paste that list.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write the never-do list for ads Bots. Sources: My rules. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. Deliverable: 12 never-do items. Review point: I paste it.
Pro tip: If it can spend, the never-do list is the product.
Handoff to creative or web
18/21✨ What it does
The Bot turns this week's fatigue and landing-mismatch findings into ticket drafts for [CREATIVE / WEB], with screenshot paths, and does not file them. You file the tickets.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Turn this week's fatigue and mismatch findings into tickets for [CREATIVE / WEB]. Do not file them. Sources: This week's reports. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not file tickets until I pick. Deliverable: Ticket drafts with screenshot paths. Review point: I file.
Pro tip: Attach screenshots. Creative will not re-open the ads manager.
Creative brief from a loser, not a winner
19/21✨ What it does
The Bot reads [LOSING AD], writes what not to repeat with evidence, and offers three replacement angles, without pausing or uploading. You brief design.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: From [LOSING AD], write a brief for what not to repeat and 3 replacement angles. Do not upload. Sources: [ADS], [BRIEF], last [N] days. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not pause or upload. Deliverable: What failed, evidence, 3 angles. Review point: I brief design.
Pro tip: Winners get cloned too often. Losers teach the constraint.
Search term dump, human negatives
20/21✨ What it does
The Bot lists search terms in [CAMPAIGN] that wasted spend versus [INTENT] and suggests negatives, without adding them. You add the negatives.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: List search terms in [CAMPAIGN] that wasted spend vs [INTENT]. Do not add negatives. Sources: [ADS SEARCH TERMS]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not change keywords or negatives. Deliverable: Term, spend, why junk, suggested negative. Review point: I add negatives.
Pro tip: A Bot that adds negatives will block your brand name once. You add them.
Pacing vs remaining days
21/21✨ What it does
The Bot paces [ACCOUNT] against [BUDGET] with days left in [PERIOD] and recommends a change without making it. You change the budget if you agree.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Pace [ACCOUNT] vs [BUDGET] with days left in [PERIOD]. Recommend, do not change. Sources: [ADS], [BUDGET]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not change budgets. Deliverable: Spend, pace, days left, recommendation. Review point: I change the budget if I agree.
Pro tip: Pace without remaining days is a mood. Show both.
Free tool
Prompt Optimizer
Turn a rough idea into a structured, professional AI prompt.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.
Related guides