Pixel Event Reference

The browser API is funnelpulse('track', eventType, data). Event names are parsed case-insensitively on ingest. If a name does not match a built-in event, it falls back to custom.

Manual event examples

Use Lead for non-revenue conversions such as opt-ins, applications, or booked calls.

<script>
funnelpulse('track', 'Lead', {
  formId: 'optin-main'
});
</script>

Use Purchase only after a payment is actually complete.

<script>
funnelpulse('track', 'Purchase', {
  value: 97.00,
  currency: 'USD',
  orderId: 'order-123'
});
</script>

Automatic lead mapping

You often do not need a manual Lead call at all. When a page's URL is attached to a funnel step whose kind is opt-in or webinar registration, every successful form_submit on that page counts as a lead automatically. Use the manual event when the conversion happens somewhere the automatic mapping cannot see — a third-party form, a multi-step application, or a booked call.

Plan availability

• All automatic events and Lead are available on Pro plans and above.
• Purchase and custom events require an Enterprise plan; on lower plans they are accepted and silently discarded, so instrumenting early is safe.

Current behavior notes

• Purchase drives sales counts and reads data.value as the order value
• Lead is tracked separately and does not affect revenue
• unknown event names are accepted but treated as custom
• events attribute to funnel steps by page URL, so keep step URLs current in the step editor

Instrumentation guidance

• fire events once on the success state, not on button click
• prefer the thank-you page or platform completion callback
• if the page can be reloaded safely, include an idempotency field such as orderId for future dedupe work