Ce primesti
Init fbq pixel_id corect pe Next.js (Script afterInteractive sau layout server-component), WordPress sau alt stack, fara duplicate fires. Events standard: PageView, ViewContent, AddToCart, AddToWishlist, InitiateCheckout, Purchase, Lead, CompleteRegistration, cu params structurate exact cum cere Meta pentru Catalogue Sales si DPA.
Webhook POST graph.facebook.com/v18.0/{pixel-id}/events cu access_token system user (permanent, nu expira), data array structurat, action_source website, event_source_url, user_data hashed SHA256. Retry logic pentru 5xx, queue Redis pentru batch in volume mari, log audit pentru fiecare event trimis.
UUID v4 generat o data per event in browser sau server, pasat IDENTIC in fbq cu eventID si in CAPI cu event_id. Meta combina events din ambele surse fara dublare. Validare in Events Manager test events si raport Deduplication Rate target peste 95% in primele 7 zile.
Trimitem in pixel si CAPI user_data hashed corect: em (email lowercase trimmed), ph (phone E.164 fara +), fn / ln (first / last name lowercase), fbp si fbc cookies, client_ip_address si client_user_agent. Match rate target 70-85% pe email + phone — direct vizibil in Events Manager Match Quality.
Setup AEM Event Configuration in Ads Manager cu top 8 events prioritizate per domain (Purchase prioritate 1, InitiateCheckout 2, AddToCart 3, etc). Configurare custom conversions cu rules pe URL sau value. Plus Domain Verification obligatorie via TXT record DNS in Business Manager.
Pixel si CAPI se incarca DUPA opt-in cookie banner (Cookiebot, Iubenda, CookieYes sau custom). Implementare consent state pe events: signal granular ad_storage, ad_user_data, ad_personalization. Log timestamp si IP pentru audit GDPR. Modus operandi conform CNIL si DPA.
Testing complet inainte de go-live: Meta Pixel Helper extension validation, Events Manager test events mode cu URL params, validare deduplicare in primele 24h, validare match rate dupa 7 zile, raport scris cu screenshots si recommendation list. Setup alerting daca match rate scade sub 50%.
Pentru setup avansat: container GTM server-side pe Cloud Run, App Engine sau VPS propriu (10-25€/luna). Beneficiu: first-party cookies cu domain-ul tau (bypass Safari ITP), control complet asupra datelor inainte de trimitere catre Meta, posibilitate de a alimenta si GA4, TikTok Pixel, LinkedIn Insight Tag din acelasi pipeline.
Process
Zilele 1-2
Sesiune 30-45 min: ce events vrei sa tracuiesti, stack tehnic (Next.js, WooCommerce, Shopify, headless), buget Meta Ads lunar, consent rate actual cookie banner. Audit Business Manager existent sau setup nou cu Ad Account, Pixel, Catalog, Domain Verification. Brief scris cu plan tehnic si quote ferm.
Zilele 3-4
Setup Domain Verification in Business Manager prin TXT record DNS pe domeniul tau (verificat in 24-48h). Configurare AEM Event Configuration cu top 8 events prioritizate. Setup access_token system user permanent in Business Settings. Plus instalare Meta Pixel Helper pentru debug pe browser-ul tau.
Zilele 5-7
Cod pixel init fbq pixel_id in stack-ul tau (layout.tsx pe Next.js, plugin pe WooCommerce, app pe Shopify). Implementare events e-commerce cu content_ids, content_type, value, currency in formatul cerut de Meta. dataLayer GTM client-side daca folosesti GTM. Generare event_id UUID per event si stocare in window.dataLayer pentru CAPI.
Zilele 8-9
Webhook POST graph.facebook.com cu access_token, data array, user_data hashed SHA256. Integrare cu hooks WooCommerce (woocommerce_thankyou) sau webhook Shopify (orders/create) sau Server Actions Next.js. Retry logic pentru 5xx, queue daca volume mare. Advanced Matching cu em, ph, fn, ln, fbp, fbc, ip, user_agent.
Zilele 10-12
Testing in Events Manager test events mode, validare Pixel Helper, validare deduplication ratio dupa 24h, validare match rate dupa 7 zile. Setup alerting Sentry pe webhook CAPI pentru erori 4xx/5xx. Training echipa ta (1h video Loom + sesiune Q&A 30 min), monitoring 7 zile post-livrare, raport scris final.
Stack suportat
Plugin oficial Facebook for WooCommerce cu CAPI built-in plus PixelYourSite Pro pentru events custom. Sync produse spre Catalog Manager si webhook order pentru Purchase event server-side.
App oficiala Meta din Shopify App Store cu CAPI activat automat din 2022. Customizare via Shopify Pixels API pentru events non-standard si Order Cancelled / Refund tracking.
Cod pixel in app/layout.tsx cu Script next/script strategy afterInteractive. CAPI in Server Actions sau route handlers cu fetch direct la Graph API si event_id UUID server-generated.
Modul oficial Meta pentru PrestaShop 1.7+ cu CAPI inclus. Setup direct din Back Office cu Pixel ID si access_token. Recomandam testing in Events Manager test events inainte de live.
Extensie oficiala Meta Business Extension cu CAPI server-side. Integrare cu Catalog Manager pentru DPA (Dynamic Product Ads) si webhook order pentru Purchase events deduplicate.
Script tag pixel in head cu data-pixel-id env var. CAPI in functii serverless (Cloudflare Workers, Netlify Functions, Vercel) cu fetch la Graph API si user_data hashed SHA256.
Pixel client in frontend Next.js sau Astro. CAPI server in WordPress backend cu plugin custom care apeleaza Graph API pe hooks WooCommerce sau Gravity Forms submission.
SDK oficial facebook/php-business-sdk in service layer cu queue Redis sau Horizon pentru batch events. Logging complet in Sentry pentru audit si re-trimitere events failed.
Preturi implementare
300€
livrare 2-4 zile
700-1000€
livrare 5-8 zile
1200-1500€
livrare 9-12 zile
Intrebari frecvente
Implementare one-off: 300-1500€ in functie de stack si scop. Pixel simplu pe Next.js sau WordPress cu 3-5 events standard (PageView, ViewContent, AddToCart, InitiateCheckout, Purchase): 300-500€. Pixel + Conversions API server-side cu deduplicare event_id, Advanced Matching hash (email, phone, fbp, fbc) si webhook order pe WooCommerce sau Shopify: 600-1000€. Setup complet enterprise cu CAPI Gateway pe server propriu, Aggregated Event Measurement (AEM) configurat pentru iOS, dataLayer GTM server-side container, 8-10 events custom, validare Events Manager si dashboard atribuire: 1200-1500€. Mentenanta lunara optionala 50-150€/luna. Meta Pixel + CAPI sunt gratuite la Meta — platesti doar Ads-urile, deci nu adaugi cost lunar Meta dupa setup. Singura cheltuiala marginala daca alegi server CAPI pe VPS propriu: 6-15€/luna VPS Hetzner.
Nu mai e, post iOS 14.5 (aprilie 2021) si extinderea ATT pe Android 14. Meta Pixel client-side ruleaza in browser, deci e blocat de: 1) Safari ITP (Intelligent Tracking Prevention) care expira cookies first-party in 7 zile. 2) iOS 14.5+ ATT prompt care reduce signal-ul cu 60-80% pentru useri opt-out. 3) Ad-blockers (uBlock, AdBlock Plus) blocheaza fbevents.js complet pentru 15-25% trafic. 4) Cookie banners cu reject all care nu permit pixel sa se incarce. CAPI (Conversions API) trimite events direct de pe serverul tau spre Meta prin endpoint graph.facebook.com/v18.0/{pixel-id}/events cu access_token, fara dependenta de browser. Cu deduplicare event_id, Meta combina automatic events din ambele surse. Rezultat masurat: +15-30% conversii atribuite si CPA mai mic cu 10-20% in Ads Manager.
Pixel simplu Next.js sau WordPress cu events standard si dataLayer GTM client-side: 2-4 zile lucratoare. Pixel + CAPI server-side cu deduplicare event_id, Advanced Matching hash SHA256 si webhook POST graph.facebook.com pe WooCommerce sau Shopify: 5-8 zile. Setup complet enterprise cu GTM Server-side container pe Cloud Run sau VPS propriu, CAPI Gateway, AEM prioritizare events pentru iOS, 8-10 events custom (Lead, CompleteRegistration, Subscribe, AddPaymentInfo etc), validare end-to-end in Events Manager test events si Pixel Helper: 9-12 zile. Plus 24-72h pentru Domain Verification in Business Manager (TXT record DNS) si AEM Event Configuration in Ads Manager. Validare deduplicare se vede in Events Manager dupa 24h cu raport match rate target peste 70% pe email + phone.
Poti pana la PageView, dar diferenta serioasa e in 6 zone tehnice. 1) Init pixel corect cu fbq init pixel_id si fbq track event_name params, fara duplicate fires (problema comuna pe Next.js cu Strict Mode si re-render). 2) Events e-commerce structurate corect cu content_ids, content_type product, value, currency in formatul exact cerut de Meta (greseala = events nu sunt utilizabile in Catalogue Sales). 3) Deduplicare client + server cu acelasi event_id UUID pe fiecare event, generat o data si pasat in fbq cu eventID si in CAPI cu event_id — fara asta dublezi conversiile. 4) Advanced Matching cu hash SHA256 pe email, phone, first_name, last_name, fbp, fbc, client_ip_address, client_user_agent — creste match rate cu 30-50%. 5) Server-side CAPI POST graph.facebook.com/v18.0/{pixel-id}/events cu access_token, data array, action_source website si user_data hashed. 6) Consent mode GDPR — pixel si CAPI se incarca DUPA opt-in, nu inainte, altfel risti amenda DPA si CNIL.
Toate. Next.js si React: cod custom in app/layout.tsx pentru pixel init + Server Actions sau route handlers pentru CAPI cu fetch direct la Graph API sau biblioteca facebook-nodejs-business-sdk. Recomandat cu Vercel Analytics + GTM client + GTM server-side container pe Cloud Run. WooCommerce: plugin oficial PixelYourSite Pro sau Facebook for WooCommerce cu CAPI built-in, plus customizare PHP hooks pentru events non-standard. Shopify: app oficiala Meta Pixel cu CAPI activat automat din 2022, plus customizare via Shopify Pixels API pentru events custom. PrestaShop si Magento 2: module oficiale Meta cu CAPI. WordPress headless cu Next.js sau Astro frontend: cod direct in frontend pentru pixel + webhook backend pentru CAPI. PHP custom (Laravel, Symfony): SDK facebook/php-business-sdk in service layer cu queue Redis pentru events batch. Spune-ne stack-ul si dam recomandare clara.
Top 7 probleme: 1) Events duplicate in Events Manager pentru ca event_id lipseste sau e diferit intre Pixel si CAPI — fix: UUID generat o data per event, pasat in ambele surse identic. 2) Match rate sub 50% in Events Manager — cauza: Advanced Matching nu trimite user_data hashed corect; fix: SHA256 lowercase pe email si phone normalizat E.164. 3) PageView trage de 2-3 ori pe Next.js cu re-render — fix: ref si useEffect cu deps corect sau script tag in layout. 4) iOS conversions lipsa — AEM Event Configuration nu e setat in Ads Manager; fix: prioritizam top 8 events per domain. 5) Domain Verification ratata — TXT record DNS lipseste, deci Aggregated Event Measurement nu functioneaza; fix: setup obligatoriu inainte de Ads launch. 6) Erori 4xx la CAPI Graph API — access_token gresit sau expirat (system user token e permanent), data array malformat sau lipsa hash; fix: validator official Meta Payload Helper. 7) GDPR — pixel se incarca inainte de consent, risc amenda; fix: consent mode v2 cu wait pana la opt-in.
Da, 90 zile suport bug-uri inclus la orice integrare — daca events nu mai ajung in Events Manager, match rate scade brusc sau Meta deprecata o versiune Graph API (se intampla anual cu 6-12 luni preaviz), reparam gratuit. Pentru schimbari de logica (events noi, integrare cu un sistem nou, migrare de la GTM client-side la GTM server-side, switch de la pixel single la multi-pixel pentru white label): 50-100€/h interventie sau pachet mentenanta lunara 80-150€/luna cu monitoring deliverability prin Events Manager (raport saptamanal match rate, deduplicare ratio, event quality score), plus 2-4h interventii incluse. Optional setam Sentry pe webhook CAPI ca sa primesti alerta daca rata de erori 4xx/5xx urca peste 1%. Documentatie completa la livrare cu cod comentat si fluxuri Mermaid — orice dev cu experienta Meta Marketing API poate prelua, nu te legam doar de noi.
Nu e potrivita daca: 1) Nu rulezi reclame Meta Ads (Facebook, Instagram, Messenger, WhatsApp) — fara Ads, pixel-ul colecteaza date inutile si risti GDPR; alternativa: doar GA4 server-side. 2) Esti exclusiv B2B cu LinkedIn Ads ca canal principal — LinkedIn Insight Tag + LinkedIn Conversions API sunt prioritate, Meta secundar. 3) Faci doar Google Ads cu Performance Max — Google Ads Enhanced Conversions + GA4 conexat e suficient, Meta opt-in. 4) Site-ul are sub 100 vizite/luna sau sub 10 conversii/luna — Meta nu are date statistice suficiente pentru optimizare; nu merita efortul tehnic. 5) Industrie complet interzisa de Meta (pariuri fara licenta, anumite suplimente, crypto cu promisiuni profit) — contul se inchide oricum. 6) Ai consent rate sub 30% in cookie banner — pixel + CAPI vor avea volume mici si atributing fragil; mai bine investesti in alt canal. Pentru e-commerce, lead-gen B2C si DTC cu Meta Ads buget peste 500€/luna, integrarea e obligatorie in 2026.
Integrari conexe
GA4 server-side cu Measurement Protocol, custom events si raportare cross-platform. Complementar cu Meta Pixel pentru analiza end-to-end conversie.
Sync lead-uri Meta Lead Ads direct in HubSpot, atribuire cross-channel si nurture automation. Inchide bucla intre ads si vanzari.
Trafic organic complementar cu Ads platite. Diversifica sursele si scade dependenta de o singura platforma.