Compare landing-page candidates
Use this evidence-collection procedure for the selected landing-page opportunity Check (experience.cross-surface.landing-page-opportunities). That Check owns applicability, required evidence, steps, decisions and output. The integration reference owns source binding and windows; the funnel procedure owns shared measurement-integrity and path-investigation steps.
Reuse compatible supplied landing evidence from $report-shopify-funnel when available. Do not require or rerun that report, import its catalog, or expand an authoritative selection.
- Use either Shopify or GA4 when it supplies compatible landing-session outcomes. Traffic alone supplies reach, not underperformance. Retain query/report provenance, row coverage, eligible sessions, counts, rates, source timezone and complete current/comparison windows.
- Normalize actual hostnames, redirects and routes. Remove tracking/private query values while preserving functional market, locale or variant distinctions. Keep unknown routes separate and never sum overlapping session populations.
- Compare the same route's compatible prior period or peers with the same intent and page type. Challenge channel/device/market mix, stock, promotions, price, seasonality, consent and tracking. Do not invent a universal benchmark or significance threshold.
- Prioritize investigation by material reach, persistent outcome gap and confidence, rather than the worst percentage. A tiny zero-conversion route should not displace a well-supported high-volume gap. Keep sparse or incompatible comparisons inconclusive.
- Inspect affected and comparison paths using the Check's required viewports. Return candidate dispositions, direct observations and uncertainty to that Check. Apply its criteria and the reporting contract rather than creating another landing-page report or outcome system.