Token导航 LogoToken导航

Agent Skill · 开发

meta-ads-integration(元广告集成)

meta-ads-integration 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

meta-ads-integration 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为操作浏览器;许可证信息还不明确,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 13,063。

总安装 1,028周安装 42GitHub Stars 19下载 329核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:meta-ads-integration(元广告集成)
来源仓库:https://github.com/finsilabs/awesome-ecommerce-skills
仓库路径:skills/meta-ads-integration
安装命令:
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill meta-ads-integration
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill meta-ads-integration

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

meta-ads-integration 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态、代码变更或协作事项进行整理。

通过 npx skills add 命令从指定 GitHub 仓库安装并使用该技能。安装前需确认权限范围、维护状态,注意是否涉及联网、命令执行或文件读写操作。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/meta-ads-integration

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill met…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要操作浏览器,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

meta-ads-integration 怎么安装?

在终端执行 npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill meta-ads-inte…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

meta-ads-integration 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

meta-ads-integration 需要什么权限?

权限级别是操作浏览器。该 Skill 可能涉及浏览器控制能力,使用时可能读取或操作网页内容,需要在受控环境中确认权限边界。

meta-ads-integration 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

meta-ads-integration 用的人多吗?

公开数据是累计安装 1,028 次,近一周安装 42 次,下载 329 次,GitHub 19 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

meta-ads-integration 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
meta-ads-integration

元广告集成 · 本页

1,02819操作浏览器未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Meta Ads Integration

Overview

Meta (Facebook/Instagram) is the dominant paid social channel for ecommerce, but reliable attribution requires pairing the browser-based Meta Pixel with server-side Conversions API (CAPI). Post-iOS 14, browser signals alone under-report 30–60% of conversions; CAPI restores signal fidelity by sending purchase events directly from your server. For Shopify, WooCommerce, and BigCommerce, official integrations handle both Pixel and CAPI automatically — no custom code required. Custom code only belongs in the Custom/Headless section.

When to Use This Skill

  • When setting up Meta advertising for a new ecommerce store
  • When conversion data in Ads Manager looks under-reported after iOS 14 rollout
  • When launching Dynamic Product Ads (DPA) and needing catalog feed sync
  • When ROAS is declining and you need to restore the signal quality Meta's algorithm relies on
  • When adding retargeting audiences based on product viewers and add-to-cart events

Core Instructions

Step 1: Choose your integration approach

PlatformRecommended MethodCAPI SupportCatalog Sync
ShopifyNative Meta Sales ChannelYes (built-in)Yes (automatic)
WooCommerceFacebook for WooCommerce pluginYes (built-in)Yes (automatic)
BigCommerceMeta channel in Channel ManagerYes (built-in)Yes (automatic)
Custom / HeadlessMeta Pixel + facebook-nodejs-business-sdkManual CAPI implementationManual feed generation

All three major platforms have official Meta integrations that install both the Pixel and CAPI in a single setup — use these rather than manually pasting Pixel code.

Step 2: Connect your platform to Meta


Shopify
  1. Go to Shopify Admin → Sales Channels → + → Facebook & Instagram
  2. Install the Facebook & Instagram sales channel
  3. Connect your Meta Business Manager account and select your Facebook Page and Ad Account
  4. Under Data Sharing, select Maximum — this enables server-side CAPI in addition to the browser Pixel
  5. Shopify automatically:

- Installs the Meta Pixel on all pages - Fires ViewContent, AddToCart, InitiateCheckout, and Purchase events - Sends the same events via CAPI from Shopify's servers (deduplication handled automatically) - Syncs your product catalog to Meta Commerce Manager for Dynamic Product Ads

  1. Go to Facebook & Instagram → Overview to verify pixel connection status
  2. In Meta Events Manager → Data Sources → [Your Pixel]: check Event Match Quality (EMQ) score — aim for 7+/10

