PixelYourSite · Meta
Meta Pixel and Conversions API for WordPress.
Track anything that matters on your WordPress site. WooCommerce and Easy Digital Downloads are fully integrated.
Meta Pixel + CAPI · video
pixel, CAPI, Advanced Matching
Pixel + Conversions API
browser and server, deduplicated
EMQ Score Boost
every signal behind the EMQ score
WooCommerce & EDD
all store events, Dynamic Ads ready
Custom events
any action, no code
Consent-aware
GDPR plugins and Limited Data Use
Pixel + Conversions API, dedicated.
Browser and server, one event ID.
Safari, Firefox and ad blockers stop a share of pixel events before Meta sees them, often the purchases you paid the most for. PixelYourSite sends each event from the browser and again from your server through the Conversions API, with one shared event ID. Meta deduplicates the pair and keeps whichever arrived, so a blocked pixel no longer means a lost conversion.
One switch per pixel.
Paste your pixel ID and Conversions API token. Every event on the site (page views, store events, forms, custom events) starts going out both ways.
Server events with the same data.
The server copy carries the same parameters, product IDs, value and user data as the browser event, so nothing is lost when the pixel is blocked.
A safety net for purchases.
Purchase can be sent through the API when a WooCommerce order reaches the status you choose, catching orders where the thank-you page never loaded. Refunds are reported too.
MCP server.
Run audits and configure anything using your own LLM.
Event Match Quality, done for you.
Every signal Meta scores, collected and sent automatically.
A higher EMQ means more of your conversions are attributed to your ads and your audiences fill with the right people. The score is built from the identifiers below; a typical WordPress setup sends one or two of them. PixelYourSite sends all four on the browser and the server side.
Browser ID
fbp
The identifier the pixel stores in a cookie. Always sent, with browser and server events.
Source
Pixel cookie
Click ID
fbc
The Meta click ID passed in the URL when someone arrives from a Facebook or Instagram ad. Captured on the landing page and attached to every later event in the session.
Source
Ad click URL
External ID
external_id
A first-party identifier PixelYourSite generates for each visitor and keeps in its own cookie, so the same person is recognised across visits and across browser and server events.
Source
PixelYourSite, first-party
Advanced Matching
em · ph · fn · ln · ct · st · zp · country
Email, phone, first and last name, city, state, postcode and country, hashed with SHA-256 before they leave your site. Sent with the Conversions API events and passed to the pixel as Advanced Matching.
Source
WordPress, WooCommerce, EDD, forms
Where the visitor’s data comes from
Logged-in users.
Name and email from the WordPress account. No configuration.
WooCommerce and EDD customers.
Name, email, phone and address from the order or payment, on the purchase and on every event after it.
Form fields.
When a visitor fills in a form, the plugin reads the name, email and phone fields you name and keeps them for the session. Works with any form plugin.
URL parameters.
Name and email passed in the link from an email campaign or an ad are saved and used for matching.
The result is a higher EMQ score without code: more matched conversions, better attribution, and larger, more accurate audiences.
WooCommerce and EDD events, ready for Dynamic Ads.
Purchase first. Then everything else, with value, content_ids, and more.
The event that matters
Purchase
Fires on the thank-you page with the order’s products, value and currency, and it is the one event PixelYourSite makes sure Meta receives.
Advanced purchase tracking.
The Purchase event is also sent through the Conversions API when the order reaches the status you choose, so Meta gets it even when the pixel never fired: closed tab, blocked script, payment gateway that skipped the thank-you page.
Profit, not just the order total.
With WooCommerce Cost of Goods, send the order’s profit as the value, so Meta optimises toward margin. Or send the total with or without tax and shipping.
Everything before and after the purchase, with the product IDs, values and currency Dynamic Ads need:
Event
Fires on
DPA ready
ViewContent
Single product page
content_ids
ViewCategory
Product category page
content_ids
AddToCart
Add-to-cart click, cart page or checkout, your choice
content_ids
RemoveFromCart
Product removed from the cart
content_ids
InitiateCheckout
Checkout page
content_ids
AddPaymentInfo
Payment step (PayPal Standard buttons)
content_ids
Subscribe · StartTrial
WooCommerce Subscriptions, EDD Recurring
—
Lead
Affiliate product click
—
FrequentShopper
Customer reaches N orders (default 2)
—
VIPClient
N orders and a minimum average order value (default 3 · 200)
—
BigWhale
Customer lifetime value passes a threshold (default 500)
—
Export customers for audiences.
Export your customers with their lifetime value as a file ready for Meta Custom Audiences and value-based lookalikes.
Lifetime-value events.
FrequentShopper, VIPClient and BigWhale fire from real order history, so you can build audiences of your best customers inside Meta.
The same for Easy Digital Downloads.
View content, add to cart, checkout, purchase, subscriptions and trials, with the download IDs your catalog uses.
Catalog IDs that match your feed.
Event ID = feed ID, or Dynamic Ads fail.
Choose the ID.
WooCommerce: product ID, SKU or a custom field. Easy Digital Downloads: download ID or SKU. Add a prefix or suffix if your feed uses one.
Variations, your way.
Report the variation or the parent product, to match how your catalog is built.
One ID across languages.
On WPML sites, translations report the same product ID, so one catalog serves every language.
Find the gaps first.
A built-in scan flags products without an ID and gives you a downloadable report before you launch the campaign.
Feeds that match by design.
Our catalog feed plugins use the same ID logic, so events and feed agree out of the box.
Every other action, with parameters for audiences.
What visitors do beyond the store, and the data to segment them.
Not all sites are e-commerce sites. PixelYourSite tracks any WordPress action, and every event, store or not, carries the same set of parameters, which is what lets you build a Meta audience like “read a blog post, came from Google, on a weekend” or a Custom Conversion for anything that really matters.
Automatic events.
Link and button clicks with their text and target, YouTube and Vimeo plays, email and phone clicks, sign-ups, downloads, comments, AdSense clicks, scroll depth, time on page.
Every form, automatically.
Any form fires a Form event on submit, with the form ID and class. To send one specific form as Lead, Contact or CompleteRegistration, add a custom event with the form trigger and target that form.
Custom events, no developer.
Sixteen triggers: a URL, a link or element click, hover, scroll, a post type, a page-view count, an email click, a form field, text copied, a video, a WooCommerce add to cart or purchase, a Google Ads call, plus one per form plugin. Seven conditions. Sent as any Meta standard event or a custom event.
Sixteen triggers, seven conditions, no code
Triggers
16
what fires the event
Page visit
A URL that contains or matches what you set.
Home page
A visit to the home page.
Post type
Any post of a WordPress post type: page, product, download, your own.
Page scroll
The page scrolled to a percentage you choose.
Number of page visits
The visitor’s Nth page view on your site.
Click on a link
A click on a link whose URL contains or matches what you set.
Click on any element
A click on a button, image, menu item or anything else, by CSS selector.
Mouse over an element
The pointer moving over an element, by CSS selector.
Embedded video view
A YouTube or Vimeo embed played.
Embedded video speed
The playback speed of an embedded video increased or decreased.
Click on an email link
A click on a mailto: link.
Filling out a form field
A visitor filling in a field of any form.
Text copied
Text copied from the page.
WooCommerce add to cart
A product added to the cart, with value and currency.
WooCommerce purchase
An order completed, with value, currency and transaction ID.
Google Ads phone conversion
Phone calls counted as Google Ads conversions, on the pages you choose.
Conditions
7
combined with AND or OR, so the event fires only for the visitors you choose
URL
The page URL contains or matches a value.
URL parameters
A URL parameter contains or matches a value.
Landing page
The first page of the visit, its URL or its URL parameters.
Traffic source
Where the visitor came from.
Device
Desktop or mobile.
User role
Guests, customers, editors, any role.
Products in the order
With the WooCommerce purchase trigger: pick products by name, SKU or ID and fire when the order includes them, or only them.
Form plugins
9
one more trigger for each one you run, so a specific form fires its own event
Contact Form 7
Elementor Form
Fluent Forms
Formidable
Forminator
Gravity Forms
Ninja Forms
WPForms
WS Form
Parameters on every event
Page title
Where the event fired
Post type & ID
post, product, download…
Traffic source
Where the visitor came from
UTM parameters
From landing page to exit page
Landing page
First page of the session
Event URL
Exact URL of the event
Browser time
Hour, day, month in the visitor’s time
User role
Visitor, customer, editor, admin
Domain
When one pixel serves several sites
Plugin name
Tells PixelYourSite events apart
Nothing before GDPR consent.
With ConsentMagic or one of four other consent plugins, the pixel does not load and no Conversions API call is made until the visitor agrees. A decline is honoured on both channels.
Limited Data Use.
Meta’s LDU flag can be applied to events for visitors covered by US state privacy laws, so Meta processes their data under those restrictions.
For developers.
Dedicated filters to disable tracking for specific users or conditions, for custom GDPR setups.
Ask your AI assistant to check it.
Audit and configure Meta tracking in plain language.
Audit the Meta setup.
“Is my pixel firing with CAPI, and is the token valid?” The assistant reads your configuration and reports what is missing.
Raise EMQ.
“Which Advanced Matching fields am I not sending?” It sees the switches and field mappings and tells you what to turn on.
Check catalog alignment.
“Do my product IDs match my Meta catalog feed?” It compares events with the feed and flags mismatches.
Change with a preview.
Turn on Advanced Matching, add a custom event, set a purchase status: the assistant shows the change and saves only after you confirm. Credentials are never shown in chat.
Multiple Meta pixels.
Run more than one pixel, each with its own conditions: by page, by post type, by WooCommerce category.
A pixel per language.
On WPML sites, fire a different pixel for each language.
Category pixels.
Fire a dedicated pixel for a WooCommerce category; it receives all the ecommerce events for that category.
Custom thank-you pages and dynamic values.
Purchase on custom thank-you pages; event values from your own fields.
Reviews
What Meta advertisers say.
Meta is one of the platforms in PixelYourSite Pro.
Google Analytics, Google Ads, TikTok, OpenAI and the others use the same events, the same matching data and the same consent rules.
Strategies
Set it up like a pro.
Step-by-step guides for Meta, written by the team that builds the plugin.