LiLA Studios

You launched your product, got some early traction, and now the questions arrive: which numbers should I watch daily? How do I know if a campaign was worth it? When do I hire another person or double down on a channel? Measurement feels like a second job — one that pays off if you do it right and wastes time if you don’t.

This post is a friendly, practical guide to the KPIs that actually move the needle for sustainable ecommerce growth. It’s written for founders, CFOs, and growth leads who want clear signals — not a dashboard forest. We’ll walk how to instrument core events, how to think about cohorts and LTV/CAC, what operational KPIs keep fulfillment healthy, and how to move from simple Sheets to a production BI setup (Looker/Metabase) without over-engineering.

Core metrics & how to instrument them (xAPI, GA4, server events)

Think of instrumentation as a checklist of the important moments in a customer’s journey. Each time someone does something — views a product, adds to cart, checks out — that’s an event you want to capture. Capture consistently and you can answer questions with data, not guesses.

What to instrument first (the high-impact events)

• Page view / product view: which products get attention.
• Add to cart: intent signal.
• Begin checkout / checkout completed: conversion funnel stages.
• Purchase completed: revenue and SKU-level detail.
• Subscription started / cancelled / paused: critical for recurring revenue.
• Refund / return initiated: operational stress signal.
• Email signup / SMS opt-in: channels for retention.

Tooling choices (plain language)

• GA4 handles client-side web events and is great for marketing channels and web attribution. It’s useful and often free, but treat it as one source of truth — not the only one.
• Server events (send events from your backend) are more reliable for purchases and reconciliation because they’re not blocked by ad-blockers or flaky browsers.
• xAPI or custom event layers provide structured ways to name and describe events consistently across web, mobile, and POS systems.

Practical approach for teams new to measurement

1. Start with a short event dictionary — a simple list of event names and required properties (e.g., purchase → order_id, total, currency, items[]). Keep it to 8–12 events.
2. Fire both client-side (GA4) and server-side for purchases. Server-side events are your source-of-truth for sales.
3. Timebox initial instrumentation to two weeks. Get the basics working and then iterate. You’ll learn a lot from the first 90 days of real traffic.

A tip: instrument with business questions in mind. If you want to know “how many customers order again in 30 days,” ensure you capture a persistent customer ID at purchase.

Cohort analysis & LTV/CAC framework

Cohort analysis is the single most practical way to understand whether what you’re doing creates lasting value. Instead of mixing everybody together, cohorts group customers by a start point — usually the week or month they first bought — and lets you see how behavior changes over time.

The simple LTV/CAC story

• CAC (Customer Acquisition Cost): total marketing spend / new customers acquired in a period. Include paid ads, creative costs, agency fees — the full funnel cost.
• LTV (Customer Lifetime Value): the revenue (or margin) you expect from a customer over their lifetime. For early-stage brands, focus on a short-window LTV (30/90/180 days) and refine as data accumulates.

Basic formulas (start simple)

• CAC = Total marketing spend in period / Number of new customers acquired in that period
• LTV (30d) = Average revenue per customer from cohort in first 30 days
• Payback period = CAC / Average gross margin per month (months to recover CAC)

Why cohorts beat averages

Averages lie. If your overall LTV looks healthy but the cohort that came from paid social has terrible 30-day retention, you’ll burn money scaling that channel. Build a simple cohort table:

• Rows: cohort month (Jan, Feb, Mar)
• Columns: revenue in days 0–30, 31–60, 61–90, cumulative LTV

Actionable rules of thumb

• If 30-day retention for a paid channel is below your target, stop scaling until you fix onboarding or product fit.
• Aim for CAC payback in 6–12 months for subscription-heavy businesses, faster for pure retail. The faster you recover CAC, the faster you can scale.

Operational KPIs for fulfillment & returns

Growth is hollow if operations can’t keep up. The KPIs below prevent small problems from becoming business-stopping disasters.

Key ops metrics to track

• Order accuracy (% correct orders packed): Target above 98% for most consumer goods. Errors cost refunds and trust.
• Fulfillment latency: Time from order to packed to handoff. For local delivery, measure in hours; for shipping, in days. Benchmarks vary by model — set realistic SLAs up front.
• On-time delivery rate: Percent of orders delivered within promised window. Aim for 95%+.
• Return rate / refund rate: Monitor by SKU and channel. High return rates often signal mismatch between product expectations and listing content.
• Inventory sync lag: Time since last successful inventory update to channel. Prevents oversells.
• Average handling time per order: For staffing and labor forecasts.

Dashboard signals that matter

• Red flags: sudden spike in returns, drop in payment success rate, or inventory sync failures. These should trigger an alert and a fast check-list (is it config? a partner outage? human error?).
• Golden path metric: percentage of orders that pass through without any touch (no manual intervention). The higher, the healthier.

Practical operational hygiene

• Run daily morning checks on inventory sync and pending orders.
• Keep quick reference SOPs for common failures (payment decline, missing SKU, customer no-show).
• Automate the simplest alerts — when order accuracy dips or returns jump, the ops lead gets a Slack ping.

LiLA dashboard templates (Sheets → Looker/Metabase → BI handoff)

Start small, then scale. Here’s a sensible path many teams follow.

Phase A — Sheets (Day 0–30)

• Use Google Sheets as a living dashboard: ingest exported orders, mark cohort buckets, calculate simple LTVs and CACs. Sheet pros: fast, editable, visible. Use this for early learning and stakeholder alignment.

Phase B — Metabase / Looker Studio (30–90 days)

• Move the most useful Sheets views into a lightweight BI tool: product performance, channel CAC, cohort retention curves, and ops health tiles. These tools connect to your database or to consolidated csvs and let non-technical folks explore.

Phase C — Looker / Redash / Enterprise BI (90+ days)

• As data volume and complexity grow, formalize a semantic layer (clean naming, consistent definitions), set up scheduled reports, and add access controls. This is the handoff for growth and finance teams who need reliable, auditable numbers.

Dashboard essentials (what each view should show)

• Executive view: revenue, gross margin, CAC, LTV (30/90), active subscribers, churn, short payback metric.
• Growth view: CAC by channel, conversion funnel (sessions → add-to-cart → checkout), cohort retention table.
• Ops view: order accuracy, fulfillment latency, inventory sync health, return rate by SKU.
• Finance view: gross margin by channel, refunds, net revenue, LTV cohorts for forecasting.

LiLA tip: lock down a single definition for “active customer,” “churned,” and “subscription cancel” across teams. Semantic mismatches are the top source of internal disagreement.

Wrap & next step

Measurement doesn’t have to be hard to be useful. Start with a short list of events, capture clean purchase data server-side, and use cohorts to see who actually returns. Combine that with a lean ops dashboard and you’ll spot problems early — and scale with confidence.

If you want help turning these ideas into an operational dashboard, schedule a LiLA metricization workshop. We’ll audit your current tracking, prioritize events, and build a simple dashboard plan (Sheets → Metabase / Looker → BI handoff) so you can move from guesswork to decisions.

Next in our series: with these metrics in place, we’ll show how to productize your learnings into a repeatable LiLA ecommerce program — the playbook that turns experiments into a growth engine.

Other Articles in the Ecommerce Series

Choosing the Right Ecommerce Platform for Your Brand
Memberships & Recurring Revenue
Dropshipping & Print-on-Demand
Fashion First
Ecommerce + Fundraising
B2B & Construction Ecommerce
Farm-to-Table Commerce
Checkout Optimization
Retention & Lifecycle
Marketplaces & Social Commerce
Scaling Ops
Measurement & Dashboards
From Blog to Business