PixelYourSite fires the right standard events on every CartFlows step (ViewContent, AddToCart, InitiateCheckout, Lead, Purchase) and adds a set of CartFlows-named custom events so you can build audiences and conversions for any flow, step, or bump. Meta Conversion API works for all of them, Purchases included.
The video covers the full setup. The sections below are the reference for what fires and how to configure it.
Supported tags and APIs
CartFlows tracking works for every platform PixelYourSite supports:
- Meta Pixel and Meta Conversions API
- Google Analytics (GA4) and GA4 Measurement Protocol
- Google Ads
- Pinterest (and Pinterest API via add-on)
- Bing (via add-on)
- TikTok and TikTok Events API
- Reddit (via add-on)
Standard events fired on CartFlows steps
The standard events fire automatically through the WooCommerce path with the right parameters for Meta Dynamic Ads, Google Dynamic Remarketing, Pinterest, Bing, and TikTok:
- ViewContent — on every CartFlows landing page. Optionally on upsell/downsell pages too (toggle in CartFlows settings).
- AddToCart — when a visitor moves to the next step or accepts an order bump.
- InitiateCheckout — on CartFlows checkout pages.
- Lead — on optin completion.
- Purchase — on the CartFlows transaction. Upsell and downsell totals are captured.
Custom events for every CartFlows action
PixelYourSite also fires CartFlows-named custom events so you can target by flow, step, or bump in any platform that accepts custom events.
| Event name | Fires on |
|---|---|
CartFlows | Every CartFlows page. Good for a broad CartFlows-visitor audience. |
CartFlows_landing | Each landing step. |
CartFlows_checkout | Each checkout step. |
CartFlows_optin | Each optin step. |
CartFlows_upsell | Each upsell step. |
CartFlows_downsell | Each downsell step. |
CartFlows_thankyou | Each thank-you step. |
CartFlows_bump | When an order bump is accepted. |
The per-step events are generated automatically from the CartFlows step type, so any custom step type you add will produce an event with that name prefixed by CartFlows_.
Parameters attached to every CartFlows event
Three global parameters ride along with every event fired on a CartFlows page (all on by default, each toggle-able in the plugin):
cartlows=yes— marker that the event happened inside a CartFlows flow. Note: this key is spelledcartlows(missing thef) in the current plugin version. Use that exact spelling when you set up a Custom Dimension in GA4 or a Custom Conversion in Meta.cartflows_flow— the flow’s title.cartflows_step— the step type (landing,checkout,optin,upsell,downsell,thankyou, etc.).
Use them to build flow-level or step-level audiences and conversions without creating separate events.
Where to configure it
In the WordPress admin: PixelYourSite Pro → CartFlows.
Each tag (Meta, Meta CAPI, GA4, Google Ads, Bing, Pinterest, Reddit) has its own card on this page. You can:
- Turn the integration on with the Enable CartFlows set-up switch.
- Enable per-step toggles (sell-step ViewContent, order-bump AddToCart, etc.).
- Toggle the three global parameters independently.
Dedicated CartFlows pixels
Each platform card on the CartFlows page accepts its own Pixel ID, API token, test-event code, and domain-verification tag. Use this if you want a separate Meta Pixel, GA4 property, Google Ads account, etc. that tracks only CartFlows activity — without touching the rest of your site’s tracking.
If you want CartFlows to use the same pixels as the rest of the site, leave these fields empty and PixelYourSite uses the main IDs from each platform’s settings.
Disable CartFlows native tracking
Important. CartFlows has its own Meta Pixel and GA4 integrations built in. If both CartFlows and PixelYourSite fire to the same Pixel/Property, every event ships twice.
Turn CartFlows’s own tracking off:
- Meta Pixel: CartFlows → Settings → Facebook Pixel → clear the ID.
- Google Analytics: CartFlows → Settings → Google Analytics → clear the ID.
PixelYourSite handles the firing from here.