Configure data in Wondaris

You've successfully connected your external data to Wondaris. Now, let's get your data organised within Wondaris so you can start uncovering valuable insights.

Wondaris helps you make sense of your data by categorising it into three key types: Customer, Event, and Related data. You'll need to add your Customer table first, as it forms the foundation for everything else.

Here’s a simple guide to adding each type of table:

Open

Your Customer table is essential because it tells Wondaris who your customers are. All your other data will link back to these customer records.

Open

• Choose your data's home:

  • If you're using Snowflake: Select the Schema where your customer data table lives.

  • If you're using BigQuery: Select the Dataset where your customer data table lives.

  • This step is required.

• Pick your customer table: From the Schema or Dataset you just selected, choose the specific table that holds your customer information.

  • This step is required.

• Name your table: Give your customer table a clear, easy-to-understand name. This is how you'll see it listed in Wondaris. For example, My Main Customers or Website Users.

• Select a unique key: Choose a field from your customer table that has a unique value for each customer. Think of it like a unique ID card for each person. This is crucial for Wondaris to properly identify and link all your data. Common examples include customer_id or email_address.

  • This step is required.

• Describe your table (optional): Add a short description to remind yourself and your team what this table contains or why it's important.

Once your Customer table is set up, you can add Event tables. These tables track actions your customers take, like making a purchase, visiting a webpage, or signing up for a newsletter. You can add as many Event tables as you need!

Open

• Choose your data's home:

  • If you're using Snowflake: Select the Schema where your event data table lives.

  • If you're using BigQuery: Select the Dataset where your event data table lives.

  • This step is required.

• Pick your event table: From the Schema or Dataset, choose the specific table that contains your event information.

  • This step is required.

• Name your table: Give your event table a clear name, like Website Purchases or App Logins. This is how you'll see it listed in Wondaris.

• Select a unique key: Choose a field that uniquely identifies each individual event. For example, transaction_id for a purchase event.

  • This step is required.

• Describe your table (optional): Add a brief description if it helps clarify the table's purpose.

• Connect to your Customer Table: This is super important! You'll need to tell Wondaris how this event table relates to your Customer table. Find the field in your Event table that corresponds to the Unique Key you chose for your Customer table (e.g., if you used customer_id as the unique key in your Customer table, you'd select customer_id in your Event table too). This creates the link between the action and the customer who performed

Related Data tables allow you to bring in extra information that adds more context to your customer profiles. This could be anything from customer preferences to survey responses or data from other business tools. Just like Event tables, you can add multiple Related Data tables.

Open

• Choose your data's home:

  1. If you're using Snowflake: Select the Schema where your related data table lives.

  2. If you're using BigQuery: Select the Dataset where your related data table lives.

  3. This step is required.

• Pick your related data table: From the Schema or Dataset, choose the specific table that contains your related information.

  1. This step is required.

• Name your table: Give your related data table a clear name, such as Customer Preferences or Survey Responses. This is how you'll see it listed in Wondaris.

• Select a unique key: Choose a field that uniquely identifies each individual record within this table.

  1. This step is required.

• Describe your table (optional): Add a brief description if it helps.

• Connect to your Customer Table: Similar to event tables, you'll need to link this related data back to your customers. Select the field in your Related Data table that matches the Unique Key from your Customer table (e.g., customer_id). This ensures the extra details are tied to the right customer.