Growth-Today/claude-skills / gt-meta-ads
gt-meta-ads
VerifiedGT 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.
| File | Kind | Size |
|---|---|---|
| .claude/skills/audiences/gt-SKILL.md | markdown | 4.2 KB |
| .claude/skills/audit/gt-SKILL.md | markdown | 5.0 KB |
| .claude/skills/campaign-setup/gt-SKILL.md | markdown | 4.8 KB |
| .claude/skills/creative-fatigue/gt-SKILL.md | markdown | 3.9 KB |
| .claude/skills/creative/gt-SKILL.md | markdown | 5.1 KB |
| .claude/skills/lead-forms/gt-SKILL.md | markdown | 4.5 KB |
| .claude/skills/learning-phase/gt-SKILL.md | markdown | 3.7 KB |
| .claude/skills/measurement/gt-SKILL.md | markdown | 5.6 KB |
| .claude/skills/tracking/gt-SKILL.md | markdown | 3.9 KB |
| CHANGELOG.md | markdown | 8.1 KB |
| README.md | markdown | 1.5 KB |
| SKILL.md | skill md | 8.4 KB |
| resources/references/2026-ai-updates.md | markdown | 2.7 KB |
| resources/references/audit-checklist.md | markdown | 5.0 KB |
| resources/references/b2b-vs-b2c-guardrail.md | markdown | 3.1 KB |
| resources/references/benchmarks.md | markdown | 3.3 KB |
| resources/references/creative-formats.md | markdown | 2.7 KB |
| resources/references/crm-attribution.md | markdown | 4.8 KB |
| resources/references/tracking-hygiene.md | markdown | 2.7 KB |
.claude/skills/measurement/gt-SKILL.md
View on GitHub---
name: meta-ads-measurement
description: Meta Ads measurement for B2B — CAPI-backed reporting, pipeline attribution, KPIs by funnel stage, and optimising to pipeline not CPL. Use for Meta measurement, reporting, KPIs, pipeline attribution, cost per result, what metrics to track, measuring B2B Meta, optimise to pipeline. Triggers on "measurement", "reporting", "KPIs", "pipeline attribution", "cost per result", "what metrics", "measuring Meta", "CPL vs pipeline", "ROAS Meta". Do NOT use for Pixel/CAPI setup (use tracking) or fatigue metrics (use creative-fatigue).
---
# Meta Ads Measurement (B2B)
The most common B2B Meta mistake is judging the channel on raw CPL, seeing a high number, and declaring "Meta doesn't work". Proper measurement tracks at multiple funnel levels and attributes the final business outcome — pipeline, deals, revenue — back to Meta's contribution.
## Instructions
1. Measure at each funnel stage with the right metric for that stage
2. Trust trends over time, not absolute benchmarks
3. Attribute to pipeline and revenue via CRM-synced offline data
4. Read creative via spend allocation, not just ad-level CPA
5. Optimise the account to pipeline, not cheap leads
## KPIs by Funnel Stage
| Stage | Primary metrics | Note |
|-------|-----------------|------|
| Awareness (TOF) | CPM, video completion (25%+ strong for B2B), reach, frequency | Deliverable is a retargeting pool, not conversions. Hold frequency 1.5-2.5/7 days. |
| Consideration (MOF) | CPL for low-friction offers, Instant Form completion rate (10-15% healthy), lead-quality signal | Watch quality, not just cost. |
| Conversion (BOF) | CPL on real offers, retargeting CTR (~1.2-1.8%), LP/form conversion rate (15-25% warm) | This is where pipeline gets created. |
| Business outcome | Cost per SQL, pipeline created, deals won, revenue | The only numbers leadership should judge Meta on. |
## Trend Over Absolute
There is no universal benchmark — cost per result depends on vertical, offer, creative, and temperature. If cost-per-result is improving week over week, the funnel is healthy regardless of how it compares to someone else's average. Track your own trend line.
## Attribute to Pipeline (the B2B unlock)
- Browser-only reporting under-counts; lean on **CAPI-backed** data (see tracking).
- Sync CRM outcomes back as offline conversions: lead → MQL → SQL → opportunity → closed-won. Now you can attribute Meta to pipeline and revenue, not just form-fills.
- Meta-reported numbers and CRM reality diverge (attribution windows, view-through, iOS). Reconcile against the CRM; treat platform-reported ROAS as directional, pipeline as truth.
- Respect the long B2B cycle: judge over a full consideration window, not the first two weeks. An awareness campaign with no direct conversions may be feeding the retargeting pool that closes later.
## Reading Creative (2026 delivery caveat)
- Under sequenced GEM delivery, **ad-level CPA is not a reliable read of creative quality** — a high-CPA ad may be assisting conversions elsewhere.
- Use the metric stack: thumbstop (hook), CTR (message), spend allocation (algorithm trust), CPA (profitability). **Spend allocation is now the strongest single signal** of which creative the algorithm trusts.
## Optimise to Pipeline, Not CPL
The whole point: configure tracking, events, and bidding so Meta chases qualified pipeline. Cheap leads the algorithm can always find; pipeline is the goal. If sales says the leads are junk while CPL looks great, the measurement loop is open — close it with offline conversions and quality feedback.
## Examples
Example 1: "How do I measure B2B Meta properly?"
→ Track stage-appropriate metrics (CPM/VCR awareness, CPL/form-rate consideration, pipeline at the bottom), trust week-over-week trend, attribute to CRM pipeline via offline conversions, and read creative by spend allocation not ad-level CPA.
Example 2: "My boss says Meta doesn't work because CPL is high."
→ Raw CPL is the wrong verdict. Measure to pipeline: sync CRM outcomes back, compare cost per SQL and pipeline created, and read the trend over a full B2B cycle before judging.
## Incrementality — Meta Conversion Lift
The causal answer to "is Meta actually working?" Meta's **Conversion Lift** splits the audience into treatment (sees ads) and control (doesn't) at the account level and measures the difference via Pixel/CAPI/offline uploads.
- **Requirements:** min ~7-day test, ≥10% of audience per cell, ~5,000+ users in the target group, 300+ conversions for significance; most tests run 3–4 weeks. Some Conversion Lift access needs a Meta Business Partner / rep.
- **Use when** spend is meaningful and the exec question is incrementality; below that, lean on CRM-based attribution.
- **For the CRM attribution loop** (offline conversions from HubSpot/Salesforce, fbclid matching, models) → Read `{SKILL_BASE}/resources/references/crm-attribution.md` (CRM build itself: gt-hubspot-admin / gt-salesforce-admin).
## Tracking hygiene & reporting
For domain verification, Aggregated Event Measurement, CAPI Gateway, standard-vs-custom events, Event Match Quality, UTM standardization, and breakdown reporting (all B2B) → Read `{SKILL_BASE}/resources/references/tracking-hygiene.md`.
## B2B guardrail
Before applying any generic Meta tactic or benchmark here, check `{SKILL_BASE}/resources/references/b2b-vs-b2c-guardrail.md` — most public Meta advice is DTC/e-commerce and does not transfer to B2B.
---
*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*
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| 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 available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |