New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Meta Pixel Setup

by ooiyeefei in ooiyeefei/ccc

Walks a site owner through installing the Meta Pixel, firing one conversion event and verifying it with the Pixel Helper before any ads run.

MITAuto-check passedMarketing & SEO

Install Meta Pixel Setup

skills CLI
$ npx skills add ooiyeefei/ccc --skill meta-pixel-setup -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ooiyeefei/ccc meta-pixel-setup --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ooiyeefei/ccc.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/meta-pixel-setup .claude/skills/meta-pixel-setup && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
meta-pixel-setup
GitHub stars
494
Token cost
~2.4k tokens
SKILL.md length
1,110 words
Files
6 (incl. references)
Skills in repo
22
Repo updated
First seen
Licence
MIT

At a glance

Walks a site owner through installing the Meta Pixel, firing one conversion event and verifying it with the Pixel Helper before any ads run.

  • Works in 5 steps: Create or find the Pixel/Dataset (get… → (Optional) Reuse an existing pixel → Install the base code → …
  • Adding the Meta or Facebook Pixel to a website for the first time
  • SKILL.md covers Start where the user is, Decision 1: Pixel only, or +…, Decision 2: the Dataset… and 1. Create or find the…, plus 6 more sections
  • Reaches connect.facebook.net and facebook.com

What it does

The skill takes a website from no tracking to a verified conversion event for Facebook and Instagram ads. It begins by asking where the person already is: whether a Facebook Page and Business Suite or business portfolio exist, whether there is a Pixel (now labelled a Dataset in the interface) and its ID, which single conversion matters, and what the site is built with. Anything already set up is reused instead of recreated.

Two decisions are put up front because people often get them wrong. One is whether to use the browser Pixel alone or add the Conversions API, which Meta's wizard pushes; the skill advises starting with the Pixel, since the API needs server work and customer data sent to Meta, which widens the privacy and compliance exposure. The other is which data category to declare, because a wrong choice can throttle ads. Reference files cover the Conversions API, install steps by platform, standard events and a verification checklist.

When your agent uses it

  • Adding the Meta or Facebook Pixel to a website for the first time
  • Setting up a Lead, CompleteRegistration or Purchase event for Meta ads
  • Finding the Pixel or Dataset ID inside Events Manager
  • Debugging a Pixel whose events never fire
  • Deciding whether Meta's push toward the Conversions API applies to you

Example prompts

  • “Install the Meta Pixel on my Next.js landing page and fire a Lead event when the waitlist form is submitted.”
  • “Meta's wizard keeps recommending the Conversions API, so tell me whether I need it before my first ads.”
  • “The Pixel Helper shows no events on my checkout page, so help me work out why.”

Requirements

  • A Facebook Page and Meta Business Suite access
  • Access to the website's code or tag settings
  • The Meta Pixel Helper for verification

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Create or find the Pixel/Dataset (get the ID)
  2. (Optional) Reuse an existing pixel
  3. Install the base code
  4. Fire the conversion event on the action
  5. Verify BEFORE you spend — the gate

What it can do on your machine

Read from SKILL.md and the folder at commit c0fd926. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are html).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • connect.facebook.net
    • facebook.com

    Also links to:

    • business.facebook.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Meta Pixel Setup loads about 2.4k tokens when it runs, and up to ~5.2k if it reads all its reference files. Until then it costs about 205 tokens; SKILL.md has 1,110 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~205
When it runs · the whole SKILL.md, loaded when a task matches
~2.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ooiyeefei/ccc at commit c0fd926, republished under its MIT licence (© ooiyeefei). 1,110 words, ~2,409 tokens.

Download SKILL.mdSave it as .claude/skills/meta-pixel-setup/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
meta-pixel-setup
description
Set up the Meta Pixel (Facebook/Instagram ads tracking) on a website and fire a conversion event (Lead, CompleteRegistration, Purchase) end to end. Guides the user through Business Suite / Events Manager, creating or finding the Pixel/Dataset ID, installing the base code, firing a standard event, and verifying it with the Meta Pixel Helper BEFORE running ads. Use whenever someone wants to add the Meta/Facebook Pixel, track FB/IG ad conversions, install "the pixel", find their Pixel/Dataset ID, set up a Lead or Purchase event for Meta ads, debug why Pixel events aren't firing, or is being pushed by Meta's wizard toward the Conversions API and isn't sure if they need it. Meets the user wherever they are — always asks what they've already set up (Facebook Page? Business Suite? a Pixel ID?) first.

