Analytics and consent integration · Updated November 15, 2026
Meta Pixel integration
The Meta Pixel reports website actions to Meta from the browser, and the Conversions API sends the same actions from your server. We set up both on WordPress, Webflow, Astro, Next.js or custom software, with matching event IDs so Meta counts each action once, and consent deciding whether either one runs.
Meta Pixel at a glance
- Connects
- The Meta Pixel in the browser, the Conversions API from a server, and Events Manager for testing.
- WordPress
- Meta's official plugin installs the Pixel and includes Conversions API support.
- Webflow
- A native Pixel ID setting with a consent delay toggle. No native Conversions API.
- Astro or Next.js with Sanity
- A layout loads the Pixel after consent; an API route sends the matching server event.
- Custom software
- Conversions API calls from your backend with an access token from Events Manager.
- Complexity
- Medium. The Pixel is quick; deduplication and data rules need care.
- Typical setup
- 1 day for the Pixel with consent, 3 to 6 days with the Conversions API and deduplication.
How we connect Meta Pixel
WordPress
Meta pixel for WordPress, published by Facebook, installs the Pixel and includes Conversions API support. As of November 15, 2026 it lists 400,000+ installs and a 2.7 star rating, so we check events in Events Manager after every plugin update. When GA4 already runs through Tag Manager, we load the Pixel there instead.
Webflow
Webflow's Meta Pixel setting takes only the Pixel ID, sends ecommerce events when Ecommerce is on, and has a Delay for cookie consent toggle. The toggle waits for consent but doesn't supply a banner, so we add one. Webflow has no native Conversions API, so server events run in a function we host or through server-side Tag Manager.
Astro or Next.js with Sanity
A layout component loads the Pixel after consent and fires Lead or Purchase with an eventID. The API route that saves the form or confirms the payment sends the same event to the Conversions API with that ID, the visitor's IP address and user agent, and a hashed email.
Custom software
Your backend posts events with an access token generated in Events Manager. Meta requires event_source_url and the user agent for website events, and fails a request with an event_time more than 7 days old. Server events also cover actions with no browser at all, such as a payment your billing system confirms later.
What organizations use Meta Pixel for
Counting each action once
When the Pixel and the Conversions API both send a Lead, Meta drops the duplicate if the Pixel's eventID matches the server's event_id and the event names match, within 48 hours. We create the ID once in the page and pass it to the server with the form.
Hashed customer data
Meta's terms require contact details to be hashed before they're sent from a server. We normalize each field the way Meta specifies, such as trimmed lowercase email and phone numbers with country code 1, then hash with SHA-256. IP address and user agent go unhashed, as Meta asks.
Actions ad blockers hide
Server events reach Meta when an ad blocker or browser setting stops the Pixel. A registration or gift confirmed by your payment processor still counts, so campaign reports sit closer to your CRM numbers.
What to watch out for
Health and sensitive data
Meta's Business Tools Terms forbid sending data that includes or is based on health or financial information or other sensitive categories, or data about children under 13. For a health charity, page URLs and event names can count. Meta also limits data from some health and wellness advertisers, and Events Manager shows whether yours is restricted.
Revoked until the visitor agrees
The Pixel's consent call, fbq('consent', 'revoke'), pauses sending until fbq('consent', 'grant') runs. We revoke by default, grant when the visitor opts in, and send server events only for visitors who agreed. Meta processes data outside Quebec, so Law 25 calls for a privacy impact assessment first.
Tokens stay on the server
A Conversions API access token can send events to your Pixel, so it lives in server settings and never in page code. We ask your Business Manager admin to give us access rather than share a personal login.
Sources
Checked against Meta's developer docs and Business Tools Terms on November 15, 2026.
- Handling duplicate Pixel and Conversions API events event_id, 48 hours
- Customer information parameters normalizing and hashing
- Server event parameters event_time, event_source_url
- Conversions API: get started access tokens
- Meta Pixel consent revoke and grant
- Meta Business Tools Terms restricted information, hashing
- Meta pixel for WordPress
- Webflow: embed Meta Pixel
- Quebec private sector privacy act (Law 25) sections 8.1 and 17
- OPC guidelines on online behavioural advertising
Questions about Meta Pixel
Do we need the Conversions API if we have the Pixel?
Not always. The Pixel alone covers many small sites. The Conversions API helps when browsers block the Pixel, when the action finishes on a server, such as a payment confirmation, or when it happens offline.
Can a health charity use the Meta Pixel?
Yes, with limits. Meta's terms bar sharing health information, so condition-specific pages, symptom checkers and appointment forms stay out of tracking. We keep the Pixel to general pages like donate and events, and remove URL paths and parameters that describe a condition.
Is consent needed for the Meta Pixel in Canada?
We treat it as opt-in. The Pixel builds advertising profiles, and Law 25 requires profiling tools to be explained and off until a visitor turns them on. The Privacy Commissioner's PIPEDA guidance only accepts opt-out for tracking that avoids sensitive information like health.
Related integrations
Cookiebot
Cookiebot is Usercentrics' consent management platform for small and mid-sized sites, with a cookie scanner, consent banner, automatic blocking and Google Consent Mode.
Cookiebot integrationCookieYes
CookieYes is a consent management platform with a cookie scanner, banner templates, automatic and manual script blocking, and Google Consent Mode v2 support.
CookieYes integrationFathom Analytics
Fathom Analytics is a paid, cookieless website analytics service run by Conva Ventures Inc. of Victoria, British Columbia.
Fathom Analytics integrationGoogle Analytics 4
Google Analytics 4 is Google's web and app analytics product. It measures visits as events and processes them on Google's servers, with no documented option to keep data in Canada.
Google Analytics 4 integrationGoogle Tag Manager
Google Tag Manager is Google's tag management system. A web container loads tags such as GA4 and the Meta Pixel in the browser; a server container runs them on infrastructure you host.
Google Tag Manager integrationMicrosoft Clarity
Microsoft Clarity is Microsoft's free behaviour analytics tool, with session recordings, click and scroll heatmaps, and a GA4 connection.
Microsoft Clarity integrationNonprofit websites
Charity sites that measure Meta campaigns without sending health data.
Nonprofit websitesBusiness automation
Server events that send confirmed gifts and registrations to the Conversions API.
Business automationWebsite development
Sites with the Pixel behind consent and server events from day one.
Website development
Running Meta ads to your site?
Tell us which actions you want Meta to count and what your pages are about. We'll say whether the Pixel alone is enough, where the Conversions API helps, and what Meta's data rules keep out.
Book a call