Analyze storefront pages

Pages groups normalized storefront paths so teams can compare product, collection, cart, checkout, and other page families without treating every URL variant as a separate product surface.

Start with page outcomes

Use traffic, entry and exit behavior, the bounce proxy, and funnel progression to find pages where the journey appears to weaken. A high exit rate is context, not automatically a defect: an order confirmation page and a product page have different expected outcomes.

Open a page group

A page detail combines:

• visits and journey transitions
• entry, exit, and bounce-proxy evidence
• issues observed on the page
• rage-click, dead-click candidate, repeated-submit, form-exit, and navigation-loop signals
• LCP, INP, and CLS distributions
• affected anonymous sessions

Breakdowns by browser, device, operating system, and viewport help distinguish a broad page problem from a concentrated environment segment. Use relative lift only when a comparable baseline exists.

Move into Issues for a grouped failure or Performance for a Core Web Vital investigation.