Tulo Paywall - Engage BI events

Target audience: Developers, Stakeholders

Introduction

The Engage tracker embedded in every paywall emits the events below. pageview fires on every paywall; the purchase-funnel events fire only on Klarna Payments Checkout because they correspond to interactions with the embedded Klarna widget. Tulo Shop Checkout emits paywall_click_purchase as the intent-to-buy signal, since the visitor leaves the paywall iframe for Tulo Shop at that point and any further funnel tracking is owned by Tulo Shop.

Every event carries the tracker context (visitor login state, paywall identifiers, and content metadata) plus the event-specific eventCustomData shown below.

Events

Event	Klarna Payments Checkout	Tulo Shop Checkout	Fires when	eventCustomData
pageview	✓	✓	The tracker has loaded and constructed itself on paywall render.	—
paywall_click_purchase	—	✓	The visitor clicks the buy button. Auto-wired by the default template.	productCode
purchase_start	✓	—	The Klarna Payments widget initializes the purchase session.	paymentMethod ("klarna_payments"), productCode
payment_start	✓	—	The visitor authorizes payment in the Klarna Payments widget.	paymentMethod ("klarna_payments"), productCode
purchase_end	✓	—	The place-order call resolves, on both successful and unsuccessful outcomes.	paymentMethod ("klarna_payments"), orderId, productCode, orderStatus, orderStatusReason, userId (only when Visitor identification is opted in)