The Affluencer Hub table contains Triple-Whale-managed affluencer (influencer/affiliate) profiles with discount codes, expense configurations, and tracking links. One row per active affluencer profile; querying spend expands rows to per-day.

📋
Table Guide
What You Can Answer With This Table

What is each affluencer costing me, and how is that trending over time? — use spend, name, group by event_date, name

Which affluencers are driving the most spend? — use spend, group by name

What discount codes are active right now, and to whom do they belong? — use discount_codes.code, discount_codes.start_date, discount_codes.end_date, name

What are my expense commitments by type and cadence? — use expenses.spend_type, expenses.amount_type, expenses.recurring_cadence, expenses.amount

Which tracking links are tied to which campaigns and traffic sources? — use links.url, links.campaign, links.source, name

Before You Query

Required field: event_date

spend is calculated dynamically per row, not stored. Per-order expenses (expenses.spend_type = 'per_order') are computed from Triple Attribution-attributed pixel orders matched to the affluencer by name. Fixed/recurring expenses (expenses.spend_type = 'fixed') are prorated across each expense's active date range using expenses.recurring_cadence and expenses.recurring_interval_length.

Each expenses line item has its own start_date / end_date. Only line items active on the row's event_date contribute to that day's spend.

When to Use a Different Table

For third-party affiliate-platform performance (e.g., Rakuten, Awin, Impact, ShareASale, Pepperjam) → use Affiliates. Affluencer Hub covers profiles, codes, expenses, and links configured directly in Triple Whale; Affiliates covers integrations with external affiliate networks.

For order-level Pixel-attributed transactions from affluencer-driven traffic → use Pixel Orders and filter by source = 'influencers'.

For ad-and-attribution-joined performance from affluencer-driven traffic → use Pixel Joined and filter by channel = 'influencers'. Affluencer Hub carries affluencer configuration and computed cost; the pixel tables carry the attributed transactions.

View the full Triple Whale Data Ontology →

Dimensions

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

Title	ID	Type	Description
Event Date	`event_date`	date	The date the order was placed. Based on the shop time zone at the moment of the event (or user time zone when no sales platform is connected).
Event Day	`event_date.day`	date	The day on which the event occurred. Derived from `event_date`.
Event Week	`event_date.week`	date	The Sunday of the week during which the event occurred. Derived from `event_date`.
Event Month	`event_date.month`	date	The month during which the event occurred. Derived from `event_date`.
Event Quarter	`event_date.quarter`	date	The first month of the quarter during which the event occurred. Derived from `event_date`.
Event Year	`event_date.year`	date	The year during which the event occurred. Derived from `event_date`.
Affluencer Source	`affluencer_source`	string	How the affluencer profile was created. Example values: `upload`, `client`, `auto_create`, `backfill`
Discount Codes	`discount_codes`	record repeated	A list of the discount codes associated with the affluencer.
Discount Code	`discount_codes.code`	string	The actual code used to attribute orders to the affluencer. Example values: `JEN20`, `UMICH`, `ARKNUTRITION`
Discount Code Start Date	`discount_codes.start_date`	date	The start date the discount code is valid. Example value: `2024-08-02 00:00:00`
Discount Code End Date	`discount_codes.end_date`	date	The end date the discount code is valid. Example value: `2025-08-02 00:00:00`
Expenses	`expenses`	record repeated	A list of expense records assigned to the affluencer.
Expense ID	`expenses.id`	string	A unique identifier for the expense. Example value: `37f1ad60-2ce9-4733-b6d9-4b3d13307e42`
Expense Type	`expenses.spend_type`	string	Indicates the category of the expense. Example values: `per_order`, `fixed`
Expense Amount Type	`expenses.amount_type`	string	Indicates whether the expense is a percentage of sales or a fixed amount (currency). Example values: `percentage`, `currency`
Expense Is Recurring	`expenses.is_recurring`	boolean	Indicates whether this expense recurs on a regular cadence (e.g. monthly) or is a one-time expense. Possible values: `true`, `false`
Expense Recurring Cadence	`expenses.recurring_cadence`	string	Frequency of the recurring expense. Example values: `one_time`, `week`, `month`
Expense Start Date	`expenses.start_date`	date	The date the expense starts. Example value: `2023-07-22`
Expense End Date	`expenses.end_date`	date	The date the expense ends (if applicable). Example value: `2025-01-01`
Expense Amount	`expenses.amount`	numeric	The value of the expense.
Expense Recurring Interval Length	`expenses.recurring_interval_length`	numeric	Number of intervals between each recurring payment. For example, if `recurring_cadence = week` and `recurring_interval_length = 2`, the expense recurs every two weeks.
Affluencer Links	`links`	record repeated	A list of destination URLs tied to the affluencer, used for traffic and attribution.
Link ID	`links.id`	string	Unique identifier for the link, formatted: `${name}${links.campaign}${links.source}`
Link Campaign	`links.campaign`	string	The name of the campaign the link is associated with (e.g. `summer-launch`, `holiday-sale`).
Link Source	`links.source`	string	The traffic source where this link is shared. Example values: `instagram`, `default`
Link Storefront URL	`links.storefront_url`	string	The public-facing URL the affluencer is promoting Example value: `https://www.instagram.com/example`
Link URL	`links.url`	string	The fully generated tracking URL that includes affluencer and link identifiers. Example value: `https://www.instagram.com/example?linkId=example_instagram&affluencerId=example`
Affluencer Name	`name`	string	The name of the affluencer. Example value: `Jane Smith`
Spend	`spend`	string	The total amount of expenses.