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.
Bundles Meta's official Pixel and Conversions API documentation so tracking changes, event deduplication and conversion events are checked against the real spec.
Install Meta Pixel and Conversions API Reference
$ npx skills add bighadj22/codflow --skill meta-ads -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install bighadj22/codflow meta-ads --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/bighadj22/codflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/meta-ads .claude/skills/meta-ads && rm -rf skills-srcUse ~/.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/
Install the "meta-ads" agent skill from https://github.com/bighadj22/codflow/tree/main/.agents/skills/meta-ads into .claude/skills/meta-ads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meta-ads", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/bighadj22/codflow/tree/main/.agents/skills/meta-adsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add bighadj22/codflow --skill meta-ads -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install bighadj22/codflow meta-ads --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bighadj22/codflow.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/meta-ads .agents/skills/meta-ads && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "meta-ads" agent skill from https://github.com/bighadj22/codflow/tree/main/.agents/skills/meta-ads into .agents/skills/meta-ads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meta-ads", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bighadj22/codflow --skill meta-ads -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install bighadj22/codflow meta-ads --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bighadj22/codflow.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/meta-ads .cursor/skills/meta-ads && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "meta-ads" agent skill from https://github.com/bighadj22/codflow/tree/main/.agents/skills/meta-ads into .cursor/skills/meta-ads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meta-ads", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/bighadj22/codflow.git --path .agents/skills/meta-ads--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add bighadj22/codflow --skill meta-ads -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install bighadj22/codflow meta-ads --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bighadj22/codflow.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/meta-ads .gemini/skills/meta-ads && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "meta-ads" agent skill from https://github.com/bighadj22/codflow/tree/main/.agents/skills/meta-ads into .gemini/skills/meta-ads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meta-ads", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install bighadj22/codflow meta-adsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add bighadj22/codflow --skill meta-ads -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/bighadj22/codflow.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/meta-ads .github/skills/meta-ads && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "meta-ads" agent skill from https://github.com/bighadj22/codflow/tree/main/.agents/skills/meta-ads into .github/skills/meta-ads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meta-ads", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bighadj22/codflow --skill meta-ads -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install bighadj22/codflow meta-ads --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bighadj22/codflow.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/meta-ads .opencode/skills/meta-ads && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "meta-ads" agent skill from https://github.com/bighadj22/codflow/tree/main/.agents/skills/meta-ads into .opencode/skills/meta-ads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meta-ads", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
meta-ads- GitHub stars
- 350
- Token cost
- ~1.8k tokens
- SKILL.md length
- 688 words
- Files
- 24 (incl. references)
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Bundles Meta's official Pixel and Conversions API documentation so tracking changes, event deduplication and conversion events are checked against the real spec.
- Works in 6 steps: Ground first. Read the relevant… → Never break the dedup equality (browser… → A new conversion-event mode must fire… → …
- Adding or changing a Meta Pixel event on a storefront
- SKILL.md covers The docs (all unaltered…, How CodFlow maps onto these…, Working rules for tracking… and Refreshing the docs
- Reaches developers.facebook.com
What it does
This skill vendors Meta's official documentation, unaltered from developers.facebook.com, for CodFlow, a cash-on-delivery e-commerce platform whose tracking runs the Meta Pixel in the theme01 front end and the Conversions API in cod-server. The rule it sets is that any tracking change must be verified against these docs before review, and a reply to a tracking pull request should read and cite the relevant reference first.
References are split into browser-side Pixel files (overview, installing the base code, the standard events table, conversion tracking, advanced matching, single-page apps, custom audiences, GDPR and data processing options) and server-side Conversions API files (overview, getting started with tokens, using the API, parameters, server event fields such as event_name, event_id and action_source, deduplication, offline events, payload helper, verifying setup and best practices). The standard events table is named as the source of truth for which event an action maps to.
When your agent uses it
- Adding or changing a Meta Pixel event on a storefront
- Debugging duplicate conversions between Pixel and Conversions API events
- Reviewing a pull request that touches Conversions API server events
- Looking up which standard event fits a user action
Example prompts
- “Check our Purchase event against Meta's standard events table and tell me if the parameters are right.”
- “Conversions look double-counted. Review how event_id deduplication works between the browser and the server.”
- “Review this PR that changes capi.ts and cite the Meta docs for anything you flag.”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Ground first. Read the relevant reference file(s) above before
- Never break the dedup equality (browser eventID === server
- A new conversion-event mode must fire from BOTH sides (browser +
- capi_event_log is the idempotency ledger — anything that can fire
- Test Mode (test_event_code) exists for verification — use
- Docs are read-only reference. These files are unaltered Meta
What it can do on your machine
Read from SKILL.md and the folder at commit ed79aa9. 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 bash).
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:
developers.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 and Conversions API Reference loads about 1.8k tokens when it runs, and up to ~51k if it reads all its reference files. Until then it costs about 120 tokens; SKILL.md has 688 words of instructions outside code blocks.
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 bighadj22/codflow at commit ed79aa9, republished under its Apache-2.0 licence (© bighadj22). 688 words, ~1,754 tokens.
Download SKILL.mdSave it as
.claude/skills/meta-ads/SKILL.md (or your agent's skills folder). This skill also uses 23 other files; get the full folder from GitHub.- name
- meta-ads
- description
- Official Meta (Facebook) Pixel and Conversions API reference docs for CodFlow's tracking stack — standard events, event parameters, deduplication, advanced matching, test events, and best practices. Use whenever working on Meta Pixel integration, CAPI server events, conversion tracking, event deduplication, attribution, or reviewing PRs that touch tracking (cod-server/src/workflows/capi.ts, capi-helpers.ts, capi_event_log, theme01 pixel scripts, store_pixel_config).
Meta Ads — Pixel & Conversions API Official Documentation
CodFlow's tracking stack (Meta Pixel in theme01 + Conversions API in cod-server) must always match Meta's official behavior. This skill vendors the official documentation so every change — ours or a contributor's — can be grounded against the real spec instead of guesses, blog posts, or AI memory.
Rule for agents and contributors: any tracking change must be verified against these docs before review. When replying to a tracking PR, read the relevant reference here first and cite it.
The docs (all unaltered official content, fetched from developers.facebook.com)
Pixel — browser side (fbq())
| File | What it covers |
|---|---|
references/pixel/pixel-overview.md | What the Pixel is, redundant setup with CAPI |
references/pixel/pixel-get-started.md | Installing the base code, the fbq queue |
references/pixel/pixel-reference-standard-events.md | The standard-event table — exact definitions of Purchase, Lead, InitiateCheckout, etc. + object properties. The source of truth for "which event is this action?" |
references/pixel/pixel-conversion-tracking.md | Firing events on actions vs page load, purchase-confirmation-page pattern |
references/pixel/pixel-advanced-matching.md | em, ph etc. customer params on fbq('init') |
references/pixel/pixel-single-page-apps.md | SPA pitfalls (irrelevant to our full-page loads — know why) |
references/pixel/pixel-custom-audiences.md | Audience creation from Pixel data |
references/pixel/pixel-gdpr.md | GDPR/Limited Data Use reasoning |
references/pixel/pixel-data-processing-options.md | _fbp cookie + data processing options |
Conversions API — server side (/events endpoint)
| File | What it covers |
|---|---|
references/conversions-api/capi-overview.md | What CAPI is, redundant setup recommendation |
references/conversions-api/capi-get-started.md | System user tokens, access, first request |
references/conversions-api/capi-using-the-api.md | Endpoint mechanics, payloads, batching, error handling |
references/conversions-api/capi-parameters.md | Parameters index |
references/conversions-api/capi-server-event-parameters.md | event_name, event_time, event_id, event_source_url, action_source — the per-event field contract |
references/conversions-api/capi-customer-information-parameters.md | Hashed ph, em, client_ip_address, client_user_agent, fbp, fbc — what we send and how it's normalized |
references/conversions-api/capi-custom-data-parameters.md | value, currency, contents, content_ids, order_id, num_items |
references/conversions-api/capi-original-event-parameters.md | Original-event dedup fields (aggregated/merged events) |
references/conversions-api/capi-main-body-parameters.md | data[], test_event_code wrapper |
references/conversions-api/capi-deduplication.md | Pixel ↔ CAPI dedup: browser eventID must equal CAPI event_id AND names must match. The rule behind CodFlow's eventID = orderId pattern |
references/conversions-api/capi-best-practices.md | Meta's recommended architecture, timing, and matching quality guidance |
references/conversions-api/capi-verifying-setup.md | Events Manager validation, Test Events |
references/conversions-api/capi-offline-events.md | Offline conversion semantics (delayed events — the category our purchase-on-delivery model lives in) |
references/conversions-api/capi-payload-helper.md | Meta's interactive payload builder (for debugging shapes) |
How CodFlow maps onto these docs (quick orientation)
- Browser: theme01's
BaseHead.astroloads the canonicalfbevents.jssnippet (PageView on load);thank-you.astrofires the conversion event with{ eventID: orderId }— the fourthfbqargument, per the dedup doc. - Server:
cod-server/src/workflows/capi.ts(Cloudflare Workflow) sends the mirrored event via/eventswithevent_id: orderId;capi-helpers.tsgates which status transitions trigger it;capi_event_logrecords what was sent (and powers idempotency). - Config:
store_pixel_config(pixel id, access token, test event code, conversion event choice, test mode) — Settings → Tracking. - Dedup contract: browser
eventID=== CAPIevent_id=== orderId, sameevent_nameon both sides. Any tracking change that breaks this equality double-counts conversions (see capi-deduplication.md). - Standard-event semantics: which CodFlow moment maps to which Meta
event is governed by pixel-reference-standard-events.md — notably
Purchaseis defined as at-checkout ("lands on thank you or confirmation page") andLeadas a completed sign-up. COD purchase-on-delivery is an offline-style delayed Purchase (see capi-offline-events.md) — legitimate, but it must be a deliberate merchant choice, not a silent default.
Show full SKILL.md (213 more words)Show less
Working rules for tracking changes
- Ground first. Read the relevant reference file(s) above before writing or reviewing a single line of tracking code. Cite the doc in the PR/review when a decision hinges on Meta behavior.
- Never break the dedup equality (browser eventID === server event_id, matching names) — silent double-counting or double-sending is the #1 tracking bug class.
- A new conversion-event mode must fire from BOTH sides (browser + CAPI mirror) or from exactly ONE side deliberately, never accidentally. PR #103's lesson: a mode that exists only in the settings enum is not a feature.
capi_event_logis the idempotency ledger — anything that can fire twice (webhook retries, status toggles) must be guarded through it.- Test Mode (
test_event_code) exists for verification — use capi-verifying-setup.md's flow before claiming an event works. - Docs are read-only reference. These files are unaltered Meta content (only a source header is prepended). Never edit them to match code — if code and docs disagree, the CODE changes (or Meta did, and we re-fetch).
Refreshing the docs
Meta updates its docs; when a tracking question can't be answered from these files (or the content looks outdated), re-fetch with Firecrawl:
firecrawl scrape "https://developers.facebook.com/documentation/<path>" --only-main-contentKeep the source header (URL + fetch date) on every file so staleness is auditable. Content below the header stays unaltered.
© bighadj22, Apache-2.0. 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 23 other files (references) in .agents/skills/meta-ads of bighadj22/codflow.
- SKILL.md
- references/conversions-api/capi-best-practices.md
- references/conversions-api/capi-custom-data-parameters.md
- references/conversions-api/capi-customer-information-parameters.md
- references/conversions-api/capi-deduplication.md
- references/conversions-api/capi-get-started.md
- references/conversions-api/capi-main-body-parameters.md
- references/conversions-api/capi-offline-events.md
- references/conversions-api/capi-original-event-parameters.md
- references/conversions-api/capi-overview.md
- references/conversions-api/capi-parameters.md
- references/conversions-api/capi-payload-helper.md
- references/conversions-api/capi-server-event-parameters.md
- references/conversions-api/capi-using-the-api.md
- references/conversions-api/capi-verifying-setup.md
- references/pixel/pixel-advanced-matching.md
- references/pixel/pixel-conversion-tracking.md
- references/pixel/pixel-custom-audiences.md
- … and 6 more
Open the folder on GitHubat commit ed79aa9
Compare with similar skills
Meta Pixel and Conversions API Reference 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Meta Pixel and Conversions API Reference this skillbighadj22/codflow | 350 | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Meta Ads AuditAgriciDaniel/claude-ads | 9.8k | — | ~906 | Automated safety check: Pass | MIT | |
| Meta Pixel Setupooiyeefei/ccc | 494 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Blog GoogleAgriciDaniel/claude-blog | 2.3k | 1 repos | ~3.3k | Automated safety check: Notes | MIT | |
| Apple Ads with the asc CLIrorkai/app-store-connect-cli-skills | 1.1k | 1 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Paid Ads AuditAgriciDaniel/claude-ads | 9.8k | — | ~1.5k | Automated safety check: Pass | MIT |
Similar skills
Meta Pixel Setup
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.
Blog Google
AgriciDaniel/claude-blog
Google API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity…
Apple Ads with the asc CLI
rorkai/app-store-connect-cli-skills
Runs Apple Ads work through the asc CLI, covering auth profiles, ad-account discovery, campaigns, reports and guarded changes, plus the move from API v5 to Platform v1.
Paid Ads Audit
AgriciDaniel/claude-ads
Runs a source-grounded paid advertising audit across up to 12 ad platforms, with parallel platform workers, deterministic scoring and a versioned JSON bundle.
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.
More from bighadj22/codflow
All 11 skills in this repoYalidine Delivery Integration
bighadj22/codflow
Wires an app to the Yalidine (Guepex) Algerian courier API: parcels, zone lookups, delivery fees and verified delivery-status webhooks.
CodFlow Change Workflow
bighadj22/codflow
A step-by-step workflow for changing the CodFlow repository: read the AGENTS.md contract, respect package boundaries, verify before claiming done and keep PRs small.
COD CRM Customer Management
bighadj22/codflow
Guides an agent through eight customer tools in a cash-on-delivery CRM for Algerian e-commerce: search, profiles, phone lookup, order history, groups, tags and deletion.
EcoTrack Courier Integration
bighadj22/codflow
Guides connecting and maintaining the EcoTrack courier adapter in CodFlow, one API shared by 82 Algerian couriers, using the official API reference and a rollout plan.
defineRoute Route Builder
bighadj22/codflow
Creates new API endpoints, and converts older ones, with the defineRoute() pattern used in cod-server, including auth strategies, scopes and OpenAPI output.
CodFlow Storefront Vercel Deploy
bighadj22/codflow
Runbook for deploying or redeploying the CodFlow Astro storefront to Vercel, with required environment variables, CLI or Git methods and checks afterwards.
Related
Works with
Categories
Questions about Meta Pixel and Conversions API Reference
What does Meta Pixel and Conversions API Reference do?
Bundles Meta's official Pixel and Conversions API documentation so tracking changes, event deduplication and conversion events are checked against the real spec. com, for CodFlow, a cash-on-delivery e-commerce platform whose tracking runs the Meta Pixel in the theme01 front end and the Conversions API in cod-server. The rule it sets is that any tracking change must be verified against these docs before review, and a reply to a tracking pull request should read and cite the relevant reference first.
When should I use Meta Pixel and Conversions API Reference?
Meta Pixel and Conversions API Reference fits situations like: adding or changing a Meta Pixel event on a storefront; debugging duplicate conversions between Pixel and Conversions API events; reviewing a pull request that touches Conversions API server events; looking up which standard event fits a user action.
How do I install Meta Pixel and Conversions API Reference in Claude Code?
Run `npx skills add bighadj22/codflow --skill meta-ads -a claude-code`. Or copy the skill folder (.agents/skills/meta-ads in bighadj22/codflow) into .claude/skills/meta-ads in your project. Claude Code loads it when a task matches its description.
How do I install Meta Pixel and Conversions API Reference in Codex?
Run `npx skills add bighadj22/codflow --skill meta-ads -a codex`. Or copy the skill folder (.agents/skills/meta-ads in bighadj22/codflow) into .agents/skills/meta-ads in your project. Codex loads it when a task matches its description.
Can I use Meta Pixel and Conversions API Reference 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 bighadj22/codflow --skill meta-ads -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-ads, .gemini/skills/meta-ads, .github/skills/meta-ads and .opencode/skills/meta-ads in your project.
What does Meta Pixel and Conversions API Reference need to run?
SKILL.md names no scripts, command-line tools or credentials: Meta Pixel and Conversions API Reference is instructions for the agent only.
Does Meta Pixel and Conversions API Reference access the network?
SKILL.md names 1 domain. In commands or code: developers.facebook.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Meta Pixel and Conversions API Reference 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 and Conversions API Reference use?
Meta Pixel and Conversions API Reference is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Meta Pixel and Conversions API Reference use?
About 1.8k tokens (SKILL.md is roughly 7k 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 50k tokens, read only when the agent opens those files.
What are the alternatives to Meta Pixel and Conversions API Reference?
Skills that share tags, products or a category with Meta Pixel and Conversions API Reference: Meta Ads Audit (AgriciDaniel/claude-ads, 9.8k stars), Meta Pixel Setup (ooiyeefei/ccc, 494 stars), Blog Google (AgriciDaniel/claude-blog, 2.3k stars) and Apple Ads with the asc CLI (rorkai/app-store-connect-cli-skills, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Meta Pixel and Conversions API Reference?
bighadj22 (a GitHub user) maintains it in bighadj22/codflow, which has 350 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 6, 2026.
Source: bighadj22/codflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.