Events
Named actions such as signup_complete or download. Recorded automatically for common actions, or manually with JavaScript / a data attribute.
Measure actions, not just pageviews: record events, count successful outcomes as goals and trace the steps visitors take — without collecting a single form value.
Named actions such as signup_complete or download. Recorded automatically for common actions, or manually with JavaScript / a data attribute.
One configured outcome per website — an event name or an exact page path — counted as daily-deduplicated sessions in the Engagement report.
2–8 event names in order, showing how many sessions reached each step and where they dropped out.
2–8 exact page paths in order — no event code needed — shown as funnel exploration for all visitors.
Settings defines how actions appear in reports; your website must capture the actions. Install the normal visitora.eu snippet first, then add one of the following.
visitora('event', 'signup_complete');
The equivalent method is visitora.trackEvent('signup_complete'). To queue an event before the script has loaded, use the stub:
window.visitora = window.visitora || function () {
(window.visitora.q = window.visitora.q || []).push(arguments);
};
visitora('event', 'signup_complete');
Buttons and links default to the click trigger:
<button data-visitora-event="download_started">Download</button>
Forms default to the submit trigger; the input event fires at most once per field:
<form data-visitora-event="signup_submit">
<input type="email" data-visitora-event="signup_start" placeholder="you@example.com">
<button type="submit">Create account</button>
</form>
To override the trigger, add data-visitora-event-on="click|submit|input|change".
Enabled per website in Settings → Goals & events, automatic discovery recognises common actions from descriptors only — URLs, form attributes, button labels, link destinations. Input values are never read. Discovered events:
signup_view, signup_start, signup_submitcontact_view, contact_start, contact_submitcheckout_view, checkout_startsearch_submit, download, outbound_click — plus newsletter subscribe and pricing/contact page viewsConfirmed outcomes need explicit events. visitora.eu does not infer successful registration, contact or payment from clicks alone. Fire an explicit signup_complete, contact_success or purchase_complete on the confirmation step, then use that name as the goal target.
free_signup, choose Event or Page, and enter the event name or exact page path (for example /pricing).signup_view
signup_start
signup_submit
signup_complete
No. Automatic discovery recognises common actions — signup, contact, checkout and search activity, downloads, outbound links — from page URLs, form descriptors, button labels and link destinations. Custom events need one line of JavaScript or one HTML attribute.
Lowercase letters, digits and underscores, up to 40 characters. The tracker normalises names automatically: it lowercases, removes everything except a–z, 0–9 and _ and truncates. Use snake_case such as signup_complete.
No. Events are names only. This is a deliberate privacy limit: no form values, prices, email addresses or free-form text ever reach visitora.eu. Use distinct event names (checkout_start, purchase_complete) instead of values.
Goal reports show daily-deduplicated sessions: within one day, repeat completions of the same goal count once per session, while the total trigger counter shows every completion. Event funnels also deduplicate per session and day.
A funnel requires the ordered steps in sequence; a goal counts each completion on its own. Visitors who skip a step or arrive directly at the last step complete the goal but not the funnel.
No. visitora.eu never infers successful registration, contact or payment from clicks alone. Add an explicit completion event such as signup_complete on your confirmation page or success handler.