Data Onboarding
- AutoDocs
- / Use Cases
Onboarding Just Got Easier
Onboarding analysts or data engineers, anyone who regularly works with your company's data can be a painful process.
With Events Explorer, you have an always available resource to answer questions about the data entering your system.
Stop wasting time on exploratory queries.
Events Explorer
The Data Dictionary You've Always Wanted
No Maintenance, Always Updated.
Searchable
Search through events by name, properties and even top-values. Figuring out “Which event sends the CPU property?” or “Where can I get a friend_id from?” has never been easier.
Sampling
We’ll keep a sample of the most frequent values observed for each property, allowing you to dive into exactly what’s being sent. For numerical values, you’ll see this as a distribution as well.
Timelines
Analytics data is not set in stone, so in addition to Version Detail you’ll be able to look over time for how events and properties have evolved.
Collaboration coming soon
With annotations, you can leave messages for other users in your organization. Document how an event is fired, or where it is used, or why it is broken 😬.
How do I define an "event"?
You can define an event by providing up to 3 properties that go into an event definition. Read more in the docs
If I accidentally send PII, can it be removed from AutoDocs samples?
Yes! Security and privacy is of the upmost importance. Review the docs on how to do this.
Are there limits to the number of events or versions?
There are. In order to safegaurd the system (for example, if you define a user_id field as an event descriptor) - any config that has more than 250 unique events or 200 unique versions will be disabled. These are flexible limits, if you have a need for more events/versions, please contact us.
How deeply nested does AutoDocs scan?
By default, events will be explored up to 10 levels deep, including nested arrays. This is a flexible limit, please contact us if you need this limit increased.