Meta Pixel + Conversions API
The full Meta stack: browser pixel and server-side CAPI running together, deduplicated, with the match quality to back it.
- Pixel installed and verified through GTM, on every template including checkout
- Conversions API server-side, covering the same events as the browser
- Shared event_id deduplication so nothing is ever counted twice
- Standard events: ViewContent, AddToCart, InitiateCheckout, Lead, Schedule, Purchase, Subscribe
- Customer parameters hashed correctly: email, phone, first and last name, city, country
- fbp, fbc and fbclid captured and persisted across sessions and devices
- Event Match Quality raised and monitored, typically to 9+/10
- Dynamic value, currency, content_ids and contents on every commerce event
- Domain verification and Aggregated Event Measurement priorities
- Offline and CRM conversions pushed back to Meta with original attribution
- Legacy and duplicate pixels from previous agencies removed
- Consent-aware firing so nothing runs before the visitor agrees