PixelYourSite MCP and WooCommerce
Your AI assistant can read and change every part of how PixelYourSite tracks WooCommerce. Ask it to check your setup, toggle events, change content ID settings, or configure lifecycle events — it will show you exactly what it plans to change and wait for your confirmation before saving anything.
“Check my WooCommerce tracking setup” is a good starting point. The assistant will audit the relevant areas and report anything that needs attention.
Requires WooCommerce to be installed and active. Write tools require PixelYourSite Pro.
Funnel events
WooCommerce funnel events are the standard ecommerce tracking events that fire on key shopping actions.
Read: on/off state of every funnel event.
Write (Pro): toggle any funnel event on or off. Changes apply across all active platforms.
| Event | When it fires |
|---|---|
| ViewContent | Single product page |
| AddToCart | When a product is added to the cart |
| InitiateCheckout | Checkout page |
| Purchase | Order received page |
| ViewCart | Cart page |
| ViewItemList | Product listing and category pages |
| RemoveFromCart | When a product is removed from the cart |
| CheckoutSteps | Checkout progress steps |
AddToCart can be configured to fire on the button click, on the cart page, on the checkout page, or any combination. These are writable separately.
“Turn off ViewItemList” or “Enable CheckoutSteps” are the kinds of requests the assistant handles directly.
Lifecycle events
Lifecycle events fire on the purchase event based on a customer’s order history. They let you segment audiences by purchase behaviour.
Read: on/off state and threshold for each lifecycle event.
Write (Pro): enable or disable each event, adjust thresholds.
| Event | Fires when |
|---|---|
| NewCustomer (FirstTimeBuyer) | Customer’s first purchase |
| ReturningCustomer | Customer has purchased before |
| FrequentShopper | Customer has reached a set number of transactions |
| VIPClient | Customer has reached a set number of transactions and average order value |
| BigWhale | Customer’s lifetime spend has reached a set amount |
FrequentShopper, VIPClient, and BigWhale require PixelYourSite Pro.
Subscriptions and POAS
track_subscriptions — fire events for WooCommerce subscription renewals and lifecycle changes. Requires the WooCommerce Subscriptions plugin.
POAS (Profit on Ad Spend) — send profit instead of revenue in the purchase event value. Requires the Pixel Cost of Goods add-on.
Both are readable and writable (Pro) via the assistant.
Content ID
Content ID is the product identifier sent with every ecommerce event. It must match the ID used in your product catalog feeds for dynamic ads to work.
Read: current content ID source, prefix, suffix, and per-platform values.
Write (Pro): change source, prefix, and suffix.
Source options:
- product_id — the WordPress post ID. Always present, always unique. The safe default.
- product_sku — the WooCommerce SKU. Only use this if every product has a SKU set. Products without a SKU send a blank content ID.
- custom_field — a custom product meta key you specify. PYS runs a background scan when this mode is enabled and reports how many products are missing a value for the chosen field.
Content ID is stored per platform. All platforms use the same value by default. If they have been set differently on individual platforms, the assistant will tell you and can re-align them.
variable_as_simple — for products with variations, send the parent product ID instead of the variation ID. On by default. Required for Google Merchant Center feed alignment.
content_id_logic — Facebook only. Set to facebook_for_woocommerce when the Facebook for WooCommerce extension is installed and manages catalog sync. When that extension is active, the assistant will warn you of the risk of double-firing pixel events.
WPML — if WPML is active, wpml_unified_id can be enabled to send a unified content ID across language variants of the same product.
Platform event toggles
Beyond the global funnel event switches, each platform has its own toggle for every event it supports. An event only fires for a platform when both the global toggle and the platform toggle are on.
This lets you fire Purchase on Facebook but not on GA4, for example.
Read: per-platform event toggle matrix showing which events each platform is set to fire.
Write (Pro): toggle individual events per platform.
Value settings
How the purchase event value is calculated: whether tax, shipping, and fees are included or excluded, and whether an order ID prefix is applied. These are readable but not writable via MCP — change them in PixelYourSite → WooCommerce.
Catalog feed alignment
If the Product Catalog Feed for WooCommerce plugin is installed (version 5.9 or later), the assistant can compare your content ID settings against the feed and flag any mismatch. A mismatch means your pixel events and your catalog use different product IDs, which breaks dynamic ads.
“Does my product feed match my pixel content IDs?” triggers this check.
The assistant will explain what differs and offer to fix the PYS side after you confirm that the detected feed is the one actually connected in your ad platform’s catalog manager.
Attribution reports
If “Save data to orders” is enabled in PixelYourSite settings and the historical sync is complete, the assistant can query your WooCommerce attribution data.
“What were my top traffic sources last month?” or “What products did my Black Friday campaign sell?”
Results are always WooCommerce only. EDD data is never combined with WooCommerce data in the same answer.