Extra WooCommerce Events
Extra events (WooCommerce)
These are optional events you can enable when you want more signals than the standard ecommerce flow. They’re mainly used for retargeting audiences, funnel analysis, and optimization on specific platforms.
Track remove from cart
What it does: fires when a shopper removes an item from the cart.
Why it’s useful
- Builds a “removed from cart” audience (great for retargeting with reassurance, shipping info, discounts, alternatives).
- Helps you spot product friction (items frequently removed).
Where it can send
- Facebook:
RemoveFromCart - Google Analytics:
remove_from_cart - Pinterest:
RemoveFromCart
How to use it
- Enable it only on the platforms where you care about cart-retargeting.
- If you already fire remove-from-cart from GTM, don’t enable it here too (avoid duplicates).
Track WooCommerce affiliate button clicks
(For affiliate/external products where the “Add to cart” is actually an outbound link.)
What it does: fires when users click the affiliate/external product button (the outbound “Buy” link).
Why it’s useful
- Tracks the moment a visitor leaves your site to buy elsewhere (a key conversion signal for affiliate stores).
- Lets you optimize campaigns for outbound intent, not just page views.
Key option: Value parameter settings
- If enabled, the event includes a
valueparameter (useful for reporting and bidding).
Where it can send
- Google Analytics
- Google Ads
Event Type
Choose what event name/type to send (example shown: Lead).
Pick the one that matches how you treat this action (common choices: Lead, ViewContent, InitiateCheckout—depends on your strategy).
Track WooCommerce PayPal Standard clicks
What it does: fires when the user clicks the PayPal Standard payment button (the moment they choose PayPal and leave/continue into that flow).
Why it’s useful
- Measures payment-method intent (helps diagnose checkout drop-off).
- Lets you build an audience of “clicked PayPal” users (often high intent).
Key option: Value parameter settings
- Adds a
valueparameter if enabled.
Where it can send
- Google Analytics
Event Type
Pick the event type you want to send (example shown: AddPaymentInfo).
That’s usually the best semantic match for “payment method chosen”.
Track CompleteRegistration for the Meta Pixel
What it does: sends Meta’s CompleteRegistration event for WooCommerce.
Why it’s useful
- A strong “post-purchase customer” signal for Meta, especially if you want a secondary conversion besides Purchase.
- Useful when you want to optimize for “new customer completed” style funnels, or when Purchase is handled elsewhere and you still want a Meta event.
When it fires
By default it fires on the registration/trigger logic used by the feature.
Optional checkbox:
- Fire this event every time a transaction takes place
If enabled, it triggers on each purchase (acts like an additional event alongside Purchase).
Event value on Facebook
Choose the value to send with the event:
- Order’s total
- Price minus Cost of Goods (if you use Cost of Goods)
- Percent of the order’s total
- Use global value (a fixed value)
Server-only option
- Send this from your server only. It won’t be visible in your browser
Sends the event server-side only (useful when you want less browser noise or you rely on server tracking).