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.

#SaaS subscriptions (MRR)

To feed the "SaaS subscription" card (collapsed "Advanced modules" section of the Analytics tab), send the subscription event on your confirmation pages. It is pseudonymised: only amounts aggregated per currency reach us, never an identifiable subscriber.

// On the "thank you / subscription confirmed" page:
window.snorklee('subscription', { action: 'new', mrr: 29, currency: 'EUR', plan: 'pro', term: 'monthly' });
// On the cancellation confirmation:
window.snorklee('subscription', { action: 'churn', mrr: 29, currency: 'EUR', plan: 'pro' });

Recognised actions: new, expansion, reactivation, contraction, churn, trial. Renewals need no event (MRR does not move); involuntary churn and changes made in the payment portal are not captured client-side.

#Where to see them

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