Custom events and identity
Go beyond pageviews once the default install is already verified.
Custom events are for meaningful product or conversion actions. Identity and session properties help the team slice those actions by the context that actually matters.
Button clicks
Form submits
Pricing actions
Session context
Docs
How to track button clicks, form completions, pricing actions, and session properties in Deplio after the base install is live.
Where to find it
Project onboarding
Open the onboarding page and look for the enrich tracking examples.
Best timing
After first-hit verification
Do not start with custom events before the base pageview install is working.
What it unlocks
Richer events reports
The events surface becomes more useful once key actions and properties exist.
1
Start with the actions that matter to decisions
The first custom events should map to real questions the team already asks, not every possible interaction.
Track signup, checkout, upgrade, demo-request, or onboarding-complete before lower-value clicks.
Prefer business-readable event names over internal implementation names.
Keep the first event list small enough that the events report stays legible.
2
Use properties when the event alone is not enough
Properties become useful when the team needs to compare the same action across plan, region, source, or workspace type.
Send properties like plan, campaign, region, or experiment variant when they answer a real comparison question.
Avoid adding noisy properties the team will never filter on.
Use consistent keys so events stay comparable over time.
3
Read the result in Events, Funnels, and Boards
Once custom actions exist, the value shows up in reporting and reusable reviews, not just in the tracking code itself.
Open Events to see event volume and property distributions.
Use Funnels when the event belongs to a conversion path.
Promote high-value event views into saved reports or boards.
Implementation examples
Use these snippets as the first practical version
The fastest way to understand the feature is to wire one meaningful action, one event with properties, and one identity example before scaling the event model.
HTML attribute
Track a click without writing much code
Use a data attribute when a simple click or submit interaction is enough.
<button data-deplio-event='signup-click'>Sign up</button>JavaScript event
Track a custom action with properties
Use the JavaScript helper when the event should include extra context such as a plan or campaign.
window.deplio?.track('pricing-cta', { plan: 'pro', location: 'hero' });Identity context
Attach session or user-level properties
Use identify to enrich later reports with plan, workspace, region, or any useful business context.
window.deplio?.identify('user-123');
window.deplio?.identify({ plan: 'pro', workspace: 'acme-growth', region: 'apac' });FAQ
How to track button clicks, form completions, pricing actions, and session properties in Deplio after the base install is live.