Client CRO Readiness¶
Complete this once per client
Complete this readiness gate at client kickoff before the Initial Baseline and first CRO campaign. Do not repeat it for every campaign. Recheck only when access is lost, tooling changes, tracking breaks, the storefront is rebuilt or migrated, or the measurement setup materially changes.
Use this page to confirm that the team can access and trust the systems required by the CRO process. Record the completed sign-off in the client's private hub, project record, or task system. Do not publish credentials or client-specific access details here.
1. Access readiness¶
Confirm working access to the correct client account, store, property, or profile:
- Shopify admin with enough permission to inspect store configuration and ecommerce reporting.
- GA4 with access to the correct property and data stream.
- Klaviyo with access to the account, campaigns, flows, forms, and attributed reporting needed for CRO.
- Google Search Console with access to the verified storefront property.
2. Analytics readiness¶
Confirm the core ecommerce and acquisition data is current and flowing. The team must be able to inspect sessions, conversion rate, add-to-cart rate, checkout reach, orders, revenue, device split, channel split, and relevant landing-page or page-level performance where the platform supplies it.
Confirm metric definitions before comparing Shopify, GA4, Klaviyo, Search Console, or experiment-platform values. Verify that consent settings do not create an undocumented measurement gap and that no PII is being sent through analytics events.
3. Behavioral evidence readiness¶
Confirm Clarity or equivalent heatmap and session-recording tooling is installed on the production storefront and collecting usable visits.
Use traffic volume, not elapsed time, as the readiness standard:
- At least 1,000 recorded sessions on each priority page or funnel surface interpreted independently.
- At least 250 recorded sessions in each device segment used for a separate mobile or desktop conclusion.
Only usable production visits count. Exclude or account for internal QA, staff traffic, bots, broken recordings, consent-related gaps, and known tracking failures where practical. If a threshold is not met, continue collecting. Any early behavior read must be labelled directional and combined with other evidence.
4. Experiment platform readiness¶
Confirm Intelligems or equivalent A/B testing tooling is installed and configured for the correct production storefront.
- Confirm the correct store and active theme are connected.
- Confirm control and variant bucketing remains consistent for returning visitors.
- Confirm the commerce events and primary outcomes used by tests can be measured.
- Confirm preview or QA access works before a live test is created.
- Confirm the setup does not create duplicate analytics events or an obvious storefront conflict.
Platform readiness does not make every campaign eligible for A/B testing. Each campaign must still calculate its required sample and pass the measurement gates in Data & Strategy.
5. Ownership and sign-off¶
| Field | Required record |
|---|---|
| Readiness owner | Person responsible for closing setup gaps |
| Access confirmed | Shopify, GA4, Klaviyo, and Search Console |
| Behavior tool | Tool name, production capture, priority surfaces, and recorded traffic |
| Experiment platform | Tool name, store and theme connection, event measurement, and QA status |
| Known gaps | Missing permissions, thin traffic, tracking limitations, or consent constraints |
| Sign-off date | Date the client became ready for Initial Baseline |
Close gate: Access, measurement, behavioral evidence, experiment tooling, owners, and known gaps are documented. The client can now build the Initial Baseline.