Events
Events represent user actions in your website or app. Told uses events for triggering surveys and audience targeting.
Automatic events
Once the SDK is installed, Told automatically tracks:
Web
- Page views — URL and path of each page visited
- Clicks — Elements clicked by the user
- Scroll depth — How far users scroll on each page
Mobile (Android & iOS)
- Screen changes — Navigation between screens/views
Automatic events require no additional code. They're collected as soon as the SDK is initialized.
Disabling automatic tracking
If you prefer not to collect automatic events, disable them in your Source settings. This does not affect custom events.
Custom events
Custom events represent specific actions you define, such as completing a purchase, watching a video, or using a feature.
Sending custom events
Web:
told('addEvent', { event: 'purchase_completed', amount: 49.99, currency: 'EUR' })
Android:
Told.trackEvent("purchase_completed", mapOf("amount" to 49.99))
iOS:
Told.trackEvent(eventName: "purchase_completed", properties: ["amount": 49.99])
The event property (name) is required. Additional properties are optional and can be used as trigger conditions.
External event sources
Told also receives events from:
- Segment — All
analytics.track()events are forwarded automatically - dataLayer — Events pushed to
window.dataLayer(Google Tag Manager)
See Triggers — Custom Events for details.
Using events
Events can be used for:
- Survey triggers — Display a survey when a specific event occurs
- Audience filtering — Target users who have performed specific actions
- User profiles — View all events for a specific user in the Audience section
Best practices
- Use descriptive event names —
purchase_completedis better thanevent1 - Be consistent — Use the same naming convention across your app (e.g.,
snake_case) - Include relevant properties — Properties enable conditional triggers (e.g., trigger only when
amount > 100) - Don't over-track — Focus on meaningful actions that inform your feedback strategy