Track without custom JavaScript
Add data-talivia-event attributes to buttons and links when a declarative HTML setup is enough.
Page views show where traffic went. Custom events show what happened there: a signup click, demo request, checkout start, activation step, or any product action your team names. Talivia keeps the trend, event totals, and underlying session together.
The dashboard chart shows when activity changes, while the ranked event list shows which actions created the total. Open the event report or a session when a spike needs context.
Add data-talivia-event attributes to buttons and links when a declarative HTML setup is enough.
Use window.talivia.track when an event depends on form results, application state, or a server response.
Attach event fields such as plan, location, or experiment context, then use those details during session-level investigation.
Choose stable names such as signup-click or checkout-started instead of encoding volatile UI copy.
Use an HTML attribute, visibility tracking, or the JavaScript tracker function that matches the interaction.
Compare event volume over time, then inspect sessions, goals, or funnels without losing the original event context.
Useful event analytics depends on stable naming and deliberate instrumentation. A click event does not prove a signup or payment completed.
Start with actions tied to a real decision: signup success, demo request, checkout start, activation, upgrade, and important outbound links. Add events only when you know how the result will be used.
Yes. Data attributes and window.talivia.track can send event data that remains available for event and session investigation.
Yes. Custom events and their data can be used in Goals and Funnels, while the original event remains visible in the session timeline.
Install the tracker, name one meaningful event, and see it inside the visitor journey.
Add your website