Launch prompts for Claude, ChatGPT, Cursor, and Codex
Copy-paste launch briefs for a $20/day display test. One full prompt for code agents, short versions for Claude, ChatGPT, and Codex. Real ids only, payment on a hosted page.
On this page
Paste one of these into your assistant when you want a first paid display test, not a research memo. Each one is a complete launch brief for a $20/day Adprime Zero campaign: create targeting, submit an ad, stop at a hosted payment link when the wallet needs money, then launch and report.
Connect Adprime Zero first: add https://mcp.adprimezero.com/mcp to Claude, ChatGPT, Cursor, Claude Code, or Codex and sign in (steps for each app). A chat with no Adprime Zero tools will invent request bodies from memory.
Why a launch prompt has to be long
A short "launch ads for my startup" prompt makes the model invent routes, pixel URLs, and provider ids. Our June 2026 reporting gaps got worse when guessed fields were treated as truth. These prompts are long on purpose: they name the live tools so the assistant does not have to guess them.
Copy one whole. Then add four lines of your own: the website, the one promise, the geography, and the daily budget. If you want webhooks, ad rotation, and conversion events in the first message, use the full brief on Get started and keep the $20/day cap in your own sentence.
Send the click to a page that keeps one promise, not to the homepage. The isolated funnel checklist is the gate before you spend. Name the campaign so a stranger can read the stack: angle__targeting__inventory__pageTemplate__wave, from the naming sheet.
What every prompt must forbid
If you shorten a prompt, keep these lines:
- Collecting cards, bank details, or login codes in the chat. Money moves through a hosted payment link.
- Printing an
ak_...key, or putting one in a web page tag. - Inventing campaign, ad, or audience ids. Use only the ids Adprime Zero returns (
camp_,cr_, targeting ids). - Inventing conversion pixel URLs.
- Using display names as segment keys.
- Treating
generated_atas reporting freshness. - Pausing the last active ad on a campaign.
- Raising the daily budget to make delivery look healthier.
- Declaring a winner from click-through rate.
The full prompt (Cursor and Claude Code)
Code agents can read docs, run commands, and keep going after a tool returns. That is useful for launch work and risky if the model improvises ids, so this version spells out the order. In Cursor, add the connector to ~/.cursor/mcp.json and sign in first, so the tool list comes from the server and not from memory.
Launch a $20/day Adprime Zero display test from this session.
Product:
- Signup: https://adprimezero.com/signup
- Docs: https://adprimezero.com/docs
- Get started: https://adprimezero.com/docs/get-started
- REST API reference: https://adprimezero.com/docs/quickstart
- API: https://api.adprimezero.com
Tools: use the Adprime Zero MCP tools (connector https://mcp.adprimezero.com/mcp). If they are missing, stop and tell me to connect it.
Do this work, in order:
1. Read the account with get_account. Never ask me for or print an API key.
2. Collect launch inputs from me: landing URL, who should see the ad, geography, headline, description, image or source image, and the one promise the page must keep.
3. Create targeting with create_targeting. If I ask for audiences, run discover_segments and use returned ids, not names. Show estimated data CPM before you attach a segment.
4. Pre-check the landing page, then submit creative with headline, description, click URL, expected content, and disclosure.
5. Create the campaign at $20/day. Name it so a stranger can read the stack (angle__targeting__inventory__pageTemplate__wave).
6. If the wallet cannot fund activation, request a hosted prepay link with request_prepay_link. Do not collect card data. Poll the funding intent after I finish the hosted page.
7. Activate with activate_campaign. It refuses, and lists what is missing, until the ad, the landing page, and the prepaid balance are ready.
Hard stops:
- Do not invent campaign, ad, or creative IDs. Use only the IDs the API returns.
- Do not write to the ad exchange or the database directly.
- Do not embed API keys in landing-page tags.
- Do not raise the daily budget above $20 unless I say so.
- If impressions or spend exist and clicks are zero, check get_beeswax_reporting_status (reporting freshness) before you change targeting. Use the clicks plural field.
Report back with the Adprime Zero IDs you created, the payment link status, and the next step I should take.Claude and Claude Code, short version
Use Adprime Zero to launch a $20/day display test.
Use the Adprime Zero tools (connector https://mcp.adprimezero.com/mcp). Start with get_account.
Create targeting (discover real segment ids if I ask for audience). Submit creative with headline, description, click URL, expected content, and disclosure.
If the wallet needs money, request a hosted prepay link. Do not collect card data.
Do not invent IDs. Use only IDs the API returns.
Name the campaign angle__targeting__inventory__pageTemplate__wave.ChatGPT, short version
Help me launch a $20/day Adprime Zero ad test.
Product docs: https://adprimezero.com/docs and https://adprimezero.com/docs/get-started
Signup: https://adprimezero.com/signup
Ask me for the landing URL, the one promise, geography, and the ad copy.
Use the Adprime Zero connector tools. If they are not connected, tell me to add https://mcp.adprimezero.com/mcp/chatgpt first.
If my balance is empty, tell me to add funds on the billing page in the Adprime Zero dashboard. Never collect payment details.
Do not invent campaign or creative IDs.
Do not send the click to a generic homepage if I am testing one message.Codex, short version
Launch a $20/day Adprime Zero campaign from this repo session.
1. Use the Adprime Zero MCP tools (https://mcp.adprimezero.com/mcp). Start with get_account.
2. If MCP is not available, use the REST API at https://api.adprimezero.com with ADP_ZERO_API_KEY from secrets.
3. create_targeting, submit_creative, create_campaign at $20/day, then activate_campaign.
4. request_prepay_link if balance cannot activate. Never collect cards.
5. Stop if a call fails. Show the error. Do not fabricate IDs.
Read https://adprimezero.com/docs/quickstart before the first write.What happens after you paste
The assistant reads the account. It stops at a payment link when the wallet is empty, and you pay in your browser. It submits the ad and waits on review; you look at any landing page that landed in requires_review. It activates when the balance and the review are ready, then reads the first report.
That is a campaign, not a generated media plan. If the assistant returns only copy and no ids from the product, the prompt did not run.
After launch, read freshness before you conclude there were no clicks. Snapshot rows can store clicks as zero on purpose, and the delivery field is clicks plural. App-by-app setup notes are in Connect your AI assistant and launch.
Related
- Guides · 4 min readConnect your AI assistant and launchAdd https://mcp.adprimezero.com/mcp to Claude, ChatGPT, Cursor, or Claude Code, sign in with an emailed code, and your assistant can fund, launch, and report on real display campaigns.
- Guides · 2 min readLaunch ads from CursorAdd Adprime Zero to Cursor as an MCP server and paste one launch brief. The campaign objects live on the account, not only in the chat.
- Playbooks · 2 min readIsolated funnel checklistOne promise from ad to page to CTA. Use this checklist before you spend, so a $20/day test is not mixed with five other messages on the homepage.
Run this from your assistant
Add one URL to Claude, ChatGPT, or Cursor, sign in with your email, and ask for the campaign. Prepaid from $5, with no insertion order and no sales call.