Skip to main content
The data dictionary is an auto-generated catalog of every custom event name, event property, and user trait your site has collected — with each name’s inferred type, example values, how often it appears, and when it was first and last seen. It answers the question every growing analytics account eventually asks: “what does this name actually mean, and is it the real one?” On top of the inventory, your team can add a description to each name and mark the official ones as verified.

​
What the dictionary catalogs

tinyanalytics never rejects a new name — you can send any custom event or property and it’s collected immediately. That’s convenient, but over time a busy namespace fills with duplicates (plan vs. subscription_plan), typos (singup), and throwaways (test_event). The dictionary discovers and lists all of it automatically, across these kinds: There’s nothing to register — the inventory is read directly from your data every time you open the page.

​
What does each dictionary entry show?

For every name, the dictionary infers and shows:
  • Type — string, numeric, boolean, or datetime, inferred from a sample of real values.
  • Example values — a few actual values so you can see what the name holds.
  • Volume — how often the name appears.
  • First and last seen — across all time, not just your selected date range, so freshness reaches past any dashboard window.
Click an entry to open a detail drawer: an event shows its properties, and a property or trait shows its value distribution and which events carry it.

​
What does “verified” mean?

Verified means a human on your team reviewed the name and confirmed it’s the official, canonical one — not a typo, a test, or an abandoned field. It records who verified it and when, so the confirmation is attributable and trustworthy. Verified is a label only. Marking a name verified does not change what’s collected, hide or exclude anything from your reports, reorder the list, or alter any data. It’s a trust signal for your team — “this is the real event, use this one” — nothing more.
Adding descriptions and marking names verified requires an owner or admin role. A name you’ve described or verified keeps showing even after it stops appearing in new data, with a “not seen” badge — so a documented-but-silent property surfaces as exactly the staleness the dictionary exists to catch.

​
Frequently asked questions

No. In the tinyanalytics data dictionary, verified is a label only. It doesn’t change what’s collected, hide or exclude anything from your reports, reorder the list, or alter any data. It records that a human on your team confirmed the name is the official, canonical one — plus who verified it and when.
No. There’s nothing to register. tinyanalytics never rejects a new name, and the dictionary reads the inventory directly from your data every time you open the page. It discovers custom event names, event properties, user traits, and group traits automatically.
A name you’ve described or verified keeps showing in the dictionary even after it stops appearing in new data, marked with a “not seen” badge. That’s the point: a documented-but-silent property surfaces as staleness you can act on.
Adding descriptions and marking names verified requires an owner or admin role. Anyone with access can browse the inventory, its inferred types, example values, volume, and first- and last-seen dates.

Track custom events

Where event names and properties come from.

Identify users

Where user traits come from.

Events explorer

Analyze the events the dictionary catalogs.

Filter your data

Filter reports by event and property.

Related topics

Export Analytics DataImport Simple Analytics DataMigrate Analytics Data to tinyanalytics