Meta Pixel (Facebook) integration

In depth

Meta Pixel (also known as the Facebook Pixel) — JavaScript snippet added to a website to optimise Facebook/Instagram ad campaigns. It tracks user actions (page view, add to cart, purchase, lead) and feeds them back to Meta's ads platform — then the ad bidding ML optimises against real business outcomes (purchases) rather than clicks alone.

Functional pillars: (1) Conversion Tracking — auto-detect standard events (PageView, ViewContent, AddToCart, InitiateCheckout, Purchase, Lead, CompleteRegistration); custom events via separate JavaScript calls; (2) Custom Audiences — "users who viewed product X but didn't buy in 7 days" → retargeting ad; (3) Lookalike Audiences — Meta's ML finds users similar to your converters; (4) Dynamic Ads — automatic product carousels for e-commerce sites; (5) Aggregated Event Measurement (AEM) — iOS 14+ post-ATT framework, 8 prioritised events/domain.

iOS 14+ + ATT (App Tracking Transparency) impact: from April 2021 Apple required an app tracking permission prompt — 70%+ users opt out. Meta ad attribution accuracy dropped by 30-40%. Mitigation: (1) Conversions API (CAPI) — server-side event sending, not blocked by browser ITP/iOS; (2) Aggregated Event Measurement (AEM) — pixel works but only 8 events/domain are prioritised; (3) First-party data combining (email, phone hash). Craftwebstudio's 2026 recommendation — Pixel + CAPI dual setup recovers 60-80% of iOS attribution.

GDPR + ePrivacy compliance: EU users require cookie consent before the Pixel can fire. Implementation: Cookiebot, OneTrust or Cookie Consent Solution + Pixel code loaded after consent. Google Consent Mode v2 + Meta Consent Mode together — for proper compliance. For Georgian businesses (no GDPR jurisdiction) — a soft consent banner is sufficient. Pixel itself is free — you pay only via ad budget.