Overview

Composable Audience Studio (CAS) is a deployment mode of Treasure Data's CDP that enables you to build and manage audience segments directly on your Snowflake data warehouse without copying data into Treasure Data. Using Zero-Copy / Federated Query architecture, CAS queries your Snowflake tables in place, keeping data under your existing governance and access controls.

This guide walks through the end-to-end process of setting up a Composable Parent Segment on Snowflake, from connection configuration to segment creation.

1. Key pair authentication for secure Snowflake access
2. Zero-Copy configuration to connect Treasure Data to your Snowflake instance
3. Parent Segment configuration file defining your customer and behavior tables
4. API upload of the configuration to create the Parent Segment in CAS

Before you begin, ensure you have:

• A Treasure account with admin-level permissions
• A Snowflake account with:
  • A database and schema containing your customer and event data
  • A warehouse available for query execution
  • A user and role with SELECT permissions on the target tables
• OpenSSL installed on your local machine (for key pair generation)
• A Treasure API key (Master API key recommended)

Data never leaves your Snowflake environment. Treasure Data sends federated queries and receives results at query time.

A Composable Parent Segment is composed of a single Customers table and multiple Behaviors tables.

The Customers table stores unified profile data and attributes, with each record representing a single profile. A unique identifier column is required for each profile.

Contains all customer attributes (e.g., email, name, city, membership tier, LTV)
Each row = one unique customer profile Unique identifier column serves as the primary key

Behaviors tables contain activity records for specific actions taken by profiles (e.g., website visits, orders).
Each Behaviors table must include a unique ID column that links the activity record to the corresponding customer profile via the Unique identifier.

Each table represents a distinct type of activity (page views, purchases, etc.)
Multiple behavior records can exist per customer Must include a time column for temporal queries

The Parent Segment uses a data model comprising one Customers table and multiple Behaviors tables.

The Customers table is dedicated to storing unified profile data and attributes, with a unique record and required unique identifier column for each profile.

Behaviors tables record activity data for specific profile actions, such as website visits or orders. Each Behaviors table must contain a unique ID column that links the activity record to the corresponding profile in the Customers table, utilizing the same identifier column.

Customers Table

Each record represents a profile. Columns are attributes per profile.

Behaviors Tables

Email activity

Web pageviews

The Customers table's user_id column links to the user_id column in each Behaviors table, establishing the 1-to-many relationship.

The relationship between Customers and each Behaviors table is 1-to-many: one customer profile can have many behavior records.