ENATIV Logo
ENATIV
Back
  1. Home
  2. ›
  3. Services
  4. ›
  5. Meta Pixel Setup

Meta Pixel Setup

Meta Pixel Setup

Meta Pixel configured so it never double-counts a conversion or fires without consent. I connect the browser pixel with the server-side Meta Conversions API, sharing one event identifier - exactly how it runs on this site.

Request Meta Pixel setupSee the process
0
measurement layers: browser pixel + server-side CAPI
0
c15t consent category (marketing)
0
server-side Lead event with deduplication

Why Work With Me

I bring more than code to the table. Here is what makes working with me different from typical agencies.

40%
faster delivery

Lightning Fast Delivery

I use modern frameworks and proven workflows to deliver projects 40% faster than traditional agencies without compromising quality.

100%
TypeScript coverage

Battle-Tested Code

Every line of code is written with TypeScript, follows best practices, and includes automated tests for reliability.

< 24h
response time

Always Responsive

Direct communication with me - no account managers, no delays. Get answers within hours, not days.

95%
client retention

Long-term Partnership

I don't disappear after launch. I stay for maintenance, updates, and continuous improvements of your product.

2
measurement layers for the Lead event: pixel + CAPI

Deduplication Built Into the Architecture

The browser pixel and the server-side Conversions API share one event identifier from the first line of code - not a patch bolted on afterward, but an architectural decision made when the integration was designed.

1
consent-gate bug found and fixed

Consent Enforced in Code

I found and closed a real gap: the server-side Lead event was firing regardless of marketing consent, until a post-implementation code review caught it. That story is now part of what I offer - I don't hide mistakes, I fix them and talk about them plainly.

What Meta Pixel Setup Covers

Browser Pixel Installation

I configure Meta Pixel as a script that loads only after consent to "marketing" category, with automatic pushState tracking disabled so the SPA doesn't generate duplicate PageViews.

Server-Side Lead Event Via Conversions API

I send the Lead event server-to-server directly from the contact-form endpoint, independent of browser blockers and the iOS 14.5+ restrictions that degrade the pixel's own match quality.

Deduplication Via A Shared Event ID

The browser pixel and the server-side Conversions API send the same Lead event with one shared identifier - Meta merges both sends into a single conversion instead of counting it twice.

SHA-256 User Data Hashing

The email address is normalized and hashed with SHA-256 before being sent to Meta - per the server-side Advanced Matching requirements, never as plain text.

Consent Gates Every Event Sent

Both the browser pixel and the server-side Conversions API fire only when the visitor has consented to "marketing" category - no exceptions, no silent workaround.

How this site does it

  • The Lead event from the contact form is sent twice - once via the browser pixel, once via the server-side Conversions API - and deduplicated on one shared event identifier, so Meta never counts one conversion twice.
  • The pixel loads only after consent to "marketing" category, and fbevents.js's automatic PageView is deliberately disabled and replaced with a single, manually fired event on every SPA route change - otherwise every navigation would count twice.
  • The visitor's email address is hashed with SHA-256 before being sent to the server-side Conversions API, and the call itself is non-blocking - a failure on Meta's side never delays or interrupts the contact-form message.
How We Work

Transparent Process

No black boxes. You know exactly what is happening at every stage.

01
Step 01

Audit The Current Pixel Setup

1-2 days

I check whether the pixel fires duplicate PageViews, whether Lead events are gated behind consent, and whether user data is ever sent in plain text. Most accounts I audit are missing at least one of these three.

Current pixel and event state reportList of events missing deduplication or a consent gateRecommended pixel + CAPI architecture
02
Step 02

Install The Browser Pixel And Consent Gate

2-3 days

I install the pixel under "marketing" consent category, disable fbevents.js's automatic pushState tracking, and replace it with a single, manually fired PageView event on every client-side route change.

Pixel wired to "marketing" consent categoryAutomatic PageView disabled and replaced with a manual callVerified no duplicate events on SPA navigation
03
Step 03

Server-Side Meta Conversions API With Deduplication

3-5 days

I implement a server-side Lead event that shares its event identifier with the browser pixel, hash user data with SHA-256 before sending, and make the send non-blocking so it never delays the actual contact-form message.

Lead event sent server-to-server via the Conversions APIShared event identifier for deduplication with the browser pixelUser data hashed with SHA-256 before sending
04
Step 04

Verification In Events Manager And Documentation

1 week

I confirm both events deduplicate correctly using Meta Events Manager's Test Events tool, verify the consent gate works in production, and leave behind documentation of the whole pixel + CAPI architecture.

Deduplication verification in Meta Events ManagerConfirmed consent gate in productionPixel + CAPI architecture documentation

Package Comparison

Features
Starter
ProfessionalMost Popular
Browser pixel installation and basic events (PageView, ViewContent)
c15t consent gate (marketing category)
Automatic PageView disabled, manual call on SPA navigation
Server-side Meta Conversions API with event-ID deduplication
SHA-256 hashing of user data before the server-side send
Verification in Meta Events Manager and documentation
PriceIndividual quoteIndividual quote

Meta Pixel Setup FAQ

No - the Lead event from the browser pixel and the Lead event sent server-to-server via the Conversions API share one, common event identifier. Meta uses that identifier to deduplicate on its side, so you see one conversion in Events Manager, not two.
Nothing is sent. The browser pixel loads only after consent to "marketing" category, and the server-side Conversions API only sends a Lead event when a client-generated event identifier exists - and that identifier only exists when consent was actually granted. No consent means no event on either side.
The visitor's email address is hashed with SHA-256 before being sent to the server-side Conversions API - Meta never receives a plain-text email address, only its cryptographic hash, per the server-side Advanced Matching requirements.
Meta's fbevents.js hooks into history.pushState and automatically fires a PageView on every URL change in a single-page application like the Next.js App Router. Without disabling that mechanism (disablePushState), every SPA navigation would generate an extra, unwanted PageView alongside the one I fire manually - so I deliberately disable it and replace it with one controlled call.
The base package covers PageView and Lead - the events that actually match a lead-generation model built around a contact form. Additional, custom events (for an e-commerce store, for example) are quoted individually, since their shape and parameters depend on your specific conversion process.
Auditing the current setup takes 1-2 days, installing the pixel and consent gate extra day, implementing the server-side Conversions API with deduplication extra day, and verification plus documentation another week. Altogether, expect roughly up to a week.
I use: Meta Events Manager / Test Events, c15t Consent Manager, Meta Pixel Helper (browser verification) and Graph API Explorer.

Other services I offer

Explore my other services that might fit your needs

GTM Implementation
Container setup, Data Layer design, and Consent Mode integration - with an honest account of when a container actually makes sense, and when direct integration in code wins instead.
Learn more
Google Ads Setup
Technical Google Ads conversion tracking built on a typed GA4 event system - concrete conversion events, consent-aware, no campaign management.
Learn more
Google Search Console Setup
Ownership verification, sitemap submission, indexing-error monitoring, and performance-report analysis - grounded in the same routing-table and sitemap mechanics that run on this site.
Learn more
Sitemap Optimization
Sitemap audit, crawl-budget methodology, canonical-URL hygiene, and robots.txt alignment - methodology proven on a sitemap generated from code, with no crawler, on this site.
Learn more

Request Meta Pixel setup

Meta Pixel configured so it never double-counts a conversion or fires without consent. I connect the browser pixel with the server-side Meta Conversions API, sharing one event identifier - exactly how it runs on this site.

Request Meta Pixel setup
© 2026 ENATIV
ProjectsServicesKnowledge hubContact
contact@enativ.pl