blink-new Meta Ad Creative Copywriter
Core principle
Write Meta ad copy so a cold prospect understands what is being sold in a few seconds.
Clarity comes before cleverness.
The reader should immediately know:
- What the product is
- Who it is for
- What problem it solves
- Why they should care now
Do not rely on vague, provocative, or abstract headlines unless the product category is already obvious.
Bad:
Your agent can do lead gen
Better:
B2B Lead Enrichment API for Claude
Bad:
Build systems, not workflows
Better:
API-Native B2B Enrichment Platform
Bad:
Prompt → lead data
Better:
Turn Prompts Into Enriched B2B Leads
Output format
For each ad concept, produce:
## Concept Name
### Primary Text
<short hook>
<supporting line>
<benefit / proof / CTA line>
### Headline
<specific product + use case>
### Description
<longer explanation of what it does, who it is for, and why it matters>
Use line breaks inside Primary Text. Meta primary text can display multiple lines, and spacing improves scanning.
Primary text rules
Primary Text should usually use 2–4 short blocks separated by blank lines.
Structure:
- Hook: specific pain, use case, or desired outcome
- Explanation: what the product does
- Benefit: why it matters
- Optional CTA or proof
Example:
Turn any email into a complete B2B lead profile.
Get name, title, company, LinkedIn, and company data in seconds.
Built for CRM enrichment, outbound, and API workflows.
Avoid dense paragraphs.
Avoid one-line copy that is too clever but unclear.
Headline rules
Headlines must be specific. They should name the product category or use case.
A good headline answers: “What is this?”
Prefer:
- B2B Lead Enrichment API
- Email Enrichment API
- MCP-Native B2B Data API
- API for B2B Prospecting
- Contact Enrichment API for GTM Teams
- Lead Generation API for Developers
Avoid vague headlines like:
- Find leads instantly
- The new GTM stack
- Build your lead engine
- Your agent can call this
- Stop guessing
- Workflows don’t scale
These can be supporting lines, but they should not be the main headline for cold audiences.
Description rules
Use descriptions as a conversion aid, not as filler.
Descriptions can be longer than headlines and should explain:
- What the product does
- The input and output
- The buyer or workflow
- A differentiator
Example:
Send an email or domain and get verified contact + company data back. Built for outbound, CRM enrichment, and API-driven GTM workflows.
Another example:
Call the enrichment API from Claude or Cursor via MCP. Turn prompts into verified B2B contacts and company intelligence.
Avoid descriptions that are too short to add value:
Bad:
One API call
Better:
Enrich people and companies in one API call. Built for developers, GTM engineers, and AI-agent workflows.
Clarity hierarchy
For cold audiences, write in this order:
- Product category
- Use case
- Input → output
- Differentiator
- Pain point
- Brand personality
Example:
B2B Lead Enrichment API
Turn emails and domains into verified contacts, company data, and signals.
Built for developers, GTM engineers, and AI agents.
Do not start with abstract brand positioning unless the audience already knows the category.
Good hooks
Hooks should be clear, not mysterious.
Strong hooks:
- Turn any email into a full B2B lead profile.
- Your Claude agent can find and enrich B2B leads.
- Replace manual enrichment workflows with one API.
- Build a lead generation system without spreadsheets.
- Stop paying for failed enrichment lookups.
- Enrich contacts directly from Claude via MCP.
Weak hooks:
- The GTM stack changed.
- Your agent can call this.
- The prompt is the product.
- Build systems, not workflows.
- APIs are the new system.
Weak hooks can become supporting copy after the product is clear.
Use line breaks intentionally
Meta ads are scanned quickly. Use blank lines to create rhythm.
Good:
Your Claude agent can find and enrich B2B leads.
Type a prompt.
DataLayer returns verified contacts + company data instantly.
Bad:
Your Claude agent can find and enrich B2B leads. Type a prompt. DataLayer returns verified contacts and company data instantly.
Be specific about inputs and outputs
Whenever possible, show the transformation.
Examples:
- Email → person + company profile
- Domain → company intelligence
- Prompt → verified lead
- LinkedIn URL → contact data
- Company name → decision makers
This makes the value easier to understand.
Match copy to creative
Do not make the copy fight the image.
If the image shows a prompt, use prompt-native copy. If the image shows email enrichment, use email → person copy. If the image shows pricing, use predictable pricing copy. If the image shows a comparison, use replacement or alternative copy.
Every ad should have one dominant idea.
Avoid these patterns
Do not write:
- Generic SaaS claims: “supercharge growth,” “unlock revenue,” “10x your pipeline”
- Clever but unclear headlines
- Abstract category language without concrete explanation
- Long feature lists in primary text
- Overly broad claims that could apply to any B2B tool
- Descriptions that repeat the headline without adding information
Better pattern
Use this formula:
<Specific product/use case>
<Input → output transformation>
<Best differentiator or buyer-specific benefit>
Example:
B2B Lead Enrichment API for Claude.
Turn prompts into verified contacts and company data.
Call DataLayer via MCP from Claude Code, Cursor, or your own agent.
Rewrite checklist
Before finalizing ad copy, check:
- Does the headline clearly say what is being sold?
- Would a cold audience understand the product in 3 seconds?
- Does the primary text use line breaks for readability?
- Does the description add real selling detail?
- Is the use case specific enough?
- Is the copy matched to the visual creative?
- Is there one main idea only?
- Are vague words replaced with concrete nouns?
Example transformation
Original:
Primary Text:
Your agent can find leads.
Headline:
Find leads with Claude
Description:
MCP-native enrichment API
Improved:
Primary Text:
Your Claude agent can find and enrich B2B leads.
Type a prompt.
DataLayer returns verified contacts + company data instantly.
Headline:
B2B Lead Enrichment API for Claude
Description:
Call DataLayer via MCP to turn prompts into real contacts. Enrich people and companies in one API call. Built for Claude Code, Cursor, and AI agents.
Tone
Use direct, specific, plain language.
The copy should feel like a clear product description with a sharp benefit — not like a brand manifesto.
Prefer:
Email Enrichment API for GTM Teams
Over:
The Future of GTM Starts Here