Trackable Events in Pixel Plus
Pixel Plus can send over 20 different Facebook events across your store. Each event gives Meta data it uses to understand your visitors, optimize ad delivery, and power features like Dynamic Ads and custom audiences. This guide covers every event available — what it tracks, when to enable it, and what it's used for.
📐 Event types
Before diving in, there are two event types to be aware of:
- Dynamic Events — Automatically include product data (IDs, names, prices, categories). Required for Dynamic Ads (retargeting specific products to specific users).
- Custom Value Events — Send a fixed numeric value you set in the module. Useful for lead scoring and custom audience building.
👁️ View Events
PageView
Config key: FCTP_PAGEVIEW
Fires on every page load across the entire store: homepage, product pages, category pages, CMS pages, cart, checkout, etc.
Enable this unless you have a specific reason not to. It is the foundation for URL-based custom audiences — for example, "users who visited /sale/" or "users who reached checkout but didn't purchase."
ViewContent
Config key: FCTP_VIEWED · Dynamic Event
Fires when a customer views a single product page. Sends the product ID, name, price, category, and currency to Meta.
This is essential for Dynamic Ads — Meta uses this event to show the exact products a visitor viewed in your retargeting ads. Product listings (category pages, search results) do not fire this event.
ViewCategory
Config key: FCTP_CATEGORY · Dynamic Event · Optional value
Fires when a customer views a category page. Sends a list of product IDs from that category (configurable: 5–10 products, top sellers or default position).
Useful for building category-level audiences and for Dynamic Ads targeting visitors by category interest.
ViewCMS
Config key: FCTP_CMS · Optional value
Fires when a customer views a CMS page (About Us, FAQ, Terms and Conditions, etc.).
Useful for audiences based on content engagement — for example, targeting users who read your FAQ page.
ViewCart
Config key: FCTP_VIEWCART · Optional value
Fires when a customer views their cart page.
Useful for building "cart abandonment" audiences — users who got to the cart but didn't start checkout.
🛒 Conversion Events
AddToCart
Config key: FCTP_ADD_TO_CART · Dynamic Event
Fires every time a customer adds a product to their cart. Sends the product ID, quantity, price, and currency.
Essential for Dynamic Ads and for measuring the health of your product pages. Meta uses AddToCart signals to optimize "Add to Cart" and "Purchase" campaigns.
Purchase
Config key: FCTP_CONV · Dynamic Event
Fires when an order is placed. Sends the order value, currency, and all product IDs in the order.
This is the most important event. It powers conversion campaigns, ROAS reporting, and purchase-based audiences. For advanced control over when this event fires (validated orders, bank transfers, deduplication), see the Purchase Event Advanced Settings guide.
InitiateCheckout
Config key: FCTP_START_ORD · Optional value
Fires when a customer clicks "Proceed to Checkout."
Marks the start of the purchase funnel. Used by Meta to build checkout-abandonment audiences and optimize for high-intent visitors.
CompleteRegistration / GuestRegistration
Config key: FCTP_REG · Optional value
Fires when a customer creates a new account (CompleteRegistration) or completes an order as a guest (GuestRegistration). Both use the same toggle.
Useful for measuring account sign-ups and optimizing for new customer acquisition campaigns.
Checkout Steps (beta)
These three events track individual steps of the checkout process. They are marked beta because they depend on your checkout module's hook implementation and may not fire on all themes or custom checkout flows.
| Event | Config key | When it fires |
|---|---|---|
CheckoutPersonalInfo | FCTP_CHECKOUT_PERSONAL_INFO | Customer confirms personal info or logs in during checkout |
CheckoutAddressStep | FCTP_CHECKOUT_ADDRESS | Customer confirms delivery address |
AddShippingInfo | FCTP_ADD_SHIPPING_INFO | Customer selects a shipping method |
AddPaymentInfo | FCTP_START | Customer starts the payment step |
Each step can have an optional custom value. Enable these only if your checkout module supports them — test first with the Facebook Events Manager or Pixel Helper.
💬 Engagement Events
Search
Config key: FCTP_SEARCH · Optional value
Fires when a customer performs a site search. Sends the search query and a list of product IDs from the results (configurable: 5–10 items).
Useful for understanding search behavior and building audiences of high-intent product seekers.
AddToWishlist
Config key: FCTP_WISH · Optional value
Fires when a customer adds a product to their wishlist.
Requires the PrestaShop Block Wishlist module to be installed and active. Triggers only on the button selector configured in the module's Advanced Options.
Contact
Config key: FCTP_CONTACT_US · Optional value
Fires when a customer submits the store's contact form.
Use this to build audiences of users who contacted you, or to track lead generation campaigns.
Discount
Config key: FCTP_DISCOUNT · Optional value
Fires when a customer applies a discount code in their cart.
Useful for measuring the effectiveness of coupon-based campaigns.
Newsletter
Config key: FCTP_NEWSLETTER · Optional value
Fires when a customer subscribes to your newsletter.
Use this to track newsletter opt-ins as leads and to build lookalike audiences based on subscribers.
👥 Audience Quality Events
These events don't map directly to conversions. Their purpose is to build richer audience segments.
CustomizeProduct
Fires once per user (cookie-based) when a customer changes a product attribute or combination — for example, selecting a size or color on a product page.
Used to identify users with high purchase intent who are actively configuring products.
Time Spent on Page
Config key: FCTP_PAGETIME · Optional value
Fires a custom event every 30 seconds a user stays on a page:
Time30s → Time60s → Time90s → Time120s
Use these to build audiences of engaged visitors — for example, "users who spent at least 60 seconds on any product page."
Pages Viewed
Config key: FCTP_PAGEVIEW_COUNT · Optional value · Configurable duration
Fires a custom event at every 5-page milestone during a session:
PagesViewed5 → PagesViewed10 → PagesViewed15 → PagesViewed20 → PagesViewedMore20
You can configure how many days the page count is tracked (using a cookie). Use these to identify your most engaged repeat visitors.
✅ Final Checklist
- PageView enabled (required for all URL-based audiences)
- ViewContent enabled (required for Dynamic Ads)
- AddToCart enabled (required for Dynamic Ads and funnel analysis)
- Purchase enabled with deduplication reviewed (see Advanced Settings)
- Beta checkout events tested in Events Manager before going live
- AddToWishlist: Wishlist module installed and selector configured
- Custom value fields filled for events you use in value-based campaigns
Which events are required for Dynamic Ads to work?
ViewContent and AddToCart are required for Dynamic Ads. ViewContent sends data when a customer views a product page, and AddToCart sends data when they add a product to cart. Purchase completes the funnel. All three must be enabled with the correct product identifier.
What is the difference between a Dynamic Event and a Custom Value Event?
Dynamic Events automatically include product data such as IDs, names, prices, and categories from the page context. Custom Value Events send a fixed number you set manually in the module settings, useful for lead scoring or assigning a value to non-purchase actions.
Should I enable PageView?
Yes, in almost all cases. PageView fires on every page load and is the foundation for URL-based custom audiences. Without it, you cannot build audiences like users who visited a specific category or reached checkout.
Do all checkout step events work on every store?
No. Checkout step events are marked beta because they depend on hooks fired by your active checkout module. On custom one-page checkout flows, some or all of these events may not fire. Always verify each event in Events Manager or with the Facebook Pixel Helper before relying on them.
Can I enable AddToWishlist without the Block Wishlist module?
No. The AddToWishlist event requires the PrestaShop Block Wishlist module to be installed and active. You also need to configure the correct CSS selector for the wishlist button in the Pixel Plus advanced options.