Meta Pixel Setup

Get the Meta Pixel tracking a real conversion on a website, verified, so Facebook/Instagram ad optimization has something true to learn from. Two things trip people up and this skill front-loads both: the Pixel-vs-Conversions-API decision (Meta's wizard aggressively pushes the heavier one) and which data category to declare (a wrong choice can throttle your ads).

Naming note: Meta renamed "Pixel" to "Dataset" in the UI. A dataset contains the pixel and its Dataset ID = Pixel ID (a ~15–16 digit number). Treat the two words as the same thing.

Start where the user is

Setup is a chain: Facebook Page → Business portfolio → Events Manager → Pixel/Dataset (get the ID) → base code on site → conversion event → verify. People arrive mid-chain. Ask first, then jump in — don't re-create what exists (a business often already has a pixel; reuse it rather than fragmenting data across two).

Ask (adapt to what they've said):

  1. Do you have a Facebook Page and Meta Business Suite / Business portfolio set up already?
  2. Do you already have a Pixel / Dataset (in Events Manager)? If yes, what's the Dataset ID (the ~16-digit number)? Paste it — that may be all that's needed.
  3. What's the one conversion that matters (a lead/waitlist submit, a signup, a purchase)? This is what ads optimize toward.
  4. The site's stack + domain (Next.js, plain HTML, WordPress, Shopify) — decides how the code goes in.

If they already have the Dataset ID and a Page, skip straight to install (§3). Do not walk them back through account creation they've done.

Decision 1: Pixel only, or + Conversions API? (start with Pixel only)

Meta's setup wizard shows "Conversions API and Meta Pixel (Recommended)" with a shiny stat. Don't reflexively take it. Here's the honest trade-off:

  • Meta Pixel (browser) — a code snippet on the site sends events from the visitor's browser. Simple, no backend, works today. This is all you need to launch.
  • Conversions API (CAPI) — your server sends events directly to Meta. It's server-to-server, "developer support required," and to actually help it needs customer PII (email, phone, IP) sent to Meta for matching. That's more build and a bigger privacy/compliance surface (GDPR/PDPA/CCPA).

So: launch with the browser Pixel. Add CAPI later, only if browser signal loss (ad-blockers, iOS ATT) is measurably hurting you and you've resolved the PII/consent question. Treat CAPI as a post-launch optimization, not a setup step. Read references/conversions-api.md before ever wiring it — it exists to stop you sending personal data to Meta by accident.

Decision 2: the Dataset "category" — leave it blank unless it clearly fits

When creating the dataset, Meta asks to "select any applicable categories." This is a trap for finance/health/sensitive products. The dialog warns: "depending on the category and location, data sharing may be limited or blocked." Categories like "Financial service," "Economic vulnerability," "Personal hardship," "Nationality" trigger Meta's restricted-data handling and can throttle or block your ad optimization.

Rule: only tick a category if it accurately and unavoidably describes you, and you understand it restricts data. A budgeting/productivity/SaaS tool is software, not a "financial service" (that category is for lenders, credit reports, consumer finance). When in doubt, leave categories empty (it's optional) — empty means no restriction, which is what a normal waitlist/signup test wants.

1. Create or find the Pixel/Dataset (get the ID)

In Events Manager:

  1. Left rail → Connect data (green +) → Web → Meta Pixel → Connect. (Or if a dataset exists, click it — the ID is right under its name.)
  2. Name it after the business (e.g. "Acme Web"). For category, see Decision 2 (usually leave blank).
  3. Copy the Dataset ID — the ~16-digit number under the name. Also always visible later under Events Manager → Datasets.
  4. If it launches a "set up / connect your website" wizard offering Conversions-API vs Pixel-only — you can close/skip it. You only need the ID; the code goes in by hand (§3). If you do proceed, choose Meta Pixel only (Decision 1).
Show full SKILL.md (464 more words)Show less

2. (Optional) Reuse an existing pixel

A pixel is not a hard reporting wall like a GA4 property. One pixel can cover a whole domain — the main app and a /waitlist landing page. Distinguish funnels by the event + custom params (e.g. content_name: 'waitlist'), not by a second pixel. If the business already has one, reuse its ID.

3. Install the base code

Paste in <head> on every page, replacing YOUR_PIXEL_ID. It fires PageView automatically. (Copy your exact snippet from Events Manager — it has the ID pre-filled — or use this canonical form.)

html
<!-- Meta Pixel Code -->
<script>
!function(f,b,e,v,n,t,s)
{if(f.fbq)return;n=f.fbq=function(){n.callMethod?
n.callMethod.apply(n,arguments):n.queue.push(arguments)};
if(!f._fbq)f._fbq=n;n.push=n;n.loaded=!0;n.version='2.0';
n.queue=[];t=b.createElement(e);t.async=!0;
t.src=v;s=b.getElementsByTagName(e)[0];
s.parentNode.insertBefore(t,s)}(window,document,'script',
'https://connect.facebook.net/en_US/fbevents.js');
fbq('init', 'YOUR_PIXEL_ID');
fbq('track', 'PageView');
</script>
<noscript><img height="1" width="1" style="display:none"
  src="https://www.facebook.com/tr?id=YOUR_PIXEL_ID&ev=PageView&noscript=1"/></noscript>
<!-- End Meta Pixel Code -->

Do NOT add an integrity/SRI hash — fbevents.js is a versioned loader Meta updates in place and doesn't publish a stable hash for; SRI will break it. Framework-specific install (Next.js next/script, WordPress, Shopify, GTM) is in references/install-by-platform.md.

4. Fire the conversion event on the action

Use a standard event so Meta's optimization and reporting recognize it — Lead (waitlist/contact), CompleteRegistration (signup), Purchase (sale). Full list + when to use each: references/standard-events.md. Fire it only after the action truly succeeded, never on a caught error.

html
<script>
form.addEventListener('submit', async function (e) {
  e.preventDefault();
  try {
    await saveTheLead(/* ... */);          // 1. persist FIRST — the real success
    if (window.fbq) fbq('track', 'Lead', { // 2. only then, count it (guard for blockers)
      content_name: 'waitlist',            // segmentable, NON-PII params only
      value_bucket: 'high'
    });
    window.location.href = '/thank-you';
  } catch (err) {
    showError('Something went wrong, please try again.');  // no event, no fake success
  }
});
</script>
PII rule — do not send personal data through the browser Pixel

Never pass email, phone, name, or address as event parameters. Send categories/buckets (content_name, a value band, a persona) — enough to segment, not to identify. (The one place Meta does use hashed PII is CAPI's Advanced Matching, which is a deliberate, consented, server-side choice — see references/conversions-api.md, not something to sprinkle into browser events.)

5. Verify BEFORE you spend — the gate

Do a real conversion on the live/preview site, then confirm:

  • Install the Meta Pixel Helper Chrome extension. Load the page → it shows the pixel + PageView. Submit the form → it shows the Lead event with your params.
  • Or Events Manager → your dataset → Test events, enter the site URL, and watch events arrive live.
  • Only fires on success: cause a failure and confirm the event does NOT fire.

Only after you can see the conversion fire correctly should ad budget go live. A miswired conversion makes Meta optimize toward the wrong people and you can't tell from the dashboard. Full checklist: references/verify-checklist.md.

"Can you set this up for me?"

The account/Page/Business-Suite/Pixel creation needs the user's own Meta login — can't be done on their behalf; that's a short UI walk (this skill guides it). Getting the Dataset ID is the user's one job. The assistant can write the base code + event into the site once it has the ID. Split it that way — and steer them away from the CAPI wizard and sensitive categories per the two decisions above.

Reference files

  • references/install-by-platform.md — base-code install for Next.js, HTML, WordPress, Shopify, GTM.
  • references/standard-events.md — Meta standard event names + params for common conversions.
  • references/conversions-api.md — what CAPI is, when it's worth it, and the PII/consent guardrails BEFORE wiring it.
  • references/verify-checklist.md — the pre-spend verification gate (Pixel Helper, Test Events, common failures).

© ooiyeefei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (references) in skills/meta-pixel-setup of ooiyeefei/ccc.

  • SKILL.md
  • README.md
  • references/conversions-api.md
  • references/install-by-platform.md
  • references/standard-events.md
  • references/verify-checklist.md

Open the folder on GitHubat commit c0fd926

Compare with similar skills

Meta Pixel Setup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Meta Pixel Setup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Meta Pixel Setup this skillooiyeefei/ccc494—~2.4kAutomated safety check: PassMIT
Meta Ads AuditAgriciDaniel/claude-ads9.8k—~906Automated safety check: PassMIT
Meta Ads for B2Bivangfalco/ads-skills278—~2.4kAutomated safety check: PassCustom licence
AdsCesarjoquin/Marketing-Skills2001 repos~3.5kAutomated safety check: PassMIT
Adscoreyhaines31/marketingskills54k1 repos~7.8kAutomated safety check: PassMIT
Meta Ad Builderkrusemediallc/arcads-claude-code1.6k—~1.7kAutomated safety check: NotesMIT

Similar skills

  • Meta Ads Audit

    AgriciDaniel/claude-ads

    Audits a Meta Ads account across Pixel and Conversions API, attribution, creative, audiences, placements, budgets and policy, and reports evidence-backed findings.

    9.8k GitHub stars~906 tokensUpdated today
    Marketing & SEOAuto-check passed

  • Meta Ads for B2B

    ivangfalco/ads-skills

    Guides B2B campaigns on Meta (Facebook and Instagram): audience data, campaign structure, creative testing, lead forms and account audits for SaaS lead generation.

    278 GitHub stars~2.4k tokensUpdated 2 mo ago
    Marketing & SEOAuto-check passed

  • Ads

    Cesarjoquin/Marketing-Skills

    When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms.

    200 GitHub starsUsed in 1 repo~3.5k tokens
    Marketing & SEOAuto-check passed

  • Ads

    coreyhaines31/marketingskills

    When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms.

    54k GitHub starsUsed in 1 repo~7.8k tokens
    Marketing & SEOAuto-check passed

  • Meta Ad Builder

    krusemediallc/arcads-claude-code

    Publish finished creatives as live Meta (Facebook/Instagram) ads via the Meta Marketing API, plus research and ad-copy support.

    1.6k GitHub stars~1.7k tokensUpdated 15 days ago
    Marketing & SEOAuto-check: notes

  • Mena Ads

    growthack88/growth-marketing-os

    MENA Ads Command Center — a complete paid-ads operating system for the Arab world (Egypt, KSA, UAE, GCC, Levant, North Africa) and global accounts.

    115 GitHub stars~2.5k tokensUpdated 5 days ago
    Marketing & SEOAuto-check passed

More from ooiyeefei/ccc

All 22 skills in this repo

  • Scribe Meeting Notes

    ooiyeefei/ccc

    Turns meeting recordings into notes with a chain of custody from audio to claim, auditing transcripts for gaps and low-confidence numbers and names.

    494 GitHub stars~876 tokensUpdated 2 mo ago
    Auto-check passed

  • Motion Video in Remotion

    ooiyeefei/ccc

    Builds marketing and explainer videos in Remotion from rendered scenes, with one real product capture as proof, and cuts them for each platform's formats.

    494 GitHub stars~2.9k tokensUpdated 2 mo ago
    Auto-check passed

  • Product Demo Video Recorder

    ooiyeefei/ccc

    Records a sharp product demo video by driving the real app with a browser agent, from storyboard to Xvfb capture and a narration script synced to the frames.

    494 GitHub stars~2.8k tokensUpdated 2 mo ago
    Auto-check passed

  • Excalidraw Architecture Diagrams

    ooiyeefei/ccc

    Generates architecture diagrams as .excalidraw files by analyzing a codebase, with optional PNG or SVG export through Playwright.

    494 GitHub stars~2k tokensUpdated 2 mo ago
    Auto-check passed

  • Google Analytics 4 Setup

    ooiyeefei/ccc

    Sets up GA4 on a website and wires one real conversion event end to end, verified in DebugView before any money goes into ads.

    494 GitHub stars~2.2k tokensUpdated 2 mo ago
    Auto-check passed

  • Landing Page GTM Copy

    ooiyeefei/ccc

    Builds or rewrites SaaS landing pages by researching the real product, positioning it against alternatives and writing buyer-focused copy, then implementing it in the codebase.

    494 GitHub stars~1.8k tokensUpdated 2 mo ago
    Auto-check passed

Works with

Categories

Questions about Meta Pixel Setup

What does Meta Pixel Setup do?

Walks a site owner through installing the Meta Pixel, firing one conversion event and verifying it with the Pixel Helper before any ads run. The skill takes a website from no tracking to a verified conversion event for Facebook and Instagram ads. It begins by asking where the person already is: whether a Facebook Page and Business Suite or business portfolio exist, whether there is a Pixel (now labelled a Dataset in the interface) and its ID, which single conversion matters, and what the site is built with.

When should I use Meta Pixel Setup?

Meta Pixel Setup fits situations like: adding the Meta or Facebook Pixel to a website for the first time; setting up a Lead, CompleteRegistration or Purchase event for Meta ads; finding the Pixel or Dataset ID inside Events Manager; debugging a Pixel whose events never fire.

How do I install Meta Pixel Setup in Claude Code?

Run `npx skills add ooiyeefei/ccc --skill meta-pixel-setup -a claude-code`. Or copy the skill folder (skills/meta-pixel-setup in ooiyeefei/ccc) into .claude/skills/meta-pixel-setup in your project. Claude Code loads it when a task matches its description.

How do I install Meta Pixel Setup in Codex?

Run `npx skills add ooiyeefei/ccc --skill meta-pixel-setup -a codex`. Or copy the skill folder (skills/meta-pixel-setup in ooiyeefei/ccc) into .agents/skills/meta-pixel-setup in your project. Codex loads it when a task matches its description.

Can I use Meta Pixel Setup in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ooiyeefei/ccc --skill meta-pixel-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/meta-pixel-setup, .gemini/skills/meta-pixel-setup, .github/skills/meta-pixel-setup and .opencode/skills/meta-pixel-setup in your project.

What does Meta Pixel Setup need to run?

SKILL.md names no scripts, command-line tools or credentials: Meta Pixel Setup is instructions for the agent only. Our summary lists: A Facebook Page and Meta Business Suite access; Access to the website's code or tag settings; The Meta Pixel Helper for verification.

Does Meta Pixel Setup access the network?

SKILL.md names 3 domains. In commands or code: connect.facebook.net and facebook.com; the agent is likely to contact these when it follows the instructions. As links in the text: business.facebook.com. This is read from the text; nothing was executed.

Is Meta Pixel Setup safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Meta Pixel Setup use?

Meta Pixel Setup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Meta Pixel Setup use?

About 2.4k tokens (SKILL.md is roughly 9.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.8k tokens, read only when the agent opens those files.

What are the alternatives to Meta Pixel Setup?

Skills that share tags, products or a category with Meta Pixel Setup: Meta Ads Audit (AgriciDaniel/claude-ads, 9.8k stars), Meta Ads for B2B (ivangfalco/ads-skills, 278 stars), Ads (Cesarjoquin/Marketing-Skills, 200 stars) and Ads (coreyhaines31/marketingskills, 54k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Meta Pixel Setup?

ooiyeefei (a GitHub user) maintains it in ooiyeefei/ccc, which has 494 GitHub stars. The repository holds 22 skills in this directory. The repository was last updated on July 29, 2026.

Source: ooiyeefei/ccc on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.