Tellback
Book Demo

Core Concepts

Understand the hierarchy and core building blocks of TellBack's telemetry and feedback system.

Last updated:

To make the most of TellBack, it helps to understand how your account, projects, sites, and telemetry records are structured.

The Hierarchy model

TellBack organizes information in a clear top-down structure:

text
[Workspace] (Billing & Team Organization)
    └── [Project] (Product context)
           └── [Sites] (Environments e.g., Staging, Production)
                 ├── [Feedback Items] (User bug reports)
                 └── [Widget Sessions] (Telemetry recordings)

1. Workspaces

A Workspace represents your top-level organizational boundary.

  • Team Ownership: All members belong to a workspace. User roles (Owner, Admin, Editor) are mapped at the workspace level.
  • Billing & Quotas: Subscriptions, plan tiers, session recording limits, and AI generation quotas are tied directly to the workspace.

2. Projects

A Project represents a single product or system context. Projects help separate feedback and developer pipelines:

  • Project Scope: Feedback cards, sessions, and AI settings are isolated within a project.
  • Team Allocation: You can restrict workspace members to specific projects to keep pipelines focused.

3. Sites

A Site represents an individual installation environment for your project (e.g., Staging, Production, Local Development).

  • Public Key: Each Site is assigned a distinct Public Key (data-tellback-site).
  • Telemetry Separation: Distinguishing sites ensures that local testing data does not mix with your production user telemetry.
  • Allowed Origins: Whietlisted domains are configured per Site to prevent cross-origin injection.

4. Widget Sessions (Telemetry)

When a visitor lands on your site, the TellBack script initializes a Widget Session (if your Feedback Mode enables tracking).

  • Telemetry Capture: Collects visitor route changes, console logs, click events, network performance errors, and DOM mutations.
  • Session Replay: Compiles collected DOM mutations to recreate high-fidelity session playback on your dashboard.
  • Session Length: Captures up to your plan's maximum session limits before wrapping up.

5. Feedback Cards

A Feedback Card is a user-initiated report submitted via the widget button or a Feedback Link. It includes:

  • User Inputs: The text description, optional element selection path, and optional voice note recording.
  • System Diagnostics: Masked screenshots, device type, screen dimensions, user agent details, and a direct lookup link to the associated Widget Session.
  • AI Task Generation: TellBack parses this raw telemetry through Gemini to compile clean, formatted developer issues automatically.

Privacy Responsibility
Site owners are responsible for providing appropriate visitor notices and obtaining any required consent for feedback collection, pageview tracking, session context, replay, audio, screenshots, and AI processing.