# <!-- FILL: Partner Name --> Query Guide

> **Note**: Universal query standards (value discovery, SUM aggregation, catalog-first approach, date-range interpretation) are in the parent skill's `references/query-standards.md`. This file covers partner-specific query rules only.

## Required Filters

<!-- FILL: List the filters that MUST appear on every consumption/fact query for this partner.
For each filter, explain why it's required and what happens if it's omitted. -->

Every query against this partner's fact data MUST include:

1. **<!-- FILL: e.g., date column -->** — <!-- FILL: why required -->
2. **<!-- FILL: e.g., country/region column -->** — <!-- FILL: why required -->
3. **<!-- FILL: e.g., metric type column -->** — <!-- FILL: why required -->

## Sentinel / Special Values

<!-- FILL: Document any non-standard NULL representations, magic values, or sentinel strings.
Example: Some partners use a placeholder string (e.g., 'PARTNER_NULL') instead of SQL NULL. -->

## Metric-Specific Breakout Columns

<!-- FILL: If different metric types use different breakout/dimension columns, document which
columns apply to which metrics. This prevents misleading GROUP BY results. -->

## Cluster Keys for Performance

<!-- FILL: List cluster key columns for each major table. Analysts should filter on these
to get fast query performance. -->

| Table | Cluster Keys |
|-------|-------------|
| `<!-- FILL -->` | <!-- FILL: comma-separated column names --> |

## Discovering Valid Filter Values

<!-- FILL: Document any partner-specific shortcuts for discovering valid values
(e.g., a reference table that lists all valid metric categories and breakout values).
If no shortcut exists, analysts fall back to the universal two-step process in query-standards.md. -->