Meta Pixel integration automatically tracks funnel events to Facebook Events Manager, enabling better ad targeting and campaign optimization across Facebook and Instagram.

​
Features

  • Event Tracking: Automatic capture of purchase, registration, and engagement events
  • Conversions API: Server-side backup for browser events

​
Meta Pixel vs Conversions API

Understanding the difference between these two tracking methods is essential:
  • Meta Pixel creates user identity on your funnel and tracks events from the browser.
  • Conversions API receives events from FunnelFox servers and checks if these events were already sent from the browser.
Conversions API is an addition to Meta Pixel that we highly recommend for complete event coverage.

​
Why Use Conversions API

Conversions API provides essential backup for browser events that may not always be available: For example, if user purchases your product using PayPal in tab-less browsers (such as Facebook WebView), browser would not send Purchase event. This happens because purchase occurs on paypal.com side, while your funnel is closed and cannot receive updates. Conversions API steps in to fix this issue — FunnelFox servers receive PayPal transaction and send Purchase event using Conversions API. As a result — you don’t loose any events. FunnelFox ensures events from browser and server are properly deduplicated in Facebook Events Manager, resulting in accurate conversion tracking.

​
Tracked Events

Trial conversion is tracked as Purchase. For paid trials, we send: Purchase → Purchase → Renewal …
EventMeta Pixel TriggerConversions API Trigger
PurchaseUser completed checkout (not for free trial)FunnelFox received transaction event from PSP (not for free trial)
StartTrialUser completed checkout with only free trial productFunnelFox received new transaction event from PSP with only free trial product
Renewal-FunnelFox received transaction event from PSP that is listed as subscription renewal
checkout_presentedUser has opened a screen with checkout
(Can fire multiple times)		-
InitiateCheckoutUser has seen the checkout element
(Triggers only once per user session)		-
CompleteRegistrationUser completed screen with Authorization element or email inputUser completed screen with Authorization element or email input
ViewContentUser navigated to a new screen-