Configuration sheet: schema

This page is a reference spec for the SourceMedium Configuration Sheet: what columns exist on each tab, which fields are required, and how dates/ranges are interpreted during ingestion.

SourceMedium checks your Configuration Sheet every 15 minutes, and your store page shows what it read from each tab, including any cell it couldn’t read. Reports use your edits from their next refresh. See Check what SourceMedium read.

General rules

Layout

Each tab keeps the template’s layout: row 2 holds the column headers and your data starts on row 3. Columns are read by position, in the order listed below, so don’t insert, remove or reorder columns. Keep each tab’s name as the template has it (capitalization doesn’t matter).

Date formats

Every tab accepts dates in these formats:

YYYY-MM-DD
MM-DD-YYYY
MM/DD/YYYY
MM/DD/YY

Cells SourceMedium can’t read

A number column with text in it, a date in another format, or a formula that shows an error such as #REF! or #N/A holds back the whole tab: reports keep using the version they used before, and your store page names each cell to fix.

Date ranges

Where a tab supports a date range, date_end is treated as inclusive (the range includes both date_start and date_end).
For tabs that amortize/spread amounts, the spread is done evenly across the number of days in the inclusive range.

Targets tab

Use the Targets tab for KPI targets displayed in scorecards and executive reporting.

Targets are treated as daily values across the selected date range. If you want a monthly total target, enter the per-day target value.

If multiple Target rows overlap on the same day for the same channel:

Summable metrics (e.g., revenue, orders, spend, sessions) are summed
Ratio-like metrics (e.g., AOV, CPA, ROAS) use the max value for that day

Column	Type	Required	Notes
`channel`	STRING	Yes	Targets are keyed by channel.
`date_start`	STRING	Yes	Parsed into a date.
`date_end`	STRING	No	If provided, targets apply to each day in the inclusive range.
`gross_revenue`	FLOAT64	No	Target value (per day if using a range).
`net_revenue`	FLOAT64	No	Target value (per day if using a range).
`total_revenue`	FLOAT64	No	Target value (per day if using a range).
`orders`	FLOAT64	No	Target value (per day if using a range).
`spend`	FLOAT64	No	Target value (per day if using a range).
`sessions`	FLOAT64	No	Target value (per day if using a range).
`aov`	FLOAT64	No	Ratio/derived KPI targets are applied as a constant value across the range.
`cpa`	FLOAT64	No	Ratio/derived KPI targets are applied as a constant value across the range.
`cpo`	FLOAT64	No	Ratio/derived KPI targets are applied as a constant value across the range.
`conversion_rate`	FLOAT64	No	Ratio/derived KPI targets are applied as a constant value across the range.
`roas`	FLOAT64	No	Ratio/derived KPI targets are applied as a constant value across the range.
`primary_product_units`	NUMERIC	No	Optional (brand-dependent).

Channel Mapping tab

Use Channel Mapping to route orders (and some marketing records) into consistent channels, subchannels, and vendors using rule-based matching.

Column	Type	Required	Notes
`row`	INT64	Yes	Rule priority, used to derive the rule’s weight (see below). `0` disables a rule only when `channel` is blank or an `Online DTC` channel.
`attribute`	STRING	Yes	Which input field to match against.
`operator`	STRING	Yes	One of: `equals`, `contains`, `in` (must match exactly).
`value`	STRING	Yes	Match value (comparison is case-insensitive). For `in`, use a comma-separated list (whitespace is ignored).
`channel`	STRING	No	Optional output channel when matched.
`sub_channel`	STRING	No	Optional output subchannel when matched.
`vendor`	STRING	No	Optional output vendor when matched.
`cost_per_order`	FLOAT64	No	Optional CPO value associated with the matched rule.

Rules are evaluated from highest to lowest derived weight, and the comparison spans every channel:

When channel is blank or an Online DTC channel, the weight is row. A row of 0 disables the rule.
For any other channel, the weight is row * 1000. A row of 0 gives the lowest weight, and the rule stays active.

For example, row 2 with channel Wholesale (weight 2,000) is evaluated before row 500 with channel Online DTC, and after row 2,500 with channel Online DTC.

Only Online DTC, Amazon, Retail, Wholesale, and TikTok Shop count as valid channels. Orders in any other channel are not valid orders, so they are left out of standard reporting and LTV, but they stay in your order data.

Built-in rules run before Channel Mapping, so a rule with channel Excluded does not move an order that a built-in rule already placed, such as a POS order in Retail. The sm-exclude-order order tag is the only route that always applies. See Create custom channel mappings.

Supported `attribute` values

These attributes are supported by the channel mapping ingestion logic:

source (UTM source)
medium (UTM medium)
source_medium (combined UTM source/medium)
campaign (UTM campaign)
discount_codes (order discount codes)
order_tags (order tags)
skus (product SKUs)
shopify_sales_channel (Shopify sales channel / marketplace signal)

