Skip to main content

Quick Start with Mitzu

Let's get started with Mitzu. On this page we will help you to setup your first workspace and connect your data.

4.1 Create a new organization​

First create a new organization in Mitzu and then go to the workspace settings page.

image

4.2 Connect your data warehouse to Mitzu​

Then head to the workspace settings page (top right corner) and click on the Connection settings tab.

image
info

Throughout this example we will use BigQuery as a data warehouse. Currently, Mitzu supports 8 data warehouse solutions:

  • Snowflake
  • BigQuery
  • DataBricks
  • Redshift
  • AWS Athena
  • Clickhouse
  • Postgres
  • Trino / Starburst
image

4.3 Add tables to your workspace​

Add event tables on the Event tables tab.

info

Event tables are regular tables in BigQuery (or in any data warehouse). The only requirement is to have some kind of userID and event time columns. Optionally, they can have an event name field.

Event tables are the basis of Mitzu's event catalog. Based on the event tables you define, you can uncover new insights from your data with SQL knowledge.

This is an example of how your event tables should look like:

image
  1. Click on the Add tables button. And add the four tables above.
  2. Select the four tables you just added in the main table.
  3. Click Configure tables.
  4. Choose anonymous_id as the user id field for the pages table. id for the stripe_customers table. And customer for the other stripe tables.
  5. Choose timestamp as the event time field for the pages table and created for the other stripe tables.
  6. Click Configure
image

Once you have completed the configuration, click the Save and update event catalog button.

success

Congratulations! You have successfully configured Mitzu to work with your data warehouse.

Step 5. Create your first insight​

When you click on the Select an event button on the insights page, you should be able to see four events. Choose the Pages event.

image
success

Congratulations! You have just created your first insight. Number of unique website visitors to website.

This is just the beginning. By moving all your data to Mitzu, you will be able to uncover insights that would be impossible otherwise.

Event tables for product analytics​

Your application should track events that are ultimately stored in your data warehouse. These events should be stored either as separate tables or as a single table.

  • In case of separate tables, Mitzu will automatically discover the events' names from the table names.
  • In case of a one big table, please provide the Event name column in the workspace settings page.
note

More on this subject in the event tables section.

Event tables for marketing analytics​

Your landing page should track events that are ultimately stored in your data warehouse. The setup is similar to the one for product analytics.

info

Mitzu unifies marketing, product and revenue analytics in a single platform. This means that you should be able to analyze the entire user life cycle in one place. From the first landing page visit to the last user interaction in your application.

The key to this challenge is the user ID unification. You can learn about this here.

More content on this subject is coming soon.