As your product and team grows and changes over time, so too will your Heap dataset. Our data governance tools allow you to ensure your dataset will continue to be reliable and trustworthy, regardless of how many definitions and team members you have using Heap.
“Get started with good data governance practices/processes from day 1, even if you are the only person using Heap at first. If you wait till you are 5 years in, it’ll already be messy.”
Alex Wimbush, Head of Product at Sendwave
Event Repair Flow
Analysts, Architects, and Admins can review a list of inactive events and quickly fix them from the event details page. Inactive events are ones which have failed to collect data for more than the past 72 hours. Events can become inactive due to site or app changes underneath Heap, or if an Admin or Architect changes an event definition in error.
It’s important to have a review and management process in place for identifying and fixing inactive events. Answer the following question and include this information in your rollout documentation:
How often will team leads go through the account to review and update inactive events?
See the Event Repair Flow section of the Data Governance guide for complete details on how to repair events.
Admin and Architects have the ability to verify events, segments, and reports in the shared space.
Verification increases data trust because something that’s been verified can only be modified by other Admins and Architects. It also lets other team members know it’s been reviewed and validated by someone with intimate knowledge of Heap and your business.
Write down your answers to the following questions to determine how your team will use this feature:
What events should be verified? (Pick one):
- All events in the shared space should be verified
- Only select events need to be verified (e.g. Mission-critical or high-value events that are core to your analytics strategy)
- No events need to be verified (since this is the most likely area of the UI to get messy, we do not recommend this approach unless you have an extremely small team)
Note: A criteria in Heap’s standing definition of a model account is one where 90% of shared saved reports use only verified events.
What segments should be verified? (Pick one):
- All segments in the shared space should be verified
- Only select segments need to be verified (e.g. Mission-critical or high-value segments)
- No segments need to be verified
What reports should be verified? (Pick one):
- All reports in the shared space should be verified
- Only select reports need to be verified (e.g. any mission-critical or quarterly reporting such as “# of Purchases” )
- No reports need to be verified
How often will Admins/Architects go through the account to verify data? (ex. every 1 or 2 weeks)
We also recommend including this checklist in your documentation:
Before verifying something, an Admin or Architect needs to make sure it is:
- Categorized correctly
- Named appropriately
- Defined correctly
- Has notes attached telling other users what this data means (if not obvious already from name/category)
- <Any other steps that are relevant to your organization>
See the Definition Verification section of the Data Governance guide for complete details on how definition verification works.