1---2name: chatgpt-ads-check3description: >-4 Decides whether ChatGPT Ads fit a B2B SaaS company yet (market open, buyers there, core channels measured, tracking5 ready before spend, a capped test with a stop rule), writes chat-card ads and context hints matched to the buyer6 questions the company isn't named in, and after a test reconciles the clicks Ads Manager reports with the visits7 and leads that actually arrive. Every platform fact carries the date it was checked. Returns GO TEST, NOT YET,8 NO FIT or BLOCKED before a test, and RECONCILED, INVESTIGATE or BROKEN after one. Use it before spending on9 ChatGPT Ads and after each test. Not for measuring organic AI visibility (use ai-answer-panel).10license: MIT11compatibility: >-12 Works in Claude, ChatGPT, Codex, Cursor and any agent that reads SKILL.md. Uses a connected ad account or analytics13 if the agent has one, otherwise exports or pasted figures. Python 3 is optional, for the reconciliation.14metadata:15 author: SHAKEUP16 version: "1.0.0"17 stage: decide18 plugin: paid-media19 homepage: https://www.shakeuphq.com/skills/chatgpt-ads-check20---21 22# ChatGPT Ads check23 24Says whether ChatGPT Ads are worth a test yet, writes ads that follow on from the buyer's question, and checks that the clicks you pay for become real visits.25 26## Purpose27 28- One job: a go or stop call on ChatGPT Ads for one company, with the ads for a test, and the reconciliation after it.29- Stage: decide. It ends in a verdict for the mode it ran.30- It marks every platform fact with the date it was checked (`references/chatgpt-ads-facts.md`). The platform is new and changes often.31- It never launches, funds or edits a campaign, and never invents a reach, a CPC or a conversion rate.32 33## Use when / not34 35| Situation | Use |36| --- | --- |37| Asking whether to test ChatGPT Ads | this skill, mode `fit` |38| A test is approved and needs its ads | this skill, mode `fit` (the ads come with `GO TEST`) |39| A test has run and the clicks don't match the visits | this skill, mode `reconcile` |40| Measuring how often AI answers name you for free | `ai-answer-panel` |41| Setting the cost per lead ceiling | `lead-value-math` |42| Checking conversion tracking across every platform | `tracking-audit` |43 44## Inputs45 46| Input | Required | Ways to provide, in order | If missing |47| --- | --- | --- | --- |48| Selling regions | yes (fit) | `## Company` "Regions"; the reader | ask once |49| Max CPL | yes (fit) | `lead-value-math` handoff; the reader | `BLOCKED` until set; offer `lead-value-math` |50| Market open in the account | yes (fit) | the reader's Ads Manager location lookup; the reader | `NOT YET` until confirmed |51| Evidence buyers use ChatGPT to research the category | no | analytics sessions from chatgpt.com (last 90 days); "ChatGPT" in free-text "how did you hear about us" answers; `ai-answer-panel` results | the fit call is marked `partial`; never assume |52| Core channel measurement | yes (fit) | `## Targets` filled and a channel with CRM outcomes reconciled within 15%; the reader | `NOT YET` |53| Tracking plan: Pixel or Conversions API, `oppref` kept, UTMs on the landing URL | yes (fit) | the reader; `tracking-audit` | `NOT YET` until it is live before spend |54| Buyer questions where the company isn't named | no | `ai-answer-panel` handoff; `## Buying moments` | use the buying moments' questions, coverage `partial` |55| Test budget and length | yes (fit) | the reader | ask once |56| Reported clicks and tagged analytics sessions, by day | yes (reconcile) | Ads Manager or the Insights report; analytics export; pasted rows | `BLOCKED` for reconcile |57| Leads, spend, platform conversions | no (reconcile) | CRM; Ads Manager | visits reconciled, outcomes not |58 59## Profile read60 61From `company-profile.md`: `## Company` (regions, category, business model), `## Buyers` and `### Buying group`, `## Buying moments`, `## Messaging house`, `## Voice`, `## Claims and proof`, `## Channels` (status of ChatGPT Ads and the others), `## Targets`, `## Accounts and data` (analytics, CRM, connected ad accounts), and every `## Learnings` entry for `chatgpt-ads-check` with status `noted`, `fact` or `accepted`.62 63No profile: ask in one message for the selling regions, the most a lead may cost, the test budget, and which analytics and CRM hold the data. Say that `company-profile` saves this next time.64 65## Steps66 671. **Apply learnings.** A past test's result, or a tracking fix, changes the prerequisites below. Name each one that fires.68 692. **Pick the mode.** Reported clicks and sessions given: `reconcile` (step 9). Otherwise: `fit` (steps 3 to 8).70 713. **Refresh the facts.** Read `references/chatgpt-ads-facts.md`. If its check date is more than 3 months old, open the OpenAI docs again and update what you repeat. Treat the "not confirmed" list as risks, never as facts.72 734. **Run the prerequisites** (mode `fit`):74 75 | Check | Passes when | Why |76 | --- | --- | --- |77 | Market | at least one selling region shows as available in the reader's account | a valid country code doesn't mean the country is open |78 | Buyers there | analytics shows chatgpt.com sessions on buying pages, or buyers name ChatGPT in "how did you hear", or tracked buyer prompts exist for the category | ads under answers only matter where buyers ask |79 | Core channels measured | `## Targets` is filled and one channel's platform and CRM counts agree within 15% | a new channel can't be read if the old ones can't |80 | Tracking before spend | Pixel or Conversions API sends the lead event, `oppref` survives the landing page and reaches server events, `event_id` dedupes browser and server, UTMs on the final URL; live now, or scheduled before launch with a test lead confirmed before the first spend (an open item that gates the launch) | advertisers get aggregated reports, so tracking is the only way to count leads |81 | Landing page | reachable by OpenAI's ad crawlers, no redirect to another address, picks up the buyer's question in its headline | a redirect can drop `oppref`, and the ad has to continue the conversation |82 | Budget and stop rule | test budget at least 2 x max CPL, a fixed length, and a written rule agreed before launch | under 2 leads' worth of spend, a zero is noise |83 84 The stop rule to write: after the test budget, continue only if cost per lead is at or under max CPL and the reconciliation is `RECONCILED`; stop if 0 leads at 2 x max CPL; repeat with a change if leads came in above the ceiling.85 865. **Note the reach risk.** Which plans see ads is not confirmed in OpenAI's docs (see the reference). If the reader's buyers work at companies that give staff company plans, say the test may reach fewer of them, and read results by job role on the landing page form, not by clicks.87 886. **Pick the questions.** From `ai-answer-panel` (prompts where the company isn't named and the buyer is close to choosing) or the buying moments' questions. One ad group per cluster of questions that one card and one page can answer honestly.89 907. **Write the ads** (only on `GO TEST`): per ad group, 2 or 3 chat cards (title 3 to 50 characters, body up to 100) that follow on from the question without repeating the answer, plus context hints that describe the use cases and needs in plain words, not keywords. Proof only from `## Claims and proof`. Run `voice-check` and `claim-check` on every card (inline without them: no dashes, no profile words to avoid, every number in the claims). Fix and recheck at most twice.91 928. **Write the test plan:** markets, platform groups, ad groups and their questions, budget, length, bid strategy (a click objective with a fixed bid or Maximize clicks while conversion volume is low; Maximize conversions once the lead event fires reliably), tracking checklist, stop rule, and when to reconcile (after the first 7 days and at the end).93 949. **Reconcile** (mode `reconcile`). Run `python3 scripts/reconcile_clicks.py --csv data.csv`. Without Python: gap = 1 minus tagged sessions / reported clicks, by campaign and by day; list days with a gap over 50%; say you ran it by hand.95 96 | Gap | Verdict | Why |97 | --- | --- | --- |98 | at or under 15% | `RECONCILED` | the same tolerance platform and CRM counts are held to |99 | over 15% to 50%, or sessions more than 15% above clicks | `INVESTIGATE` | something loses or mixes visits; work the cause table in the reference, cheapest check first |100 | over 50%, or 0 sessions on 20 or more clicks | `BROKEN` | most paid clicks never reach analytics: stop reading performance until it's fixed |101 102 With leads: cost per lead against max CPL. With platform conversions: compare click-through conversions only, on the same date basis, before calling a gap.103 104## Check and verdict105 106Mode `fit`, first match wins:107 108| Verdict | Condition |109| --- | --- |110| `BLOCKED` | No selling region, or no max CPL after one question |111| `NO FIT` | None of the selling regions is open to ChatGPT Ads in the reader's account |112| `NOT YET` | Any other prerequisite in step 4 fails: name each one and what fixes it |113| `GO TEST` | Every prerequisite passes: the ads and the test plan follow |114 115Mode `reconcile`, first match wins: `BLOCKED` (no clicks or no sessions), `BROKEN`, `INVESTIGATE`, `RECONCILED`, by the gap table in step 9.116 117Named stops: `BLOCKED` asks for the missing input. `NOT YET` lists the failing prerequisites in the order to fix them. `BROKEN` stops any reading of the test's performance. No other stops.118 119## Learn120 121Append to `## Learnings` when:122 123- a test ends: a `fact` with spend, leads, cost per lead, the reconciliation gap and the stop rule's call;124- a reconciliation finds the cause of a gap (a redirect, a consent setting): a `fact`, so the next test checks it first;125- a platform fact in the reference turns out to have changed: a `fact` with the date and the page, and the reference updated;126- the reader goes ahead despite `NOT YET`: a `proposal` with their reason.127 128Example: `- 2026-10-24 | chatgpt-ads-check | fact | The demo page redirect dropped oppref; 31% of clicks had no session until it was removed | Why: reconciliation, 2026-10-01 to 10-14 | Status: noted`129 130## Output131 132```133Mode: <fit | reconcile> · Verdict: <GO TEST | NOT YET | NO FIT | BLOCKED | RECONCILED | INVESTIGATE | BROKEN> · Coverage: <complete | partial (what's missing)>134Facts as of: <check date of the reference, and what was rechecked>135 136fit:137| Prerequisite | Result | Evidence | Fix |138Reach risk: <one line>139Questions and ad groups: <list>140Ads: | Ad group | Title (chars) | Body (chars) | Proof | Context hints |141Test plan: <markets, platforms, budget, length, bidding, tracking, stop rule, reconcile dates>142 143reconcile:144| Campaign | Clicks | Sessions | Gap | Status |145Days over 50%: <dates> · Cost per lead: <value or not available> · Likely causes, in order: <list>146 147Learnings applied: <list, or none>148```149 150Then the handoff block.151 152## Hand off153 154```handoff155skill: chatgpt-ads-check156version: 1.0.0157verdict: GO TEST158coverage: partial (reach by plan not confirmed)159for: <company> ChatGPT Ads test160outputs:161 mode: fit162 markets: [US]163 test_budget: 3000164 stop_rule: continue if CPL at or under 285 and reconciled; stop at 0 leads after 570165 ad_groups: 2166 facts_checked: 2026-10-24167next: [tracking-audit]168open: [confirm the pixel fires on the demo form before spend]169```170 171After a test, `mode: reconcile` with `gap` and `cost_per_lead` in `outputs`.172 173## Failure modes174 175| Problem | Do this |176| --- | --- |177| The reader quotes a platform fact newer than the reference | Use it if they can show the source, then update the reference date |178| Analytics can't separate paid from organic ChatGPT visits | Add the UTM to the final URL before the test; until then, reconciliation is `INVESTIGATE` |179| The test is too small to reach 2 x max CPL | `NOT YET`; offer a longer test at the same daily budget instead of a bigger one |180| Ads Manager isn't open to the reader's account yet | `NOT YET` or `NO FIT` by region; record the date checked |181| The reader asks for ads before the fit check | Run the fit check first; ads come only with `GO TEST` |182 183## Influenced by184 185- OpenAI's ChatGPT Ads documentation for advertisers and developers: bidding, targeting, context hints, chat card limits, the Measurement Pixel, the Conversions API and attribution windows: https://developers.openai.com/ads186- SHAKEUP's ChatGPT Ads practice: a capped test with one question and a stop rule agreed in advance, tracking before the first spend, and ads planned on the buyer prompts where the company isn't named yet.