The WordPress way to install Facebook Pixel is clunky
You run Facebook or Instagram ads. Without the Meta Pixel on your site, you can't build lookalike audiences, can't retarget site visitors, and the ads optimize toward clicks instead of conversions.
The canonical WordPress paths are: install an analytics plugin (comes with admin pages, updates, subscription nags), paste the snippet into functions.php (breaks when you switch themes), or set up Google Tag Manager as middleware (overkill for one pixel).
What most people do instead
A better way: one command, one ID, tracking live
Run enable fb pixel with your Pixel ID. The command auto-registers as a startup command so the tracking snippet outputs on every page load. No theme edit, no plugin, no GTM middleware.
Consent-aware flag included. Pass -consent_aware=true and the pixel only fires when your cookie-consent plugin's gate has been accepted. Works with any standard WP consent plugin that sets a cookie flag.
How it works
The command hooks wp_head with the Meta-provided tracking snippet, then auto-registers itself in Startup Commands so the tracking stays active across requests. Re-running with a different ID updates the existing entry. Disable from Startup Commands to remove.
enable fb pixel -pid=1234567890123456| Parameter | Value |
|---|---|
-pid(required) | Pixel ID (format: 1234567890123456) |
-consent_aware | true to only fire after cookie consent (checks standard consent cookie) |
| Scope | Auto-registered as startup command — runs on every frontend page load |
| Where to find the ID | Meta Events Manager → Data sources → Pixel |
| Can be used in |
Real example
You spent $400 on Facebook ads for a product launch. The ads converted poorly because Meta couldn't optimize without conversion data — the pixel wasn't installed. Run enable fb pixel -pid=1234567890123456, relaunch the campaign a week later, and Facebook optimizes toward buyers instead of clicks. ROAS triples.