Authorized sources
Klaviyo uses a read-only private API key. Shopify uses Archet's disclosed standard app permissions.
Five founder-assisted audit slots
Find where Shopify behavior and Klaviyo automation disagree
Archet runs a bounded, read-only review across the sources you authorize, shows the evidence behind each supported finding, and tells you what to review next. No campaigns, profiles, flows, or store data are changed by the audit.
The 20-second proof
One controlled run, its report, and its limits
On August 31, 2026, one Archet-controlled production run persisted 14 finding rows: 6 healthy, 3 warnings, 0 critical, and 5 unknown. The report combined four automated probes with configuration and state checks; 14 means finding rows, not 14 independent provider probes.
This is runtime evidence from one controlled run, not merchant validation or evidence of revenue impact. No real-merchant Klaviyo write was executed.
Shopify + Klaviyo
Controlled run · 2026-08-31Controlled-production evidence
0--4 sec
One run persisted 14 finding rows
On August 31, 2026, one Archet-controlled production run recorded 6 healthy, 3 warnings, 0 critical, and 5 unknown findings.
14 rows · 6 healthy · 3 warnings · 0 critical · 5 unknown
Ready20 seconds
The evidence version
What sits behind a finding
A roughly 75-second read of the boundaries, provenance, confidence, and action state the short proof compresses.
Finding provenance
Direct Klaviyo metric and report reads are compared with Shopify order evidence, connector state, and a bounded storefront scan.
Evidence versus inference
Counts and configuration are evidence. A likely cause is labeled as an inference, with confidence and any missing evidence stated explicitly.
Recommended action
The audit names the smallest next review. It does not claim attributed revenue or incremental lift without a defensible baseline.
Authority boundary
The audit can monitor and propose. A supported write is separate and remains behind identity, permission, approval, revalidation, and audit controls.
Receipt state
The forwardable audit records findings and evidence. A provider-action receipt exists only after an authorized action is actually executed.
What you receive
A useful artifact, not a generic demo
- Three to five findings when the evidence supports them
- Shopify and Klaviyo evidence, severity, and confidence for each finding
- Evidence limits and unknowns without invented revenue precision
- The recommended next action and current monitor, propose, or execute boundary
- An explicit inconclusive result when the available evidence is insufficient
How the cohort works
- 1. Qualify. Confirm Shopify, Klaviyo, and a relevant lifecycle or ecommerce owner.
- 2. Authorize. Connect only the sources required for the bounded read-only review.
- 3. Review. Receive the first verified finding and a founder-assisted readout.
- 4. Decide. Keep the artifact whether or not a design-partner or paid deployment follows.
Check your marketing stack
Start with a bounded qualification call. Access is requested only after the audit is a fit.