Maintained Analytics dimensions
Explore confirmed customer metadata without rereading trace bodies.
Watch the workflow: Follow an analytics category to recorded evidence · Authored dummy data
Inspect category counts and the recorded source evidence behind one count. This clip uses a source-defined authored demo analysis. It does not show maintained-catalog approval, code confirmation or catalog maintenance. Switch an authored source-defined event analysis to category totals, filter a six-event category, inspect one exact record reference and follow its source trace. These are retained event counts, not customer outcomes or maintained-catalog approval.
Read the walkthrough transcript
- 00:00 — Compare authored event counts in Tensile. This demo uses a source-defined analysis.
- 00:06 — Select high to inspect six authored events. Counts describe retained evidence only.
- 00:11 — Open an exact record reference. See the recorded source trace behind the count.
- 00:17 — Follow the source trace. Recorded events do not establish customer success.
Analytics can use a shared dimension catalog for a connected customer source. The background job reads metadata and persists normalized categorical values and exact record references. Chart queries use these stored fields, rather than the full trace. Each workspace and connected project has its own set of records and mapping; all business accounts in that authorized project are included.
Choose a dimension
Confirmed fields with two to eleven values are available for grouping. Still-approved categories can remain visible with zero records. A field with only one remaining value is unavailable for a new selection. Select dates, a field and an optional second field. Select a chart point or category to filter the underlying records; the table uses the same record set. Missing values, conflicting values and unconfirmed codes remain separate. Observed counts describe retained evidence, not complete customer history.
Personal saved analyses retain their mapping revision. Reopening one cannot silently adopt newly confirmed code meanings. A withdrawn or unsafe dimension becomes unavailable; choose another field or create a new analysis.
Review new codes
New values remain pending until their meaning is confirmed. Ordinary Analytics readers see pending counts, without the raw codes. Authorized Tensile reviewers can review proposed values and confirm a label. If the mapping changes, reload it before confirming; retries cannot overwrite another review.
Customer identity, cohort rules and declared source vocabulary are configured for each connected project. A different customer can use different fields and stable keys. Identifiers, person names, contact details, free text, lists and measures do not become grouping dimensions merely because they have few values.
Availability
The catalog applies retention, source access and held-out evidence restrictions. Corrections, source movements and deletions are reconciled by the metadata job. An incomplete or oversized read reports an unavailable or held result, rather than a partial total. Data outside retained history cannot be queried.