⌕◔
Atlas HydrationUnited States
Structured shellPERF-009
Page guide
Store Traffic Routing

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

Home/Performance/Store Traffic Routing
PERF-009 · AnalyticsPageTemplate

Store Traffic Routing

Understand how traffic enters the Store and moves through pages to product detail pages and purchases.

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
flow diagram

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

2
entry pages

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

3
drop-off

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

4
PDP clicks

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

5
campaign source

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

6
page sequence

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, source_material
Screen states
completepartialunknown source

Primary actions

Open PageidOpen Recommendations

Navigation and exits

DIR-014
AI RecommendationsReview explainable AI recommendations, evidence, impact, readiness, priority, and affected scope before adding work to the roadmap.
->PERF-008
Store Page PerformanceAnalyze one Store page, its creative version, visitors, dwell, product routing, orders, and campaign traffic.
->

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.