meta-conversions
Use when setting up Meta Conversions API (CAPI), implementing server-side event tracking, debugging event deduplication, monitoring EMQ scores, or creating custom conversion events. Also use when the Meta Pixel alone is insufficient due to browser restrictions or privacy settings.
| Model | Source |
|---|---|
| sonnet | pack: ads |
Full Reference
┏━ 🔧 meta-conversions ━━━━━━━━━━━━━━━━━━━━━━━━━━┓ ┃ Use when setting up Meta Conversions API (CAPI… ┃ ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛
Meta Conversions
Section titled “Meta Conversions”Meta Conversions API (CAPI) sends events server-to-server, bypassing ad blockers and browser cookie restrictions. Run CAPI alongside the browser Pixel — they are complementary, not alternatives.
Quick Reference
Section titled “Quick Reference”| Item | Value |
|---|---|
| Endpoint | POST https://graph.facebook.com/v21.0/{PIXEL_ID}/events |
| Deduplication window | 48 hours by event_name + event_id |
| EMQ target | 7+ (6 minimum acceptable) |
| event_time format | Unix seconds (not milliseconds) |
Reference Index
Section titled “Reference Index”| I want to… | File |
|---|---|
| Send CAPI events, set up custom conversions, test events | reference/sending-capi-events.md |
| Fix deduplication, improve EMQ, hash PII correctly, monitor pixel | reference/deduplication-and-emq.md |
Usage: Read the reference file matching your current task from the index above. Each file is self-contained with code examples and inline gotchas.