Meta Pixel·Ad pixelmeta pixel on every wordpress site, native.
paste a Meta Pixel ID, save, and the snippet renders in `<head>` gated against marketing consent. PageView + ViewContent fire automatically. Facebook, Instagram, Audience Network — one pixel, native injection, no Pixel plugin.
free trial. no credit card. all 30 integrations included on every plan.
Meta Pixel layers inside every wordpress site.
First: aggressive page caching strips the pixel because someone added it via a plugin filter that ran after the cache snapshot. PageView fires zero times.
audience funnel · Meta Pixelcold visitors → custom audiences, automatic.
PageView + ViewContent fire by default — enough to build the top three audience tiers without writing a single fbq() call. ecommerce events plug into your checkout for the bottom of the funnel.
PageView fires for every visitor with marketing consent.
ViewContent fires on product/article pages — auto-built into a Custom Audience.
AddToCart fires from your checkout flow — high-intent retargeting pool.
Purchase fires server-side via CAPI for iOS-attribution-resilient signal.
the consent gap that cuts pixel signal in half.
cheap WordPress hosting fires Meta Pixel without honoring marketing consent — which collapses iOS 14.5+ attribution because Apple ATT depends on the consent-mode signal being present and correct.
~48% iOS attribution
pixel fires before consent class is set on `<html>`. Meta's CAPI dedup window misses or downweights the event.
~92% iOS attribution
consent class is set before first paint. pixel fires with the right marketing-consent signal. Meta accepts the event into the standard attribution window.
illustrative figures based on typical DTC ecommerce traffic patterns. your numbers depend on iOS share, opt-in rate, and event mix.
paste your pixel ID. retarget by tomorrow.
Yovale validates the numeric pixel ID at save. the MU-plugin renders the Pixel snippet in `<head>` and fires PageView automatically — gated against the visitor's marketing consent.
- 1Open Tracking → Ad Pixels
Find Meta Pixel in the dashboard's tracking panel.
- 2Paste your pixel ID
Copy from Meta Events Manager → Data Sources → Pixels. format: 8–20 digit numeric.
- 3Toggle on, save
Open your site. Meta Pixel Helper extension confirms the pixel fires. PageView + ViewContent ready for ad attribution.
1234567890123456consent gate: marketing_storage required.
where Meta Pixel breaks on cheap WordPress hosting.
Cache strips the snippet
the Pixel plugin filter runs after the page cache snapshots the HTML. PageView fires zero times. attribution falls flat — and you don't know why.
Consent banner races the Pixel
the Pixel and the consent banner are added by separate plugins, so they race. sometimes Pixel fires before consent (compliance violation). sometimes after Meta's dedup window (lost attribution).
iOS 14.5 silently kills 30%+
without consent-aware firing, Meta's iOS attribution model can't trust the event. you lose ~30% of attributed conversions and Meta's reporting hides the gap inside 'modeled conversions'.
included on every Yovale plan, no upsell tier.
Starter $149/yr, Growth $249/yr, Business $499/yr — Meta Pixel works identically on all three.
fire automatically — enough to build website Custom Audiences from day one.
fires only after marketing_storage = granted. EU March 2024 enforcement covered.
AddToCart, Purchase, Lead, etc. fire from your theme/checkout via fbq() calls.
fires from your domain — no client-side proxy, full first-party cookie support.
questions before you switch hosts for Meta Pixel.
Will Meta Pixel fire correctly with EU consent?
Yovale gates the Pixel behind marketing_storage. If the visitor declined marketing cookies, the Pixel doesn't render. This satisfies the March 2024 Consent Mode v2 enforcement.
Do I need to install the WooCommerce Pixel plugin?
Only if you want server-side ecommerce events (AddToCart, Purchase) wired from WooCommerce. The base Pixel + PageView + ViewContent fire from Yovale's injector regardless.
Does this support Meta CAPI?
The browser-side Pixel ships from Yovale. Server-side CAPI (Conversions API) is a separate Meta integration that runs from your application code or a CAPI gateway — outside the WordPress page.
Will the page cache break the Pixel?
No. The snippet is part of the cached HTML. Marketing consent state lives client-side on a `<html>` class so the cache key stays page-level.
Can I use Meta Pixel with GTM?
Yes — many teams manage Meta Pixel through their GTM container. Or run Pixel direct through Yovale and skip GTM entirely. Both paths work.
other ad pixel integrations on every site.
TikTok Ads attribution — same install pattern, marketing-gated.
Google Ads conversion tag — pair with Meta Pixel for cross-network attribution.
B2B audience tracking — different platform, same install simplicity.
verify ownership of your domain in Meta Business Manager.
Meta Pixel on your WordPress site by day one.
free trial. no credit card. paste a Pixel ID, save, and Meta Pixel Helper turns green.