MadalaVijay
UserClaude Code skills for diagnosing Meta Conversions API measurement after the integration is built. Deduplication, match quality, event taxonomy, and reconciling against the money.
Categories
Indexed Skills (6)
dedup-verification
Decide whether browser and server events are actually deduplicating, or whether the account is double counting. Use when platform-reported conversions look high, after any Conversions API deploy, or before trusting a conversion count that both the pixel and the server can claim.
event-taxonomy
Design the conversion event set so campaigns optimise toward the outcome you actually sell. Use when one event covers two commercial steps, when cheap conversions are crowding out expensive ones, or before adding a custom conversion.
match-quality
Diagnose a low event match quality score on server-side conversion events, decide which customer parameters are worth adding, and judge when the score is not worth chasing. Use when match quality is flagged, after adding CAPI, or before spending engineering time on identity parameters.
platform-vs-ledger
Reconcile platform-reported conversions against the payment processor, CRM or operational record, and decide which number to act on. Use before any budget reallocation, when reported conversions and money received disagree, or when validating a new CAPI deploy.
tracking-change-control
Sequence a change to live conversion tracking so the cost of relearning is contained and the result is attributable. Use before migrating an optimisation event, deploying CAPI on a spending account, or bundling pixel fixes into a release.
value-integrity
Diagnose why conversion counts reconcile but reported revenue does not, and decide whether a return-on-spend figure is safe to quote. Use before publishing any ROAS, when revenue and the ledger diverge, or when a value parameter is suspected.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.