The Custom Categories table stores user-defined campaign groupings (categories and subcategories) with their AI rules and provider scopes. One row per subcategory. Learn more about Custom Categories for Campaign Organization.

📋

Table Guide

What You Can Answer With This Table

• What categories and subcategories have I defined? — use category_name, sub_category_name
• Which subcategories use an AI rule, and what does the rule look like? — use ai_rule, sub_category_name
• What providers does each subcategory include or exclude? — use include_providers, exclude_providers, sub_category_name
• When were my subcategories created? — use created_at, group by category_name, sub_category_name

Before You Query

• This table is not time-series. No event_date filter is needed. Use created_at if you want to narrow to a creation-date range.
• Only active subcategories are returned. Inactive subcategories are excluded by the query layer and cannot be retrieved here.
• include_providers and exclude_providers are repeated-string arrays. Use arrayJoin (or the equivalent unnest pattern) to filter or aggregate by individual provider.

Key Relationships

Table	Join Key	What the Join Enables
Custom Category Mappings	sub_category_id	The campaigns currently assigned to each subcategory, with their channel and campaign metadata.

When to Use a Different Table

• For the actual campaigns assigned to each subcategory, or for performance metrics by category → use Custom Category Mappings. This table only defines categories and rules; Custom Category Mappings has the campaign assignments and joins to Ads for performance.

View the full Triple Whale Data Ontology →

Dimensions

Dimensions are immutable properties that can be used for grouping data.