⌕◔
Atlas HydrationUnited States
Structured shellPERF-006
Page guide
Catalog Change Impact

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

Home/Performance/Catalog Change Impact
PERF-006 · AnalyticsPageTemplate

Catalog Change Impact

Evaluate before/after and controlled comparisons for listing copy, images, A+, pricing context, or other catalog changes.

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
change selector

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

2
comparison windows

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

3
confounders

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

4
CTR/CVR/sales

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

5
confidence

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

6
conclusion

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
product, metric_observation, impact_analysis
Screen states
insufficient datadirectionalmoderate confidencehigh confidence

Primary actions

Open ArtifactidOpen Recommendations

Navigation and exits

DIR-014
AI RecommendationsReview explainable AI recommendations, evidence, impact, readiness, priority, and affected scope before adding work to the roadmap.
->WS-124
Change Impact ReviewShow downstream artifacts, executions, live assets, and performance analyses affected by a proposed or approved change.
->

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.