Data management
Keep the events and properties your project receives tidy and understandable — definitions, property types, verification, history and ingestion warnings.
As your tracking grows, so does the list of events and properties your team has to choose from. Data management is where you keep that list understandable: what each event means, which ones to trust, and which to hide.
Open it from the sidebar's Data menu, for example through Event definitions. It has these tabs:
| Tab | What it holds |
|---|---|
| Event definitions | Every event name your project has received. |
| Actions | Your actions. |
| Properties | Every event and person property your project has received. |
| History | Changes your team made to definitions. |
| Event ingestion warnings | Problems found as events arrived. |
Event definitions
An event definition is created automatically the first time an event name arrives. Open one to see how recently it was seen, its properties, and a sample of matching events.
On plans that include Verified events and properties, you can also add:
- a description of what the event means and when it is sent;
- tags, to group related events;
- a status: Verified marks events your team trusts, Hidden removes an event from filters and pickers without deleting any data, and Visible is the default.
Verified and described events are easier to find in the event picker, which helps everyone build insights on the right data.
Property definitions
Property definitions work the same way, for the properties on your events and persons.
Each property has a property type: String, Numeric, Boolean or DateTime. The type is guessed from the first values received, and decides which filter operators are offered. If a property was guessed wrongly, for example a number sent as text, open its definition and correct the Property Type.
History
The History tab lists changes your team made in the app, such as new descriptions, tags or statuses. Definitions created automatically by incoming events are not listed.
Ingestion warnings
The Event ingestion warnings tab lists events from the last 30 days that were changed or dropped as they arrived, grouped by the kind of problem, with examples. See Event ingestion warnings for what each warning means and how to fix it.
Keep your data tidy
- Agree on a naming style before you add custom events, and describe each one when it first appears.
- Hide test or retired events instead of leaving them in everyone's way.
- Mark the events your key reports depend on as Verified.
- Use annotations to record tracking changes, such as a renamed event.
- Use Filter out internal and test users, in Settings → Project → Customization, so your own team's visits do not skew your numbers.
Related
Can't find what you need? Contact support