Atlas HydrationUnited States
Structured shellPERF-012
Page guide
Sponsored Brands Static Performance

Did the change improve CTR, CVR, revenue, ROAS, or new-to-brand performance? Which result is directly measured, associated, correlated, or inferred?

Structured review shell
This route is intentionally visible before detailed implementation.

Review the intended hierarchy, information regions, actions, states, and navigation. Use Review Mode to identify what must be added or changed before this screen is promoted to deep implementation.

Intended screen regions

Derived from the page implementation registry

1
CTR/CPC/CVR/ROAS/NTB

Review whether this region belongs on the page, where it should appear, and what decisions it must support.

2
headline comparison

Review whether this region belongs on the page, where it should appear, and what decisions it must support.

3
image comparison

Review whether this region belongs on the page, where it should appear, and what decisions it must support.

4
product selection

Review whether this region belongs on the page, where it should appear, and what decisions it must support.

5
destination

Review whether this region belongs on the page, where it should appear, and what decisions it must support.

6
placement

Review whether this region belongs on the page, where it should appear, and what decisions it must support.

Governed component composition

PageHeaderSearchFieldTabsDataTablePaginationBulkActionBarVersionTimelineTrendStatChartFramePerformanceAttributionCard

Expected data

Primary endpoint
/v1/performance/summary
Primary entities
brand, product, metric_observation
Screen states
custom imageproduct collectionwinningfatigued

Primary actions

Navigation and exits

Acceptance criteria

  1. Renders only after required context and permissions resolve.
  2. Supports declared loading, empty, blocked, error, and stale-data states without layout shift.
  3. All governed actions expose reason, target object, resulting state, and undo/recovery path where allowed.
  4. Keyboard focus order follows visual reading order and all overlays restore focus to their invoker.
  5. Route is deep-linkable and browser back returns to the prior scoped view without losing safe local filters.