Custom events

Custom events count important actions: signup, download, button click, purchase or quote request. They must remain aggregate and free of personal data.

#Send an event

window.snorklee('signup');
window.snorklee('purchase', { amount: 49, currency: 'EUR' });

The name must contain only letters, numbers or _ (maximum 40 characters; normalised to lowercase server-side, so SignUp and signup count together). The tracker also limits the number of events sent on one page (20 per pageview).

#Good examples

• signup
• trial_started
• pricing_click
• purchase
• download

#Bad examples

Do not use an event name or property containing a person: email, phone, name, customer identifier, account, personal order number, free-text message or sensitive data.

#Where to see them

Events appear in the "Triggered events" card of the Analytics tab (Conversions & revenue section) and in CSV exports. They help understand conversions, not follow up with a precise visitor.

#Form tracking

The script automatically tracks two technical form events: form_submit when a form is submitted and form_abandon when a visitor leaves after interacting without submitting. Only a technical form identifier is sent when available; entered fields and free-text messages are never collected.

These events appear in the "Triggered events" card of the Analytics tab. They can also be used in a simple segment or in segment-based AI analysis.