Skip to main content

Weekly digest & engine audit

How to use it​

  1. Turn on the weekly digest — it lands Monday 7 AM with last week's KPIs + top actions. (Analytics → Digest)
  2. Point your technical team at the engine audit for system health.
  3. Skim it Monday instead of digging all week.

⏱ ~5 min Monday · 💳 Free · 🎯 The right detail to the right person

Why this matters for your business​

Two surfaces serve different audiences:

  • Weekly digest — for merchants/operators. The "what happened, what to do" email Monday at 7 AM.
  • Engine audit — for the technical team. System health, worker status, integration posture.

Both serve the same purpose: make the right level of detail visible to the right person at the right cadence, so neither team has to dig for it.

What this typically unlocks​

OutcomeResult
Merchant time on data review5 min Monday vs. hours throughout week
System issues caught before customer impact+85%
"Did anyone notice this?" → "Yes, in Monday digest"resolved
Decision-readiness Monday morningimmediate

Weekly digest — what's in it​

Lands in your inbox + appears in-app every Monday 7 AM (local time):

Subject: Your week — 3 actions, $4.2K opportunities

LAST WEEK
────────────
Revenue: $84,200 (+8% vs prior week)
Orders: 1,420 (+5%)
New customers: 287 (-2%)
Top channel: Meta retargeting

WHAT WORKED
────────────
✓ Cart-recovery journey: $9,400 recovered (+22%)
✓ "Spring sale" campaign: 142 conversions
✓ TikTok new audience: 38 customers at $32 CAC

OPPORTUNITIES (3)
────────────
1. Cart-recovery email open rate down 28% — likely Apple
   Mail Privacy. Switch primary metric to clicks.
   [Apply →]
2. 12 customers crossed predictive-LTV $500 threshold
   this week. Eligible for VIP outreach.
   [Show list →]
3. Free-shipping bar dormant on 14 mobile PDPs.
   Activate?
   [Activate →]

WHAT'S COMING UP THIS WEEK
────────────
• Approval queue: 3 campaign approvals waiting
• Calendar: Mother's Day campaign launches Friday

Configurable — exclude sections, change cadence (daily for high-velocity stores, monthly for steady-state).

Engine audit — for the technical team​

The platform's operational health surface:

SectionWhat it shows
Worker statusAll 30+ background workers — running, queued, failed
Queue depthsPer-engine queue sizes; alerts on backlog
Webhook healthDelivery rates, retry counts, dead-letter
API rate limitsShopify, Meta, Google, TikTok — current usage vs. cap
Recent errorsLast 24h, grouped by source
Deploy logRecent platform updates
Storage / DBPer-shop usage vs. tier cap

If everything is healthy, this dashboard is boring — green checkmarks across the board. The day it's not boring is the day someone needs to act.

Real merchant scenarios​

Scenario A — Founder reads digest in 5 minutes​

Setup. Solo founder. Pre-platform: ~30 min Monday checking each dashboard.

Post-platform: Reads digest at 7:05 AM, sees 3 actions, clicks 2 of them (one apply, one schedule for later). 5 minutes.

Time saved: 25 min/week × 52 = ~22 hours/year.

Scenario B — Engineering catches Resend hiccup​

Setup. Engineer opens engine audit Monday. Sees: "Email worker queue depth 8K (typical 100). Email send latency P99

30s."

Investigation: Resend (email provider) had an upstream issue overnight; queue built. Auto-failover to SMTP triggered correctly; queue clearing.

Action: Verified failover; let it clear. No customer impact (sends still happening, just slightly delayed).

Scenario C — Agency reads digest per client​

Setup. Agency manages 12 brands. Weekly digest sent to each brand's marketing lead AND the agency's account manager.

Account manager: Reviews 12 digests in ~30 min Monday. Identifies cross-client opportunities ("Brand A and Brand B both have Apple Mail KPI shift; let's hit it on a webinar").

Best practices​

✅ Read the digest Monday morning, not later in the week. The "fresh" framing matters; by Wednesday it's stale.

✅ Configure recipient list per shop. Founder + marketing lead + ops lead probably want different emphasis.

✅ Action top 3 items the week of digest. Letting them slip negates the value.

✅ Watch engine audit for green checkmarks. Boring is good; investigate the moment it's not.

❌ Don't auto-archive the digest. Read first, then archive.

❌ Don't ignore engine audit because "it's working." Set weekly reminder.

Plan tiers​

CapabilityFreeStarterProAgencyEnterprise
Weekly digest (basic)✓✓✓✓✓
Customizable sections—✓✓✓✓
Configurable cadence—✓✓✓✓
Multi-recipient—✓✓✓✓
Engine Audit—✓✓✓✓
Multi-shop digest roll-up———✓✓
White-label digest (agency)———✓✓
Custom digest sections (SQL)————✓

See also​