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.
Install
$ agentstack add skill-kelpi-ai-meta-ads-skills-pixel-conversions ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-kelpi-ai-meta-ads-skills-pixel-conversions) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: kelpi-ai
- Source: kelpi-ai/meta-ads-skills
- License: MIT
- Homepage: https://kelpi.ai/skills
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.