Telemetry Events Reference

Examine the complete list of telemetry events tracked by the TellBack widget.

Last updated:2026-07-11

When a telemetry session is active, the TellBack script queues behavioral and diagnostic events to help developers debug visual, network, and logic errors.

---

Catalog of Telemetry Events

1. page_view

• When it fires: On initial page load.
• What it helps diagnose: Page path transitions and initial referrer channels.
• User-entered text: None.
• Privacy note: Captures public URLs and standard browser environment properties.

2. route_change

• When it fires: On Single Page Application (SPA) client-side routing changes.
• What it helps diagnose: SPA transitions without full document reloads.
• User-entered text: None.

3. repeated_navigation

• When it fires: When a user navigates to the same path repeatedly within a short window (possible redirect loop).
• What it helps diagnose: Broken routing states.
• User-entered text: None.

4. click

• When it fires: When a visitor clicks an interactive element.
• What it helps diagnose: Click targets, coordinate placements, and target selector details.
• User-entered text: None.
• Privacy note: Click text is redacted if the target is sensitive or matched by Balanced/Strict masking configurations.

5. rage_click

• When it fires: When a user clicks a single element rapidly (e.g. 5+ times in 1 second).
• What it helps diagnose: Stiff UI elements, broken scripts, or unresponsive buttons.
• User-entered text: None.

6. dead_click

• When it fires: When a user clicks an element that fails to yield any DOM mutation or state change.
• What it helps diagnose: Unattached button listeners.
• User-entered text: None.

7. scroll_depth

• When it fires: When a user scrolls past page milestones (e.g., 25%, 50%, 75%, 100%).
• What it helps diagnose: Content visibility and scroll boundaries.
• User-entered text: None.

8. form_focus / form_blur

• When it fires: When a user moves focus into or out of a form field.
• What it helps diagnose: Form interaction patterns and input drop-offs.
• User-entered text: None.

9. input_metadata_change

• When it fires: When a user types in a form field.
• What it helps diagnose: Character counts, whether the field is dirty, and validation timing.
• User-entered text: None. TellBack never records or transmits raw characters typed into inputs.

10. repeated_submit_failure

• When it fires: When a form submission action fails repeatedly.
• What it helps diagnose: Broken validations or API errors.
• User-entered text: None.

11. form_abandon

• When it fires: When a user leaves a form after interacting with it without submitting.
• What it helps diagnose: High form friction.
• User-entered text: None.

12. console_error

• When it fires: When a Javascript error occurs or console.error() is invoked.
• What it helps diagnose: Frontend runtime exceptions, stack traces, and script crashes.
• User-entered text: Contains the error message text.
• Privacy note: Review console outputs to ensure credentials or secrets are not printed.

13. network_error

• When it fires: When an XHR or Fetch request fails (e.g. status code >= 400 or network timeouts).
• What it helps diagnose: Failed endpoints, server outages, or bad API calls.
• User-entered text: None.

14. widget_open / widget_close

• When it fires: When the TellBack feedback panel is opened or closed.
• What it helps diagnose: User intent to submit.
• User-entered text: None.

15. voice_record_start / voice_record_end

• When it fires: When voice feedback recording begins or ends.
• What it helps diagnose: Voice note usage.
• User-entered text: None.

16. feedback_submit / demo_booking_submit

• When it fires: On successful feedback or demo scheduling card submissions.
• What it helps diagnose: Submission completion status.
• User-entered text: Feedback comment text.

---