WooCommerce
  1. Install Facebook for WooCommerce (free, official Meta plugin) from the WordPress plugin directory
  2. Go to WooCommerce → Facebook → Get Started and connect your Meta Business Manager account
  3. Under Facebook Connection → Data Sharing Level: select Maximum
  4. The plugin installs the Meta Pixel across all pages and fires standard events automatically
  5. CAPI is enabled automatically under the Maximum data sharing setting
  6. Go to WooCommerce → Facebook → Product Sync to trigger an initial product catalog sync to Meta Commerce Manager
  7. Verify catalog sync status in Meta Commerce Manager → Catalog → Data Sources

BigCommerce
  1. Go to BigCommerce Admin → Channel Manager → Add a Channel
  2. Select Facebook & Instagram
  3. Connect your Meta Business Manager account
  4. Enable Enhanced Conversions (CAPI) during setup
  5. BigCommerce syncs your product catalog automatically and registers it in Meta Commerce Manager for Dynamic Product Ads
  6. Check product sync status in Channel Manager → Facebook & Instagram → Products

Custom / Headless

For headless stores, you must install both the browser Pixel and server-side CAPI manually.

Browser-side Pixel (add to <head> on every page):

// Replace YOUR_PIXEL_ID with your Pixel ID from Meta Events Manager
fbq('init', 'YOUR_PIXEL_ID');
fbq('track', 'PageView');

// Product page
fbq('track', 'ViewContent', {
  content_ids: [product.sku],
  content_type: 'product',
  value: product.price,
  currency: 'USD',
});

// Purchase — pass eventID for deduplication with CAPI
const purchaseEventId = `purchase-${orderId}`;
fbq('track', 'Purchase', {
  content_ids: order.lineItems.map(i => i.sku),
  value: order.subtotal,
  currency: order.currencyCode,
  order_id: order.id,
}, { eventID: purchaseEventId });

Server-side CAPI (send from your order webhook):

import { FacebookAdsApi, ServerEvent, UserData, CustomData, EventRequest } from 'facebook-nodejs-business-sdk';

FacebookAdsApi.init(process.env.META_CAPI_ACCESS_TOKEN!);

async function trackPurchaseCapi(order: Order, req: Request) {
  const eventId = `purchase-${order.id}`; // MUST match the eventID passed to fbq()

  const userData = new UserData()
    .setEmail(order.customerEmail)    // SDK hashes PII automatically (SHA-256)
    .setPhone(order.customerPhone)
    .setFirstName(order.customerFirstName)
    .setLastName(order.customerLastName)
    .setZip(order.shippingAddress?.zip)
    .setCountry(order.shippingAddress?.countryCode)
    .setClientIpAddress(req.ip)
    .setClientUserAgent(req.headers['user-agent'] as string)
    .setFbp(req.cookies['_fbp'])   // _fbp cookie = browser identity signal
    .setFbc(req.cookies['_fbc']);  // _fbc cookie = click identity signal

  const customData = new CustomData()
    .setValue(order.subtotal)
    .setCurrency(order.currencyCode)
    .setContentIds(order.lineItems.map(i => i.sku))
    .setContentType('product')
    .setNumItems(order.lineItems.length)
    .setOrderId(order.id);

  const event = new ServerEvent()
    .setEventName('Purchase')
    .setEventId(eventId)
    .setEventTime(Math.floor(Date.now() / 1000))
    .setUserData(userData)
    .setCustomData(customData)
    .setActionSource('website');

  await new EventRequest(process.env.META_CAPI_ACCESS_TOKEN!, process.env.META_PIXEL_ID!)
    .setEvents([event])
    .execute();
}

Product Catalog Feed for Dynamic Product Ads: Generate a CSV feed and serve it at a stable URL. Register it in Meta Commerce Manager → Catalog → Data Sources → Add Data Feed.

// Generate CSV with required columns: id, title, description, availability, condition, price, link, image_link, brand
// Schedule regeneration every 4 hours — serve at a stable /feeds/meta-catalog.csv endpoint

Step 3: Campaign structure for ecommerce

Build a three-tier campaign structure in Meta Ads Manager:

Campaign 1: Prospecting

  • Objective: Sales → Purchases
  • Budget: 60% of total Meta budget
  • Audience: Broad (US 18–65, no interest targeting) — use Advantage+ targeting
  • Ads: 3–5 creatives (static image, video, carousel, UGC)
  • Use Advantage+ Shopping Campaigns (ASC) — Meta's automated format consistently outperforms manual campaign structures for ecommerce

