{"templateId":"markdown","sharedDataIds":{"sidebar":"sidebar-sidebars.yaml"},"props":{"metadata":{"markdoc":{"tagList":[]},"type":"markdown"},"seo":{"title":"Composable Audience Studio for Databricks","description":"Set up Composable Audience Studio on Databricks using Zero-Copy federated queries to build audience segments without copying data.","siteUrl":"https://docs.treasuredata.com","lang":"en-US","llmstxt":{"hide":false,"sections":[{"title":"Table of contents","includeFiles":["**/*"],"excludeFiles":[]}],"excludeFiles":[]}},"dynamicMarkdocComponents":[],"compilationErrors":[],"ast":{"$$mdtype":"Tag","name":"article","attributes":{},"children":[{"$$mdtype":"Tag","name":"Heading","attributes":{"level":1,"id":"overview","__idx":0},"children":["Overview"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["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 Databricks data warehouse without copying data into Treasure Data. Using Zero-Copy / Federated Query architecture, CAS queries your Databricks tables in place, keeping data under your existing governance and access controls."]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["This guide walks through the end-to-end process of setting up a Composable Parent Segment on Databricks, from connection configuration to segment creation."]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":2,"id":"what-you-will-set-up","__idx":1},"children":["What You Will Set Up"]},{"$$mdtype":"Tag","name":"ol","attributes":{},"children":[{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Service principal and PAT authentication for secure Databricks access"]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Databricks authentication configuration to connect Treasure Data to your Databricks workspace"]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Parent Segment configuration file defining your customer and behavior tables"]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["API upload of the configuration to create the Parent Segment in CAS"]}]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":2,"id":"prerequisites","__idx":2},"children":["Prerequisites"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Before you begin, ensure you have:"]},{"$$mdtype":"Tag","name":"ul","attributes":{},"children":[{"$$mdtype":"Tag","name":"li","attributes":{},"children":["A Treasure account with admin-level permissions"]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["A Databricks workspace with:",{"$$mdtype":"Tag","name":"ul","attributes":{},"children":[{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Unity Catalog enabled with a catalog, schema, and tables containing your customer and event data"]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["A SQL warehouse or compute cluster available for query execution"]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["A service principal with appropriate permissions on the target catalog/schema/tables"]}]}]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["A Treasure API key (Master API key recommended)"]}]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":2,"id":"architecture","__idx":3},"children":["Architecture"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["Data never leaves your Databricks environment. Treasure Data sends federated queries and receives results at query time."]},{"$$mdtype":"Tag","name":"Diagram","attributes":{"data-language":"mermaid","diagramType":"mermaid","diagramSource":"graph LR\n subgraph TD[\"Treasure Data\"]\n CAS[\"Composable Audience Studio - Segment Builder - Activation - Insights\"]\n end\n\n subgraph DB[\"Your Databricks Workspace\"]\n CT[\"Your Table (profiles + attributes)\"]\n BT1[\"Behaviors Table 1\"]\n BT2[\"Behaviors Table 2\"]\n BTN[\"Behaviors Table N ...\"]\n end\n\n CAS <-->|\"Zero Copy / Query\"| CT\n CAS <-->|\"Zero Copy / Query\"| BT1\n CAS <-->|\"Zero Copy / Query\"| BT2\n CAS <-->|\"Zero Copy / Query\"| BTN\n","diagramHtml":"","diagramHtmlDark":""},"children":["graph LR\n subgraph TD[\"Treasure Data\"]\n CAS[\"Composable Audience Studio - Segment Builder - Activation - Insights\"]\n end\n\n subgraph DB[\"Your Databricks Workspace\"]\n CT[\"Your Table (profiles + attributes)\"]\n BT1[\"Behaviors Table 1\"]\n BT2[\"Behaviors Table 2\"]\n BTN[\"Behaviors Table N ...\"]\n end\n\n CAS <-->|\"Zero Copy / Query\"| CT\n CAS <-->|\"Zero Copy / Query\"| BT1\n CAS <-->|\"Zero Copy / Query\"| BT2\n CAS <-->|\"Zero Copy / Query\"| BTN\n"]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":2,"id":"parent-segment-data-model","__idx":4},"children":["Parent Segment Data Model"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["A Composable Parent Segment is composed of a single Customers table and multiple Behaviors tables."]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":3,"id":"customers-table","__idx":5},"children":["Customers Table"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["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."]},{"$$mdtype":"Tag","name":"ul","attributes":{},"children":[{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Contains all customer attributes (e.g., email, name, city, membership tier, LTV)"]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Each row = one unique customer profile"]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Unique identifier column serves as the primary key"]}]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":3,"id":"behaviors-tables","__idx":6},"children":["Behaviors Tables"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["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."]},{"$$mdtype":"Tag","name":"ul","attributes":{},"children":[{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Each table represents a distinct type of activity (page views, purchases, etc.)"]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Multiple behavior records can exist per customer"]},{"$$mdtype":"Tag","name":"li","attributes":{},"children":["Must include a time column for temporal queries"]}]},{"$$mdtype":"Tag","name":"Heading","attributes":{"level":3,"id":"composable-parent-segment-data-model","__idx":7},"children":["Composable Parent Segment Data Model"]},{"$$mdtype":"Tag","name":"Diagram","attributes":{"data-language":"mermaid","diagramType":"mermaid","diagramSource":"erDiagram\n Customers ||--o{ \"Behaviors Table 1\" : \"1 to many\"\n Customers ||--o{ \"Behaviors Table 2\" : \"1 to many\"\n Customers ||--o{ \"Behaviors Table 3\" : \"1 to many\"\n\n Customers {\n string unique_id PK\n string email\n string name\n string city\n string membership_tier\n float ltv\n }\n\n \"Behaviors Table 1\" {\n string unique_id FK\n timestamp time\n string action\n }\n\n \"Behaviors Table 2\" {\n string unique_id FK\n timestamp time\n string action\n }\n\n \"Behaviors Table 3\" {\n string unique_id FK\n timestamp time\n string action\n }\n","diagramHtml":"","diagramHtmlDark":""},"children":["erDiagram\n Customers ||--o{ \"Behaviors Table 1\" : \"1 to many\"\n Customers ||--o{ \"Behaviors Table 2\" : \"1 to many\"\n Customers ||--o{ \"Behaviors Table 3\" : \"1 to many\"\n\n Customers {\n string unique_id PK\n string email\n string name\n string city\n string membership_tier\n float ltv\n }\n\n \"Behaviors Table 1\" {\n string unique_id FK\n timestamp time\n string action\n }\n\n \"Behaviors Table 2\" {\n string unique_id FK\n timestamp time\n string action\n }\n\n \"Behaviors Table 3\" {\n string unique_id FK\n timestamp time\n string action\n }\n"]},{"$$mdtype":"Tag","name":"p","attributes":{},"children":["The relationship between Customers and each Behaviors table is 1-to-many: one customer profile can have many behavior records."]}]},"headings":[{"value":"Overview","id":"overview","depth":1},{"value":"What You Will Set Up","id":"what-you-will-set-up","depth":2},{"value":"Prerequisites","id":"prerequisites","depth":2},{"value":"Architecture","id":"architecture","depth":2},{"value":"Parent Segment Data Model","id":"parent-segment-data-model","depth":2},{"value":"Customers Table","id":"customers-table","depth":3},{"value":"Behaviors Tables","id":"behaviors-tables","depth":3},{"value":"Composable Parent Segment Data Model","id":"composable-parent-segment-data-model","depth":3}],"frontmatter":{"seo":{"title":"Composable Audience Studio for Databricks","description":"Set up Composable Audience Studio on Databricks using Zero-Copy federated queries to build audience segments without copying data."}},"lastModified":"2026-06-01T09:09:59.000Z","pagePropGetterError":{"message":"","name":""}},"slug":"/products/customer-data-platform/composable-cdp/databricks","userData":{"isAuthenticated":false,"teams":["anonymous"]},"isPublic":true}