Segment Product Analytics dbt Package

📣 What does this dbt package do?

This package transforms your raw Segment event data into Houseware Event Schema, to make events, users and their properties available on Houseware.

Typically these Segment events arrive at your warehouse in different tables such as:

• TRACKS
• PAGES
• Individuals tables for your events, e.g. SIGNUP_SUCCESS, BUTTON_CLICKED etc

The output of using this package is a single long events table called allevents, which will be materialized in the target destination on your warehouse.

🎯 How do I use the dbt package?

We need to know the schema in which your Segment events are flowing in the target database. Please add the following configuration to your dbt_project.yml file:

# dbt_project.yml

...
config-version: 2

vars:
  segment_product_analytics:
    segment_schema: "DEFAULT_SEGMENT_SCHEMA" # replace this with the schema in which Segment events are flowing

🗄 Which warehouses are supported?

This package has been tested on Snowflake.

🙌 Can I contribute?

Additional contributions to this package are very welcome! Please create issues or open PRs against main. Check out this post on the best workflow for contributing to a package.

🏪 Are there any resources available?

• Have questions, feedback, or need help? Email us at nipun@houseware.io
• Check out Houseware's blog
• Learn more about dbt in the dbt docs
• Check out Discourse for commonly asked questions and answers
• Join the chat on Slack for live discussions and support
• Find dbt events near you
• Check out the dbt blog for the latest news on dbt's development and best practices