Campaign 2: Retargeting

  • Budget: 30% of total Meta budget
  • Ad Set 1: Viewed product but did not add to cart (last 7 days)

- Audience: Website custom audience → ViewContent event, last 7 days - Ads: Dynamic Product Ads (DPA) carousel showing viewed products

  • Ad Set 2: Added to cart but did not purchase (last 3 days)

- Audience: Website custom audience → AddToCart, last 3 days; exclude Purchases last 3 days - Ads: DPA + urgency messaging

Campaign 3: Retention / LTV

  • Budget: 10% of total Meta budget
  • Ad Set: Customer list audience (upload from Shopify → Customers export)

- Exclude customers who purchased in the last 30 days - Ads: New arrivals, cross-sell products

  • Ad Set: 1% Lookalike of top purchasers (great for prospecting)

Step 4: Set up Dynamic Product Ads

For Shopify and WooCommerce, the official integrations auto-sync the product catalog. Verify setup:

  1. Go to Meta Commerce Manager → Catalogs → [Your Catalog]
  2. Check Data Sources — confirm your platform's feed is syncing and last updated within 24 hours
  3. Check Items — verify products show correct prices, availability, and images
  4. In Ads Manager → Create Ad Set: select your catalog under Catalog Sales campaign objective
  5. Choose Dynamic formats and creatives — Meta automatically selects the best ad format per user

Step 5: Verify Event Match Quality

In Meta Events Manager → Data Sources → [Your Pixel] → Overview:

SignalHow to Improve
EMQ below 6Send more user data (email, phone, fbp/fbc cookies)
CAPI not firingCheck platform integration is set to Maximum data sharing
Duplicate conversionsVerify deduplication — eventID must match between Pixel and CAPI
ViewContent not firingCheck the platform integration is active and pixel is on product pages

Best Practices

  • Use Advantage+ Shopping Campaigns (ASC) for prospecting — Meta's automated campaign type consistently outperforms manual structure for ecommerce; start here, not manual campaigns
  • Set data sharing to Maximum on Shopify/WooCommerce — this single setting enables CAPI and is worth significantly more accurate attribution than the default
  • Pass _fbp and _fbc cookies in CAPI — these are the strongest identity signals for iOS 14+ attribution; include them in every CAPI event
  • Use order_id as the deduplication key — prevents duplicate conversion counting when both Pixel and CAPI fire for the same purchase
  • Exclude recent purchasers from prospecting — add a 30-day purchaser exclusion to cold campaigns to protect budget
  • Refresh creative every 4–6 weeks — Meta campaigns show creative fatigue quickly; rotate 3–5 variations per ad set

Common Pitfalls

ProblemSolution
Duplicate purchase conversions in Ads ManagerEnsure eventID is identical in both Pixel and CAPI calls for the same event; Shopify's native integration handles this automatically
Conversions under-reported after iOS 14Set data sharing to Maximum in the Shopify Facebook channel settings or enable CAPI in WooCommerce Facebook plugin
Dynamic Product Ads show wrong priceShopify/WooCommerce catalog syncs happen up to every 24 hours; for time-sensitive price changes, trigger a manual sync
Low EMQ score despite native integrationGo to Meta Events Manager → check that both browser and server events are showing; verify the integration is fully authorized
iOS 14+ campaign reach is lowGo to Meta Business Manager → Brand Safety → Domains → Verify your domain; enable Aggregated Event Measurement
Ad account disabledNever send raw (unhashed) PII through the API; use the official SDK which hashes all data automatically

Related Skills

  • @google-ads-ecommerce
  • @tiktok-ads-integration
  • @google-shopping-feed
  • @email-marketing-automation
  • @marketing-attribution-dashboard

平台分布

Codex

31.82%
按下载量换算105

Claude

30.29%
按下载量换算100

Cursor

19.75%
按下载量换算65

Gemini CLI

10.08%
按下载量换算33

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

操作浏览器

该 Skill 可能涉及浏览器控制能力,使用时可能读取或操作网页内容,需要在受控环境中确认权限边界。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills