Grok Bot analytics prompts that pack numbers, then wait
Weekly packs from GA, the warehouse, and sheets. Cite the report or write unknown. Distinct from product specs and paid-ad spend. The Bot does not change pixels or dashboards in prod. You still decide.
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.
Weekly packs
5 promptsMonday north-star pack
1/21✨ What it does
The Bot pulls this week vs last four weeks for [NORTH STAR LIST] from [GA / WAREHOUSE / SHEET], cites each number with a report URL, and writes unknown when a source will not open. You still decide which move is real and what to ship next.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Pack [NORTH STAR LIST] for this week vs the previous four. Cite each number. Write unknown if a source is down. Do not change dashboards. Sources: [GA PROPERTY], [WAREHOUSE], [WEEKLY SHEET], [DEFINITION 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 edit GA, GTM, pixels, or live dashboards. Do not invent a rate. Deliverable: Metric, this week, prior four, delta, report URL or unknown, one sentence per move. Review point: I decide which move is real.
Pro tip: Name the metrics and the source of truth. Three tools will disagree.
Warehouse vs GA reconcile
2/21✨ What it does
The Bot reconciles [METRIC] for [WINDOW] between [WAREHOUSE] and [GA PROPERTY], lists the delta, and stops at unknown instead of blending the two. You still decide which source is truth and whether to investigate.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Reconcile [METRIC] for [WINDOW] in [WAREHOUSE] vs [GA PROPERTY]. Show both. Do not pick a winner. Sources: [WAREHOUSE QUERY OR VIEW], [GA REPORT], [DEFINITION 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 change the warehouse or GA. If a source is stale, say so. Deliverable: Warehouse number, GA number, delta, as-of times, likely cause labeled guess vs fact. Review point: I pick the source of truth.
Pro tip: Blended numbers hide a tracking bug. Keep both columns visible.
Sheet snapshot vs live
3/21✨ What it does
The Bot compares [WEEKLY SHEET] to live [GA OR WAREHOUSE] for the same [WINDOW] and flags rows that drifted, with the as-of time on each cell. You still decide which sheet cells to overwrite.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Diff [WEEKLY SHEET] against live [GA OR WAREHOUSE] for [WINDOW]. Flag drift. Do not overwrite the sheet. Sources: [SHEET], live [GA OR WAREHOUSE]. 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 the sheet. Do not silently refresh cells. Deliverable: Row, sheet value, live value, as-of, keep / refresh suggestion. Review point: I overwrite the cells I accept.
Pro tip: A frozen sheet is a snapshot, not truth. Date every cell.
Exec one-pager from sources
4/21✨ What it does
The Bot writes a one-page exec pack for [STAKEHOLDER] from [NAMED SOURCES] covering [METRIC LIST], with a link under every number and a thin-sources note if a tool is down. You still decide what goes into the meeting.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: One-pager for [STAKEHOLDER] on [METRIC LIST] from [NAMED SOURCES]. Cite or unknown. Do not invent a chart. Sources: [GA], [WAREHOUSE], [SHEET], [LAST WEEK PACK]. 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 email the exec. Do not change any dashboard tile. Deliverable: One page, links, unknown list, last-good note if a source failed. Review point: I choose what enters the meeting.
Pro tip: No link, no number. A slide without a report URL is a rumor.
Fail closed if a source is down
5/21✨ What it does
The Bot builds the weekly pack for [METRIC SET] from [SOURCES] and, if any required source is missing or stale past [SLA], returns a last-good note instead of inventing a chart. You still decide whether to wait or to present last-good.
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 any required source for [METRIC SET] is missing or older than [SLA], return last-good plus what you tried. Do not invent. Sources: [SOURCES]. Last-good pack in [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 reuse yesterday as new without labeling it last-good. Deliverable: Either a cited pack or a last-good note with timestamps and failed sources. Review point: I wait or I present last-good.
Pro tip: A 12-row pack built on one live source is fiction. Fail closed.
Traffic and landings
4 promptsChannel mix without spend
6/21✨ What it does
The Bot tables sessions, users, and conversion by [CHANNEL GROUPING] in [GA PROPERTY] for [WINDOW] vs [BASELINE], with no spend, CAC, or bid numbers unless they already live in those reports. You still decide which channel story to brief.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Table [CHANNEL GROUPING] in [GA PROPERTY] for [WINDOW] vs [BASELINE]: sessions, users, [CONVERSION]. No spend unless it is already in that GA report. Sources: [GA ACQUISITION], [CHANNEL GROUPING 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 open ads managers. Do not recommend bids or budgets. Deliverable: Channel, sessions, users, conversion, delta vs baseline, report URL. Review point: I brief the channel story.
Pro tip: This is not a media-buying memo. Leave spend on the paid-ads page.
Landing quality pack
7/21✨ What it does
The Bot ranks [N] landings in [GA PROPERTY] for [WINDOW] by [SESSIONS / CONV], screenshots above-the-fold, and flags title vs query mismatch without editing the page. You still decide which landing to change.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Rank top [N] landings in [GA PROPERTY] for [WINDOW]. Screenshot the fold. Flag title vs query mismatch. Do not edit pages. Sources: [GA LANDING REPORT], live pages in the 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 edit CMS, titles, or ads. Deliverable: URL, sessions, conversion, screenshot path, mismatch, suggested owner. Review point: I pick which landing to change.
Pro tip: Screenshot the fold. A paraphrase without a picture starts a fight.
New vs returning split
8/21✨ What it does
The Bot splits [CONVERSION] in [GA PROPERTY] for [WINDOW] into new vs returning, cites the definition used, and writes unknown if the audience is not in the property. You still decide whether the split changes the plan.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Split [CONVERSION] for [WINDOW] into new vs returning in [GA PROPERTY]. Cite the definition. Unknown if the audience is missing. Sources: [GA AUDIENCES], [DEFINITION 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 create or edit audiences. Deliverable: New, returning, definition cite, sample, unknown if missing. Review point: I decide if the split changes the plan.
Pro tip: Cite the GA audience definition. "New" is not the same in every property.
UTM hygiene, no ad edits
9/21✨ What it does
The Bot lists live campaign URLs from [SHEET OR GA] for [WINDOW] that are missing UTM, colliding on [CAMPAIGN], or landing on a 404, with screenshots and no ad edits. You still decide which tags to fix.
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 missing UTM, colliding [CAMPAIGN] names, and 404 landings in [SHEET OR GA] for [WINDOW]. Screenshot. Do not edit ads or pages. Sources: [CAMPAIGN SHEET], [GA], 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 edit ads, UTM on live URLs, or landing pages. Deliverable: URL, issue, screenshot, suggested fix. Review point: I fix the tags.
Pro tip: Hygiene is a report. The paid-ads page owns spend and bids.
Funnels and cohorts
4 promptsFunnel step pack
10/21✨ What it does
The Bot compares [FUNNEL STEPS] this week vs the last [4] weeks in [GA OR WAREHOUSE], names the largest step-level change, and attaches chart links without rewriting the funnel. You still decide which step to investigate.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Compare [FUNNEL STEPS] this week vs the last [4] in [GA OR WAREHOUSE]. Largest step change. Chart links. Do not rewrite the funnel. Sources: [GA FUNNEL OR EXPLORE], [WAREHOUSE], [FUNNEL DEFINITION]. 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 the funnel, events, or dashboards. This is not a product spec or flag flip. Deliverable: Step, this week, prior four, delta, chart URL, facts vs hypotheses. Review point: I pick the next chart.
Pro tip: Name the steps. "Why is conversion down" without steps is a novel.
Cohort retention table
11/21✨ What it does
The Bot builds a [WEEKLY / MONTHLY] retention table for [COHORT DEF] from [WAREHOUSE OR GA] covering [N] periods, labels incomplete periods, and refuses a blended average. You still decide which cohort story to tell.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Retention table for [COHORT DEF] at [WEEKLY / MONTHLY] for [N] periods from [WAREHOUSE OR GA]. Label incomplete. No blended average. Sources: [WAREHOUSE], [GA COHORTS IF PRESENT], [COHORT DEFINITION]. 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 invent retention if the grain is missing. Do not change the model. Deliverable: Table, incomplete flags, definition cite, unknown cells. Review point: I pick the cohort story.
Pro tip: Incomplete last period is a label, not a drop. Ban a single blended rate.
Goal vs written definition
12/21✨ What it does
The Bot checks [GOAL OR KEY EVENT] completions in [GA PROPERTY] for [WINDOW] against [DEFINITION DOC] and flags any event that no longer matches the written definition. You still decide whether to keep the goal or rewrite the doc.
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 [GOAL OR KEY EVENT] in [GA PROPERTY] for [WINDOW] against [DEFINITION DOC]. Flag drift. Do not edit the goal. Sources: [GA ADMIN / KEY EVENTS], [DEFINITION 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 create, delete, or mark key events. Deliverable: Event, live count, written definition or missing, drift, suggested owner. Review point: I keep the goal or I rewrite the doc.
Pro tip: If the doc is silent, write "definition missing". Do not invent a formula.
Segment comparison pack
13/21✨ What it does
The Bot compares [SEGMENT A] vs [SEGMENT B] on [METRIC LIST] in [GA OR WAREHOUSE] for [WINDOW], cites sample size, and writes unknown when a segment is empty. You still decide which segment to act 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: Compare [SEGMENT A] vs [SEGMENT B] on [METRIC LIST] for [WINDOW] in [GA OR WAREHOUSE]. Cite n. Unknown if empty. Sources: [GA SEGMENTS], [WAREHOUSE], [SEGMENT DEFINITIONS]. 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 create or edit segments. Do not invent a lift percent on n under [MIN N]. Deliverable: Metric, A, B, n, delta, report URL or unknown. Review point: I pick the segment to act on.
Pro tip: Sample size first. A 12-session winner is noise.
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.
Data trust
4 promptsEvent taxonomy drift
14/21✨ What it does
The Bot diffs [EVENT CATALOG] against live events in [GA OR WAREHOUSE] for [WINDOW], lists new, missing, and renamed names, and does not create or delete events. You still decide which taxonomy edits to ship.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Diff [EVENT CATALOG] vs live events in [GA OR WAREHOUSE] for [WINDOW]. New, missing, renamed. Do not create or delete events. Sources: [CATALOG], [GA EVENTS], [WAREHOUSE EVENT LIST]. 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 GTM, GA events, or the warehouse schema. Deliverable: New / missing / renamed, first-seen date, suggested owner. Review point: I ship taxonomy edits.
Pro tip: Renames without aliases break every weekly pack. Keep the old name visible.
Broken-event hunt
15/21✨ What it does
The Bot hunts [EVENT LIST] in [GA / GTM / WAREHOUSE] for [WINDOW], screenshots empty charts or sudden zeros, and writes a repro path without touching tags. You still decide which tracking fix to ship.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Hunt [EVENT LIST] in [GA / GTM / WAREHOUSE] for [WINDOW]. Screenshot zeros. Repro path. Do not touch tags. Sources: [GA], [GTM READ-ONLY], [WAREHOUSE], [RELEASE LIST]. 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 publish GTM. Do not edit pixels. Do not "fix" a tag in prod. Deliverable: Event, last-good, first-zero, screenshot, repro, facts vs hypotheses. Review point: I ship the tracking fix.
Pro tip: A zero can be a holiday or a dead tag. Screenshot the empty chart.
Pixel and tag inventory
16/21✨ What it does
The Bot inventories pixels and tags on [URL LIST] in the cloud browser, notes what fired vs [EXPECTED TAGS], and does not add, remove, or publish any tag. You still decide which pixel stays.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Inventory pixels and tags on [URL LIST]. Compare to [EXPECTED TAGS]. Do not add, remove, or publish. Sources: Cloud browser on [URL LIST], [TAG PLAN], [GTM READ-ONLY IF AVAILABLE]. 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 GTM, pixels, or consent banners. Sign-in is takeover. Deliverable: URL, tags seen, expected, missing or extra, screenshot. Review point: I decide which pixel stays.
Pro tip: Read-only inventory. Changing a pixel is a production change.
Metric definition audit
17/21✨ What it does
The Bot audits [METRIC LIST] against [DICTIONARY] and the live report in [GA OR WAREHOUSE], and writes "definition missing" instead of inventing a formula. You still decide which definition to lock.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Audit [METRIC LIST] vs [DICTIONARY] and the live report in [GA OR WAREHOUSE]. Definition missing is allowed. Do not invent a formula. Sources: [DICTIONARY], [GA], [WAREHOUSE], [DASHBOARD LIST]. 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 the dictionary or the dashboard. Deliverable: Metric, written formula or missing, live filter, mismatch, suggested lock. Review point: I lock the definition.
Pro tip: Two dashboards with the same name and different filters are two metrics.
Make the analytics Bot durable
4 promptsAnalytics Bot description
18/21✨ What it does
The Bot writes an analytics-pack description named [NAME] with [SOURCES], the cite-or-unknown rule, and a never-edit-pixels / never-edit-live-dashboards line. You still decide whether to create that 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 an analytics-pack Bot description named [NAME] for weekly packs from [SOURCES]. Never edit pixels or live dashboards. Sources: [GA], [WAREHOUSE], [SHEETS], [REVIEW WINDOW]. 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 production settings, pixels, GTM, or live dashboards. Deliverable: Description, pack format, never-do. Review point: I create the Bot.
Pro tip: Write "unknown is a valid cell" and "no prod tracking edits" in the description.
Monday pack routine
19/21✨ What it does
The Bot drafts a weekday routine that posts the [METRIC SET] pack from [SOURCES] at [TIME TZ] and fails closed if a source is down, without changing any dashboard. You still decide when to enable it.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Weekdays at [TIME TZ], post the [METRIC SET] pack from [SOURCES]. Fail closed if a source is down. Do not change dashboards. Sources: [SOURCES]. Last-good in [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 enable the routine. Do not edit tiles when a chart looks wrong. Deliverable: Routine card, pack format, last-good behavior. Review point: I enable it after one dry run.
Pro tip: Put the fail-closed rule in the routine, not only in one skill.
What analytics Bots never do
20/21✨ What it does
The Bot writes a never-do list for analytics Bots from your rules in [RULES DOC], including no pixel edits, no live dashboard changes, and no invented rates, plus the human substitute for each. You still decide what to paste into every analytics 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 the never-do list for analytics Bots from [RULES DOC]. Include no pixel edits, no live dashboard changes, no invented rates. Sources: [RULES DOC] and my extras: [LIST]. 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 paste into other Bots until I say so. Deliverable: 12 never-do items and the human substitute. Review point: I paste it into the Bot.
Pro tip: Paste this next to product and paid-ads never-do lists. They share one computer.
Dashboard screenshot archive
21/21✨ What it does
The Bot opens [DASHBOARD LIST] in the cloud browser, saves dated screenshots to [FOLDER], and writes last-good if a dashboard will not load, without editing tiles or filters in prod. You still decide which shots go into the pack.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Open [DASHBOARD LIST], save dated screenshots to [FOLDER]. Last-good if a board will not load. Do not edit tiles or filters in prod. Sources: [DASHBOARD URLS], [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 change filters, date pickers, or tiles on the live dashboard. Deliverable: Paths, as-of, last-good flags, missing boards. Review point: I pick which shots enter the pack.
Pro tip: An archive is evidence. Editing a prod tile to make the shot pretty is a prod change.
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