Sales tab

Use the Sales tab to enter non-integrated sales and have them included in reporting.

Column	Type	Required	Notes
`channel`	STRING	Yes	Sales channel bucket for the entry.
`sub_channel`	STRING	No	Optional label for internal organization.
`date_start`	STRING	Yes	Parsed into a date.
`date_end`	STRING	No	If provided, amounts are spread evenly across the inclusive range.
`gross_revenue`	FLOAT64	No	Total for the period (spread evenly if `date_end` provided).
`net_revenue`	FLOAT64	No	Total for the period (spread evenly if `date_end` provided).
`orders`	FLOAT64	No	Total for the period (spread evenly if `date_end` provided).
`primary_product_units`	NUMERIC	No	Optional (brand-dependent).
`discounts`	FLOAT64	No	Total for the period (spread evenly if `date_end` provided).
`refunds`	FLOAT64	No	Total for the period (spread evenly if `date_end` provided).

Orders are stored as whole numbers; when a Sales row spans multiple days, order counts are distributed across the range to stay integer-valued.

Cost tab (Marketing Costs)

Use the Cost tab (sometimes labeled Marketing Costs) for marketing spend that isn’t captured by an integration.

Column	Type	Required	Notes
`category`	STRING	Yes	Used to categorize spend (commonly `Marketing`).
`channel`	STRING	Yes	Channel where you want reporting to reflect spend.
`sub_channel`	STRING	No	Optional subchannel.
`vendor`	STRING	No	Optional platform/vendor.
`cost`	FLOAT64	Yes	Total cost for the period.
`date_start`	STRING	Yes	Parsed into a date.
`date_end`	STRING	No	If provided, cost is spread evenly across the inclusive range.

Financial Cost tabs

Financial Cost tabs define rates used for profit and cost reporting. These tabs require date_start and date_end, in any of the date formats above.

For Financial Cost tabs, rows without a date_end are ignored.

Financial Cost - Product COGS

Column	Type	Required	Notes
`category`	STRING	Yes	Typically `Financial`.
`channel`	STRING	Yes	Channel the cost applies to.
`expense_channel`	STRING	Yes	Typically `Product COGS`.
`sku`	STRING	Yes	SKU/variant identifier the cost applies to.
`fixed_cost`	FLOAT64	Yes	Per-unit product cost for the SKU.
`date_start`	STRING	Yes	A date.
`date_end`	STRING	Yes	A date.

Financial Cost - Shipping

Column	Type	Required	Notes
`category`	STRING	Yes	Typically `Financial`.
`channel`	STRING	Yes	Channel the cost applies to.
`expense_channel`	STRING	Yes	Typically `Shipping Cost`.
`region`	STRING	Yes	Region bucket used for allocation.
`cost`	FLOAT64	Yes	Per-order shipping cost for the period.
`date_start`	STRING	Yes	A date.
`date_end`	STRING	Yes	A date.

Financial Cost - Fulfillment

Column	Type	Required	Notes
`category`	STRING	Yes	Typically `Financial`.
`channel`	STRING	Yes	Channel the cost applies to.
`expense_channel`	STRING	Yes	Typically `Fulfillment Cost`.
`region`	STRING	Yes	Region bucket used for allocation.
`cost`	FLOAT64	Yes	Per-order fulfillment cost for the period.
`date_start`	STRING	Yes	A date.
`date_end`	STRING	Yes	A date.

Financial Cost - Merchant Processing Fees

Column	Type	Required	Notes
`category`	STRING	Yes	Typically `Financial`.
`channel`	STRING	Yes	Channel the cost applies to.
`expense_channel`	STRING	Yes	Typically `Merchant Processing Fees`.
`region`	STRING	Yes	Region bucket used for allocation.
`vendor`	STRING	Yes	Payment processor/platform label.
`fixed_cost`	FLOAT64	Yes	Fixed per-order fee.
`variable_cost`	FLOAT64	Yes	Variable rate (used as a rate downstream).
`date_start`	STRING	Yes	A date.
`date_end`	STRING	Yes	A date.

Financial Cost - Operating Expenses

Column	Type	Required	Notes
`category`	STRING	Yes	Typically `Financial`.
`channel`	STRING	Yes	Channel the cost applies to.
`expense_channel`	STRING	Yes	Typically `Operating Expenses`.
`region`	STRING	Yes	Region bucket used for allocation.
`cost`	FLOAT64	Yes	Total operating expenses amount for the period.
`date_start`	STRING	Yes	A date.
`date_end`	STRING	Yes	A date.

Configuration Sheet Overview

Start here for how-to guides and workflows.

How does channel mapping work?

Standard channel labels, Shopify Flow tagging, and how to customize the rules.

Integrations

Ecommerce & Subscription

Marketing & Advertising

Email & SMS

Customer Success & Operations

Analytics & Measurement

Finance

Data Infrastructure