Checkout Step Events
Pixel Plus can fire a separate Meta event at each step of your store's checkout process. This gives Meta a granular view of your conversion funnel — from the moment a customer clicks "Proceed to checkout" all the way to the payment step — and lets you build audiences based on where customers drop off.
Checkout step events (CheckoutPersonalInfo, CheckoutAddressStep, AddShippingInfo) are flagged as beta inside Pixel Plus. They rely on the hooks fired by your active checkout flow, so behaviour varies between themes and checkout modules. Treat them as bonus funnel signals — useful when they fire, but not load-bearing. Always verify each one in Meta Events Manager or with the Facebook Pixel Helper before using it for campaign targeting.
If your store uses an OPC module (such as The Checkout, Supercheckout, or any single-page checkout replacement), it is normal and expected that Pixel Plus cannot fire the intermediate step events — there are simply no separate steps to hook into. This is not a bug.
In an OPC setup the events that matter are InitiateCheckout → AddPaymentInfo → Purchase. Enable those three, confirm they fire, and you have a complete conversion funnel for Meta optimisation. Some additional engagement/custom events from the module may also behave differently under OPC, and that's fine — the funnel shape is just not the same as in the standard multi-step checkout. Your core conversion tracking remains intact.
📋 Available checkout events
| Event | Config key | When it fires |
|---|---|---|
InitiateCheckout | FCTP_START_ORD | Customer clicks "Proceed to Checkout" from the cart |
CheckoutPersonalInfo | FCTP_CHECKOUT_PERSONAL_INFO | Customer confirms personal info or logs in during checkout |
CheckoutAddressStep | FCTP_CHECKOUT_ADDRESS | Customer confirms the delivery address |
AddShippingInfo | FCTP_ADD_SHIPPING_INFO | Customer selects a shipping method |
AddPaymentInfo | FCTP_START | Customer reaches the payment step |
Each event can be assigned an optional custom value. This is a fixed number you set in the module — for example, 5 to represent that reaching the payment step has a lead value of €5. Leave it at 0 if you don't use value-based bidding for these events.
⚙️ Configuration
- Go to Modules > Module Manager in your Back Office
- Find Pixel Plus and click Configure
- Navigate to the Events tab
- Enable the checkout step events you want to track
- Optionally set a custom value for each event
- Click Save
At minimum, enable InitiateCheckout and AddPaymentInfo. These two create the top and bottom of the checkout funnel. The intermediate steps (address, shipping) are useful for diagnosing where customers drop off, but add noise if your checkout is a single fast-loading page.
🔍 How to verify they're firing
After enabling, test the full checkout flow on your store and then check:
Option 1 — Facebook Pixel Helper (browser extension) Install the Meta Pixel Helper Chrome extension. As you move through checkout, it shows each event as it fires in real time. Look for the event names listed in the table above.
Option 2 — Meta Events Manager Go to Meta Events Manager, select your Pixel, and open the Test Events tab. Enter your store URL and walk through checkout. Events appear within seconds.
Option 3 — Pixel Plus logging Enable the internal event log in Pixel Plus (Debug tab) to see all fired events recorded in your Back Office.
⚠️ Common issues
Step events not firing on one-page checkout (OPC) — expected
The standard multi-step PrestaShop checkout fires a hook at each step transition, which Pixel Plus listens to. One-page checkout modules render the whole flow on a single page and don't expose those intermediate transitions, so the three beta step events (Personal Info, Address, Shipping) typically won't fire under OPC. This is expected behaviour, not a malfunction.
For an OPC funnel, rely on:
- InitiateCheckout — fires when the customer enters the checkout page
- AddPaymentInfo — fires when the payment step is reached
- Purchase — fires on order confirmation
Those three define the conversion funnel Meta needs to optimise your campaigns. Any other custom or engagement events that don't behave the same way under OPC are fine to ignore — the funnel shape is simply different from a multi-step checkout. If your OPC module exposes its own hook for an intermediate step and you want it tracked, contact Smart Modules support.
InitiateCheckout fires but later steps don't
This usually means the checkout module uses AJAX to advance between steps without triggering the expected hooks. The steps that fire correctly depend on which hooks the checkout module calls. Only enable the steps you've confirmed are firing correctly.
AddPaymentInfo fires but the payment step is slow to load
The AddPaymentInfo event fires when the payment step is displayed to the customer. If your payment module loads an iframe or external redirect, the event still fires — but the customer may leave before loading completes, causing the next step (Purchase) to appear as a drop-off.
✅ Final Checklist
- Enable the checkout step events you want to track in the Events tab
- Walk through a test checkout on your store
- Verify each enabled event appears in Meta Events Manager or Pixel Helper
- Disable any step that fails to fire (to avoid gaps in funnel reporting)
- Optionally set custom values if you run value-based bidding campaigns
Which checkout events should I enable at minimum?
Enable InitiateCheckout and AddPaymentInfo at minimum. These mark the start and bottom of the checkout funnel and give Meta enough data to build checkout abandonment audiences and optimize campaigns.
Why are checkout step events marked as beta?
The intermediate checkout step events (CheckoutPersonalInfo, CheckoutAddressStep, AddShippingInfo) are beta inside Pixel Plus because they depend on hooks fired by your specific checkout module. The standard PrestaShop multi-step checkout fires them reliably; custom themes or one-page checkout modules may not.
What should I do if some checkout events are not firing?
Verify each event in Meta Events Manager or with the Facebook Pixel Helper by walking through the checkout on your store. Disable any step that does not fire to keep funnel reporting accurate. If you use a one-page checkout (OPC) module, missing intermediate steps are expected — focus on InitiateCheckout, AddPaymentInfo, and Purchase instead.
I use a one-page checkout module. Is it a problem that the step events don't fire?
No. One-page checkout modules render the whole checkout on a single page and don't expose intermediate step transitions, so Pixel Plus cannot fire the beta step events. This is expected. Track InitiateCheckout, AddPaymentInfo, and Purchase — those three define your conversion funnel under OPC, and core conversion tracking remains fully intact.
Can I assign a monetary value to checkout step events?
Yes. Each checkout event has an optional custom value field in the module settings. Set a fixed number representing the estimated value of reaching that step if you use value-based bidding. Leave it at 0 if you do not use value-based bidding.
Does InitiateCheckout fire when the customer clicks the cart checkout button?
Yes. InitiateCheckout fires when the customer clicks Proceed to Checkout from the cart page. It marks the entry point of the purchase funnel and is used by Meta to build high-intent audiences.