# Grouped Metric Row-Limit Coverage

Show when a grouped time-series limit prevents an investor chart from being treated as a complete account total.

## Scope
Preparation and review only. No account action or professional decision.

## Inputs
Request metrics/granularity/groups/limit, returned buckets, Other grouping evidence, supplied total and date range.

## Workflow
1. Record the request scope and row limit exactly.
2. Count returned rows across dates and groups; do not read limit 5 as five accounts per date.
3. Keep Other, absent groups and zero-valued ungrouped buckets distinct according to source behavior.
4. Return coverage limitations and unreconciled totals; no omitted group is called zero or a top-five account ranking.

## Output contract
request_scope | limit | returned_rows | date_group_coverage | other_bucket | total_comparable | hold

## Fictional acceptance test
Fictional request spans 2 dates and has limit 5 total rows. It does not guarantee 5 accounts on each date. A missing group is not a zero account; supplied all-account total cannot be reconciled from truncated groups alone.

## Review gates
Keep original values, source IDs and version dates. Unknown facts stay held. Use qualified review for hiring, legal and accounting conclusions. No send, share, sign-in, scheduling, ledger change or payment. Fictional contract review is not a live account compatibility test.

## Method source
https://docs.stripe.com/data/analytics/supported-metrics

Checked October 9, 2026. Oct 9 live AIS Search Console through Oct 6: marketing Copilot 37 impressions, Planable/Claude 33, Planable/ChatGPT 23, campaign brief 12, investor agent 19. Social-review/reporting topics follow these parent-query leads. Other professions follow documented workflow needs, not measured exact search intent. Site impressions are not monthly volumes; exact topic volume is unmeasured.