skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
kelpi-ai/meta-ads-skills77 installs

pixel-conversions

Verify the tracking is telling the truth: which events fire, which double-fire or died, and whether Meta's numbers can be reconciled with your store's. Use before launch, after any site change, and whenever dashboards disagree.

How do I install this agent skill?

npx skills add https://github.com/kelpi-ai/meta-ads-skills --skill pixel-conversions
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    No security issues were detected. The skill is a diagnostic tool for Meta Ads pixel verification and operates in a read-only capacity.

  • Socketwarn

    1 alert: gptAnomaly

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

Pixel & Conversions

Doctrine

If the pixel is broken, every other number is a lie, and the algorithm optimizes toward the lie. The most common ownerside symptom is "Meta says my ads are fine, Shopify says sales are down": that is either attribution's normal flattery or a real tracking break, and knowing which is worth more than any optimization. Measurement integrity precedes optimization, always.

When to use

  • Before the first campaign, after every site or checkout change, and monthly regardless.
  • Whenever Meta's dashboard and your store/CRM disagree hard.
  • Needs a Meta Ads MCP, read access.

Run it

Tracking truth check, READ-ONLY:

1. List the pixels on my account and which one my active campaigns optimize toward.
2. For the last 7 days: which conversion events fired, at what volume? Flag anything that looks broken: purchase events at zero while traffic flows, events double-firing, or a custom event that silently replaced a standard one.
3. Compare Meta's reported conversions for the period against my store's number: [MY STORE'S COUNT]. State the gap as a percentage and explain the plausible causes in plain language (attribution windows, view-through, genuine breakage), ranked by likelihood.
4. Tell me the ONE fix worth doing first if anything is broken, and what it would confirm.
5. Change nothing.

Guardrails

  • Read-only; fixes happen on the site or in Events Manager by a human.
  • Never explain a gap away: "a 15% gap is normal attribution behavior" and "your purchase event died Tuesday" are different findings; say which one the data shows.
  • If store numbers are unavailable, say the reconciliation is incomplete rather than trusting Meta's side alone.

Good output looks like

A verdict in one line ("your tracking is telling the truth" or "purchase events died on [date]"), the evidence, and one prioritized fix.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/kelpi-ai/meta-ads-skills/pixel-conversions">View pixel-conversions on skillZs</a>