Events & visitor timelines

Create a naming plan#

Choose stable names such as signup_complete, pricing_cta or demo_requested. Use the same name for the same action across the site. Do not embed emails, customer IDs, order numbers or arbitrary form text.

Instrument and verify#

1. Add window.weeveo.track("demo_requested") after the actual successful action, not merely the initial click when success matters.
2. Make a consented manual test visit.
3. Find the name in Events under a range including today.
4. Create an event goal if it represents a conversion.
5. Use that exact event name in a funnel step.

Read event counts#

Events shows names, counts, unique visitors and visitor conversion rate. An event count can exceed visitors because a visitor may repeat an action. Internal names such as $pageview, $heartbeat, $leave, $engagement, $performance and $identify are reserved tracker behavior, not a convention for your custom events.

Visitor activity#

Visitor lists and detail timelines can contain personal analytics data. Their availability depends on tracking mode and retained permitted records. Limit access appropriately; a timeline does not prove that two devices belong to one person.

API equivalents#

list_events, list_visitors and get_visitor_events. For method signatures and validation see the browser SDK.