CASE FILE 05CLIENT GENERALISEDALL DATA MOCKED

Email performance in one view.

A store was sending lots of email without knowing what each send earned. This project built a clear Klaviyo dashboard showing revenue per email, flows vs campaigns, and list health.

CLIENTECOM BRAND
MODELLIFECYCLE → ORDERS
STACKKLAVIYO · LOOKER
ENGAGEMENT5 PHASES · FULL SYSTEM
STATUSLIVE · AUTOMATED
THE BOARD — OVERVIEWAI-BUILT · LIVE HTML
EXHIBIT A
1

The tiles show sends, opens, clicks and revenue per email.

2

The chart tracks opens and clicks day by day.

3

The donut shows how much revenue comes from automated flows vs campaigns.

The Brief

Lots of emails, little clarity.

The email calendar was full, but nobody knew if the automated flows or the weekly campaigns were making the money. Opens looked fine and revenue looked fine — but the two were never connected.

We connected every send to the orders it produced and built the dashboard around one number: revenue per email. Now the team knows what works and when the list needs a rest.

THE GOAL: know what every email earns, and spot list fatigue early.

✗ THE PROBLEMS

  • Flows vs campaigns revenue split unknown
  • Send-frequency debates settled by opinion
  • Unsub creep noticed months late
  • Subject-line wins never systematised
  • List growth counted, list health ignored
The System

How the system works.

Klaviyo data is pulled and connected to orders at the individual email level. The results are shown in a clean, light Looker Studio dashboard, with alerts for fatigue and spam rates.

Klaviyo API

Sends, opens, clicks, unsubs, orders — message level.

Models

Revenue-per-mail, flow-vs-campaign split, fatigue signals.

Looker Studio

Six light-theme pages: program, flows, campaigns, list, deliverability, alerts.

Action Layer

Fatigue and spam-rate alerts · weekly send-plan summary.

The Process

How the project ran.

01

Audit

  • Traced revenue attribution gaps between Klaviyo and store
  • Benchmarked engagement decay across segments
02

Measurement Plan

  • Revenue-per-mail as the north-star metric
  • Defined fatigue thresholds worth alerting on
03

Implementation

  • Klaviyo API modelled to message-level orders
  • Flow vs campaign split built once, reused everywhere
04

Dashboard Build

  • Light-theme six-pager — easy to read
  • Top-campaign and top-flow leaderboards
05

Automate & Optimise

  • Fatigue + spam alerts
  • Weekly send-plan summary with winners
The Build

Campaigns, in detail.

Two more pages: the campaign table and the alerts page. Built in HTML with sample data.

PAGE 02 / 06 — CAMPAIGNSLIVE HTML · MOCK DATA
EXHIBIT B
Campaign Deep-Dive

Every subject line, priced.

  • The table ranks campaigns by revenue per email, not just opens.
  • The chart tracks revenue per email against the $0.80 target.
  • The segment list shows which groups to protect, upgrade or rest.
PAGE 06 / 06 — ALERTS + AILIVE HTML · MOCK DATA
EXHIBIT C
Automation Layer

Alerts keep the list healthy.

  • Rules watch opens and unsubscribes for each segment and flag fatigue early.
  • The Monday AI summary shows what flows and campaigns earned, in dollars.
  • Each alert includes the fix: change the schedule, roll out a winner, or rest a segment.
Deliverables

What was delivered.

The Results

What changed.

EVERY EMAIL, PRICED.

Revenue per email sits next to open rate, so send-frequency debates end with a number.

FLOWS VS CAMPAIGNS.

The team knows which part of the program earns the most, and focuses there.

FATIGUE, SPOTTED EARLY.

Rising unsubscribes trigger an alert months before they hurt revenue.

NOTE: CLIENT DETAILS GENERALISED · ALL NUMBERS ARE SAMPLE DATA · DASHBOARDS ARE HTML RECREATIONS

Next Steps

Want this for your business?

If your email calendar is full but nobody knows what a send earns, this dashboard answers it.