Skip to content

Growth-Today/claude-skills / gt-meta-ads

gt-meta-ads

Verified

GT Meta Ads — expert Meta (Facebook and Instagram) Ads strategist for B2B companies, built by Growth Today (growthtoday.co). Use when asking about Meta ads, Facebook ads, Instagram ads, Advantage+, custom audiences, lookalike audiences, creative fatigue, Pixel and Conversions API (CAPI), learning phase, Meta funnel structure, retargeting, Instant Forms, Meta lead gen, ad creative strategy, frequency capping, or B2B paid social on Meta. Triggers on: Meta ads, Facebook ads, Instagram ads, Advantage+, custom audience, lookalike, creative fatigue, CAPI, Conversions API, Pixel, learning phase, Instant Forms, Opportunity Score, offline conversions, Meta retargeting, frequency cap, Reels ads. Do NOT use for LinkedIn Ads (use gt-linkedin-ads), Google Ads (use gt-google-ads), or organic social content. More GT skills: growthtoday.co.

.claude/skills/lead-forms/gt-SKILL.md

View on GitHub
---
name: meta-ads-lead-forms
description: Meta Ads Instant Forms and lead quality for B2B — form length tradeoffs, qualification, CRM sync, and lead nurture. Use for Instant Forms, lead ads, lead generation forms, lead quality, form length, qualifying questions, CRM sync, lead follow-up speed. Triggers on "Instant Form", "lead form", "lead ads", "lead quality", "form length", "qualifying questions", "CRM sync", "lead follow up", "junk leads". Do NOT use for tracking/CAPI (use tracking) or measurement reporting (use measurement).
---

# Meta Ads Instant Forms & Lead Quality (B2B)

This is the dimension the competitor's pack omits: a flood of cheap Instant Form leads is not a win if sales cannot use them. For B2B, lead quality and speed-to-follow-up are the whole game. Instant Forms remove friction (pre-filled fields, on-platform), which lifts volume but lowers intent — so you must design for quality and sync fast.

## Instructions

1. Use Instant Forms for low-friction volume; landing pages for higher intent
2. Tune form length to balance volume against lead quality
3. Add qualifying questions to filter out non-buyers
4. Sync leads to the CRM in real time and follow up fast
5. Feed lead quality back to optimisation (see measurement)

## Instant Form vs Landing Page

| | Instant Form | Landing page |
|---|---|---|
| Friction | Very low (pre-filled, on-platform) | Higher (click out, load, fill) |
| Volume | Higher | Lower |
| Lead quality / intent | Lower (easy to submit absentmindedly) | Higher (more deliberate) |
| Best for | MOFU offers, webinars, guides, top-of-list capture | High-ACV, sales-led, where quality > volume |

Run both and compare on **pipeline**, not CPL. Instant Form CPL will look better; landing-page leads often qualify better. The carousel + lead-form combo can lift qualified leads at lower CPL for the right offer.

## Form Length vs Lead Quality

- **Short forms** (name, email) → max volume, lowest quality. Fine for top-of-funnel content.
- **Longer forms** (4-5 fields) → for B2B with $20k+ ACV the slight volume drop is worth the big quality lift. The friction itself filters.
- Use the "higher intent" form option (review step before submit) when quality matters more than raw count.

## Qualifying Questions

- Add a qualifying question or two (company size, role, budget, timeline, use case). These filter out non-buyers before they hit the CRM and give sales context.
- Custom questions (short answer / multiple choice) cut tyre-kickers more than relying on auto-filled contact fields alone.

## CRM Sync & Speed-to-Lead

- **Sync in real time.** Instant Form leads sitting in Meta unsynced go cold fast. Pipe to the CRM immediately (native integration, or via the GT stack — n8n / HubSpot).
- **Speed-to-follow-up is decisive in B2B.** The lead filled a form on a social feed, not a buying-intent search — momentum fades in minutes. Route to fast follow-up (sequence + human).
- Map every form field to a CRM field so qualification data is usable, not stranded.

## Close the Quality Loop

- Pass lead outcome (MQL / SQL / junk / closed-won) back from the CRM as offline conversions so Meta optimises toward leads that become pipeline, not just form-fills (see measurement, tracking). Without this you are training the algorithm to find more easy-form-fillers.

## Examples

Example 1: "My Meta Instant Forms get tons of leads but they're low quality."
→ Add qualifying questions, lengthen the form (4-5 fields for high-ACV), use the higher-intent form option, sync to CRM in real time with fast follow-up, and feed lead outcomes back as offline conversions so Meta optimises to quality.

Example 2: "Instant Form or landing page for B2B?"
→ Instant Form for low-friction MOFU volume, landing page for high-ACV intent. Run both, compare on pipeline not CPL, and qualify hard if you lean on Instant Forms.


## 2026 updates

For Opportunity Score, Advantage+ 2026 changes (25/wk threshold, Predictive Budget Allocation), gen-AI Creative Enhancements, Advantage+ Leads, and Threads placements → Read `{SKILL_BASE}/resources/references/2026-ai-updates.md`.
## CRM attribution

For sending CRM outcomes back to Meta as offline conversions (HubSpot/Salesforce, Meta CAPI, fbclid matching) → Read `{SKILL_BASE}/resources/references/crm-attribution.md`.
---

*Created by [Growth Today](https://www.growthtoday.co) — AI-native GTM engineering firm. Maintained and updated by [Brigitta Ruha](https://www.linkedin.com/in/brigittaruha/). More open Claude Skills for go-to-market teams: https://www.growthtoday.co/claude-skills*
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall