Paid Ads Setup
Read ../shared/operating-contract.md. Do not alter campaigns during setup.
Establish access
- Detect the current NotFair Google Ads and Meta Ads MCP surfaces using their existing shared preambles. If either is missing, give the connection path from the relevant preamble and stop before claiming access.
- List only accounts actually returned by the connected surface. Let the user select the intended account when more than one is available; never infer it from an account name.
- For LinkedIn, TikTok, Amazon, and ChatGPT Ads, check the available tools before proposing a connection. If no verified connector exists, request a current export or describe the plan-only boundary.
Capture decision-quality context
Read project documents that are clearly marketing-relevant, then ask only for gaps that data cannot establish:
- product, offer, geography, and primary conversion;
- unit economics: target CPA or break-even ROAS, margin, and customer value;
- approved claims, differentiators, exclusions, and brand voice;
- monthly budget, launch constraints, seasonality, and competitors;
- landing-page URLs and analytics/tracking owner.
Use the Google and Meta audit skills to persist account-specific business context where supported. Do not overwrite an existing AGENTS.md, CLAUDE.md, or project instructions as a side effect of setup. Offer a clearly marked paid-media context file only after the user approves the exact location and content.
Finish with a gap register
Report connected platforms, selected accounts, verified conversion signals, available date range, and the smallest next action. State missing tracking, economics, claim proof, or platform access explicitly. Hand off to /notfair:paid-ads-review for a baseline, /notfair:paid-ads-launch for a new campaign, or the platform audit for a deeper diagnosis.
1---2name: paid-ads-setup3description: Connect NotFair paid-ad accounts and establish reusable campaign context. Use when setting up paid media in a new workspace, connecting Google or Meta, refreshing brand context, or preparing an agent to work on ads safely.4---5
6# Paid Ads Setup
7
8Read `../shared/operating-contract.md`. Do not alter campaigns during setup.
9
10## Establish access
11
121. Detect the current NotFair Google Ads and Meta Ads MCP surfaces using their existing shared preambles. If either is missing, give the connection path from the relevant preamble and stop before claiming access.
132. List only accounts actually returned by the connected surface. Let the user select the intended account when more than one is available; never infer it from an account name.
143. For LinkedIn, TikTok, Amazon, and ChatGPT Ads, check the available tools before proposing a connection. If no verified connector exists, request a current export or describe the plan-only boundary.
15
16## Capture decision-quality context
17
18Read project documents that are clearly marketing-relevant, then ask only for gaps that data cannot establish:
19
20- product, offer, geography, and primary conversion;
21- unit economics: target CPA or break-even ROAS, margin, and customer value;
22- approved claims, differentiators, exclusions, and brand voice;
23- monthly budget, launch constraints, seasonality, and competitors;
24- landing-page URLs and analytics/tracking owner.
25
26Use the Google and Meta audit skills to persist account-specific business context where supported. Do not overwrite an existing `AGENTS.md`, `CLAUDE.md`, or project instructions as a side effect of setup. Offer a clearly marked paid-media context file only after the user approves the exact location and content.
27
28## Finish with a gap register
29
30Report connected platforms, selected accounts, verified conversion signals, available date range, and the smallest next action. State missing tracking, economics, claim proof, or platform access explicitly. Hand off to `/notfair:paid-ads-review` for a baseline, `/notfair:paid-ads-launch` for a new campaign, or the platform audit for a deeper diagnosis.
majiayu000