Events and the funnel
Supported integrations can capture events from page view through purchase, plus lead and registration events. Exact coverage depends on the installed integration and event settings. You choose which eligible events are sent to destinations.
On this page
The core funnel
- Page View — the visitor arrives.
- Product View — they look at a specific item.
- Add to Cart — intent becomes concrete.
- Started Checkout — they begin buying.
- Purchase — the sale completes, with value and line items.
Capturing the intermediate steps rather than only the purchase is what makes drop-off analysis possible — see Conversion intelligence.
Lead generation and other events
For non-commerce sites, Lead and Registration cover the main conversions. Beyond those, many Meta Standard Events are supported, including Contact and phone clicks, Wishlist, Schedule, Start Trial, Submit Application, Donate, Find Location and Customize Product.
Choosing what to send
Every captured event is stored in AdProtektor. Separately, you choose which events are surfaced to your ad platforms.
More events is not automatically better
Ad platforms optimise against the events you send them. Flooding them with low-intent signals can make bidding worse, not better. Send the events that genuinely represent business value, and keep the rest for your own analysis.
Frequently asked questions
Can I send a custom event?
Conversions can be sent server-to-server through the custom API, which is the route for anything the standard capture does not cover.
Are events captured if the visitor blocks scripts?
Server-side captured events — Shopify webhooks, WooCommerce purchases, API ingestion — do not depend on the browser at all, so they survive client-side blocking.