Events & conversions

Measure the actions that mean progress

Pageviews tell you where people went. Events tell you whether they did the thing that matters: created an account, requested a demo, invited a teammate, or completed a successful checkout.

Choose a small event vocabulary

Start with outcomes, not clicks. A useful first set is signup_completed, demo_requested, workspace_created, or checkout_started. Keep names stable so charts and funnels stay comparable over time.

Track a successful action

Call the tracker after the action has genuinely succeeded—for example, after your server confirms a signup or after a form submission resolves successfully.

window.clarvivo?.track("signup_completed", {
  plan: "growth",
  source: "pricing_page",
});

Properties should add useful context for analysis. Do not send passwords, payment details, authentication tokens, or other sensitive personal data in an event.

Conversions, forms, and commerce

Clarvivo supports conversion and ecommerce helpers in addition to named events. Use them only when their meaning is clear: a conversion for a confirmed value event and purchase tracking for a completed transaction. For payment-provider revenue attribution, prefer signed webhooks or the server-side revenue API described in Revenue attribution.

Verify before building a funnel

Publish the change, complete the action once, and confirm the event in Real-time. Then create the funnel or goal. This prevents a funnel with a step that never actually arrives.