← 返回
未分类 Key 中文

Meta Ads Lead Gen Analysis

[Didoo AI] Specialized analysis module for Meta lead generation campaigns. Use when CPL is elevated, lead quality is unclear, or you need to diagnose why lea...
[Didoo AI] Specialized analysis module for Meta lead generation campaigns. Use when CPL is elevated, lead quality is unclear, or you need to diagnose why lea...
elias-didoo elias-didoo 来源
未分类 clawhub v1.1.0 1 版本 100000 Key: 需要
★ 0
Stars
📥 411
下载
💾 0
安装
1
版本
#analysis#didoo-ai#latest#lead-gen#meta-ads

概述

Required Credentials

CredentialWhere to GetUsed ForOAuth Scope
----------------------------------------------
META_ACCESS_TOKENMeta Developer Console → Graph API Explorer → Generate TokenFetching campaign and form integration dataads_read (read-only)
META_AD_ACCOUNT_IDAds Manager URL: adsmanager.facebook.com/act_XXXXXXXXXIdentifying which account to query

When to Use

When running lead generation campaigns and standard e-commerce analysis logic doesn't apply. Specifically for:

  • CPL is higher than expected or target
  • Lead volume is healthy but conversion rate to closed deals is low (quality problem)
  • LPV rate looks fine but form submit rate is unknown
  • CAPI may not be sending offline lead data back to Meta
  • Not sure if the problem is the ad, the audience, or the form itself

Lead gen has fundamentally different metrics than e-commerce — standard CVR and LPV benchmarks don't apply. Use this skill instead of applying e-commerce logic to lead gen campaigns.


Key Differences from E-commerce Analysis

MetricE-commerce BenchmarkLead Gen BenchmarkWhy It Differs
------------
LPV Rate> 70% is healthy> 50% is healthyMany leads browse without intent to submit
Form Submit RateN/A> 20% is healthyForm friction is the primary drop-off point
CPLVaries by industryThe primary metricWhat you're actually paying for
CVR (post-click)Purchase rateLead-to-qualified rateMeta can't see what happens after form submit
Attribution1-day or 7-day click7-day click usuallyLonger window for consideration

Step 1: Gather Lead Gen Specific Data

Pull these metrics at the campaign and adset level:

  • Spend, impressions, CTR
  • LPV Rate (Landing Page View rate = landing page views / link clicks)
  • Form Submit Rate (if available — requires CAPI or form integration)
  • CPL (cost per lead)
  • Frequency
  • Lead volume vs. prior period

Also ask the user:

  • What does a "good lead" look like for their business?
  • What's their lead-to-close rate historically?
  • Are they using CAPI to send offline lead data back to Meta?

Step 2: CAPI Verification — Critical for Lead Gen

Without CAPI sending offline lead data back to Meta:

  • Meta is optimizing for form submissions, not qualified leads
  • CPL shown may be "form submit cost" not "actual lead cost"
  • The algorithm can't learn which leads actually convert

How to verify CAPI is connected:

  1. Go to Meta Events Manager → select your pixel
  2. Check "About CAPI" — status should be green/active
  3. Ask: are offline leads (calls, CRM-qualified leads) being sent back via CAPI?

If CAPI is NOT connected for offline leads:

  • This is a priority fix — it will lower CPL over 2–3 weeks
  • Recommend a CRM integration or Zapier/Make workflow
  • Or use Meta's Lead Forms (form submission = conversion automatically tracked)

Step 3: Audience Targeting Analysis for Lead Gen

Cold Audiences (Interest-Based Targeting)

  • Interest targeting works for cold audiences
  • Frequency builds fast — limit budget to avoid rapid fatigue
  • Test narrower interest layers (2–3 stacked interests, not broad categories)

Custom Audiences (Retargeting and Lookalikes)

  • Website visitors (pixel): typically highest conversion rate
  • Email lists (matched audiences): strong for existing customer re-engagement
  • Lookalikes (LAL): based on converter audiences, quality depends on seed list quality
  • Test LAL layers 1–3% first — wider LAL = lower quality but more volume

Step 4: Format Output

Lead Gen Health Summary:

  • Spend / CPL / Lead Volume
  • LPV Rate vs. benchmark (> 50% healthy for lead gen)
  • Form Submit Rate (if available)
  • CAPI Status (connected / not connected)

SECTION 1: CAPI Gap (if applicable)

State whether offline lead data is being sent to Meta. Impact: algorithm is optimizing for quantity, not quality.

SECTION 2: Audience Diagnosis

Diagnose targeting based on frequency and CPL — is the audience too broad or well-matched?

SECTION 3: Funnel Stage

Identify the CPL bottleneck stage:

  • LPV < 50% → Ad-to-Form disconnect
  • LPV ≥ 50% but low leads → Form friction (check form fields)
  • LPV and CVR OK but CPL high → Audience mismatch or CAPI not connected

> LP Landing Page diagnosis: The full LP disconnect diagnostic (Step 4a–4d) lives in meta-ads-recommendation → Step 4. This skill identifies the funnel stage; recommendation prescribes the fix.


Session Context — What This Skill Writes

After completing analysis, store the following in session context:

KeyDescriptionExample
---------------------------
lp_diagnosisFunnel stage causing the CPL problem"Form friction — submit rate 12%, below 20% benchmark"
capi_statusWhether offline leads are being sent to Meta"Not connected — offline lead data not flowing"
cpl_breakdownWhich stage is the bottleneck"LPV 65% OK; Form submit 11% is the bottleneck"
recommended_fix_priorityRanked fix order"1. CAPI 2. Form fields 3. Audience"

> meta-ads-recommendation reads these keys to produce the lead gen action plan.


Key Collision Resolution

> ⚠️ Key priority: meta-ads-analysis writes lp_diagnosis_general; this skill writes lp_diagnosis (the lead-gen-specific version). meta-ads-recommendation is configured to prefer lp_diagnosis when available — so running both skills in sequence does NOT cause overwriting. The two keys coexist.


Rules

  • Apply lead gen benchmarks, not e-commerce benchmarks
  • Always verify CAPI status before diagnosing CPL issues — missing CAPI is the most common cause of misleading CPL data
  • Do not recommend creative changes if form friction is the bottleneck
  • Do not recommend audience changes if LPV rate indicates a page problem
  • This is analysis only — recommendations route to meta-ads-recommendation

版本历史

共 1 个版本

  • v1.1.0 当前
    2026-05-07 08:47 安全 安全

安全检测

腾讯云安全 (Keen)

安全,无风险
查看报告

腾讯云安全 (Sanbu)

安全,无风险
查看报告

🔗 相关推荐

business-ops

Discord

steipete
当需要通过discord工具控制Discord时使用:发送消息、添加反应、发布或上传表情包、上传表情、创建投票、管理帖子/置顶/搜索、获取权限或成员/角色/频道信息,或在Discord私信或频道中处理管理操作。
★ 78 📥 37,924
business-ops

Stripe

byungkyu
Stripe API 集成,支持托管 OAuth,实现对客户、订阅、发票、产品、价格和支付的可写金融集成。
★ 27 📥 25,933
business-ops

Trello

steipete
使用 Trello REST API 管理看板、列表和卡片
★ 161 📥 41,171