5 Data Governance Steps

Plan:

Kaliper allows you to create plans that consist of three components: KPIs, events to be tracked to measure those KPIs, and properties of those events (dimensions).

It facilitates collaboration between multiple stakeholders by having them contribute to the plan.

Multiple plans can be created and attached to various sources, such as a mobile app or website, where any violations or reports can be based on the components defined in the plan.

KPI:

Key Performance Indicators (KPIs) play a crucial role in measuring the success of your analytics objectives.

Every plan in Kaliper should include KPIs, as they serve as the foundation of the plan.

It’s important to have a clear and thorough description of each KPI, as this helps team members understand the purpose and logic behind the metric.

To ensure the most accurate and meaningful results, we recommend including associated events that outline the logic used to calculate the KPI.

By tracking and analyzing these essential metrics, you can better understand the performance of your plan and make informed decisions to drive success.

Best practices for defining KPIs

• Defining key performance indicators (KPIs) is an important process that involves collaboration between product owners, the marketing team, and C-level executives. By working together, you can develop a telemetry plan that helps you track the progress of your business objectives.
  
• To ensure that your KPIs are effective, it’s important to clearly define the expected outcomes for each one. This includes providing a detailed description of the KPI and how it ties back to events.
  
• Remember, a well-defined KPI should be specific, measurable, attainable, relevant, and time-bound. By adhering to these “SMART” criteria, you can ensure that your KPIs are meaningful and actionable, and that you have a clear understanding of what success looks like for your business.

Events:

Best practices for defining Events

Use clear and descriptive names:
Make sure your event names are easy to understand and descriptive.

Include enough context in your events:
Make sure your events include enough contextual information so that you’ll be able to identify what happened and why it happened.

Use meaningful dimensions:
Use dimensions (or attributes) to provide more information about a particular event. Use meaningful names for your dimensions to make it easier to find the events you’re looking for.

Make your events queryable:
Make sure your events are queryable so that you can easily analyze them.

Use the right event types:
Choose the right event types for your events. For example, you should use an error event type for any errors that occur.

Create an event taxonomy:
Create an event taxonomy to help you organize your events into logical groups so that it’s easier to analyze them.

Monitor your events:
Monitor your events to make sure they’re being logged properly and that the data is accurate.

Dimension:

Is nothing but properties of events, users or groups.

This is a very crucial component of planning and the data you collect. This is the premise for comparing data streamed and generating violations.

Best Practices for defining Dimensions:

Use meaningful names:
Dimension names should be descriptive and self-explanatory.

Avoid duplication of data:
Every dimension should be unique and should not contain any redundant data.

Make sure your dimensions are consistent:
If you are using a particular dimension across different events, make sure it has the same structure and values.

Utilize hierarchical dimensions:
This will allow you to create more useful and meaningful data.

Get feedback from stakeholders:
Ask your stakeholders what kind of data they would like to see in your events telemetry.

Use segmentation:
Segmented dimensions allow you to analyze data more easily and effectively.

Utilize custom dimensions:
Custom dimensions can help you store additional data that may not fit into the existing dimensions.