How Étoile Milano Recovered an Extra €15.7K With Littledata-Triggered Klaviyo Flows
Introduction
Étoile Milano is a luxury jewelry brand with a loyal DTC customer base on Shopify. Working with their email agency Subjectlime, the team rebuilt their entire Klaviyo program in 58 days: a new sending domain, list growth, and a lifecycle stack of 15 automations. Email became the most reliable channel on the P&L, with €169K attributed in the first reporting window, around 29% of total store revenue.
The Challenge
Étoile Milano's email program was underperforming its potential. Deliverability was degrading, flows were missing or unstructured, and Shopify revenue didn't reconcile with Klaviyo.
Underneath sat a data problem. Standard client-side tracking couldn't identify enough shoppers: Safari's ITP and ad blockers stopped browse and cart events from firing, and opted-in subscribers arriving on new devices browsed as strangers. Every unidentified shopper was an abandonment flow that never triggered.
The data foundation needed to be in place first. Subjectlime rebuilt the sending infrastructure and lifecycle stack, and installed Littledata as the data layer between Shopify and Klaviyo.
Key Wins
€15.7K
incremental revenue from Littledata-triggered flows in 30 days
2.5×
lift in recovered abandonment revenue
2.9×
more abandoned carts identified
12.9%
of all email-attributed revenue from three Littledata flows
The Solution
Subjectlime gave Étoile a clean foundation to build on: an authenticated sending domain, structured list hygiene, and 15 sequenced automations.
Littledata then made sure those automations could reach every shopper they were built for, automatically, with no custom code required.
Every shopping event now reaches Klaviyo server-side, tied to a profile wherever the shopper can be identified:
- Viewed Product – Littledata: fires on every product view
- Added to Cart – Littledata: fires when an item is added to cart
- Checkout Started – Littledata: fires when a checkout is created in Shopify
Why this matters:
- Events fire server-side from Shopify, so ad blockers and browser limits can't stop them
- Littledata's cloud identity graph ties sessions back to known Klaviyo profiles, including across devices
- Klaviyo-attributed revenue reconciles against Shopify orders, with test orders, returns, and duplicates filtered out
Klaviyo · Top performing flows · The Littledata-triggered versions (Checkout Started – Littledata, Viewed Product – Littledata, Added to Cart – Littledata) run alongside the standard-triggered versions.
How It Works
- Parallel flows: Each core abandonment flow ran in two versions with identical messaging, one on the standard trigger, one on the Littledata trigger.
- Exclusion logic: Flow filters, part of the segmentation system Subjectlime built into the account, kept every profile in only one version, so each flow worked a distinct audience.
- Incremental by design: The standard flows fired for shoppers standard tracking identified. The Littledata flows fired for shoppers only Littledata's events identified, shoppers who would otherwise receive no abandonment message at all.
- Verified reporting: Revenue reconciliation confirmed the Klaviyo numbers against Shopify's source of truth.
Littledata lets Étoile's flows fire on every identified shopping moment, so the same automations recover more revenue as the brand grows.
With better identity resolution
Target emails higher in the funnel for 2× performance
Klaviyo's native tracking can only start a flow once a shopper enters an email address, around 3% of sessions. By then, half of your engaged shoppers are already out of reach.
Littledata's identity resolution recognizes returning shoppers the moment they act, so Étoile's flows trigger at add to cart (around 6% of sessions) and start checkout, not just at email entry.
Triggering higher in the funnel roughly doubles the audience entering abandonment flows, which means more sends, more recovered carts, and more revenue from the same flows. For Étoile, that showed up as 2.9× more carts identified and a 2.5× lift in recovered revenue.
With and Without Littledata
Same store, same flows, same creative: 17 January to 16 February 2026.
| Without Littledata | With Littledata | |
|---|---|---|
| Abandoned cart triggers (30 days) | 1,174 | 4,594 (2.9× via Littledata events) |
| Browse abandonment emails | 5,047 | 11,902 (+36% more per published range) |
| Recovered abandonment revenue | €10,229 | €25,960 (2.5× lift) |
| Shoppers behind privacy walls | Invisible to flows | Identified and entered into flows |
| Revenue reporting | Klaviyo and Shopify didn't match | Reconciled, with noise filtered out |
Results
Over the 30-day window from 17 January to 16 February 2026:
- Littledata-triggered abandonment flows recovered €15,731, incremental to the €10,229 from the standard-triggered versions.
- Total recovered abandonment revenue reached €25,960, a 2.5× lift from the same flows, creative, and audience. Six in every ten euros came through a Littledata trigger.
- Added to Cart – Littledata fired on 3,420 carts against 1,174 for the standard event: the same store activity, with 2.9× more of it identified.
- Browse abandonment triggered 36% more emails, in line with the 20–200% range Littledata publishes for browse flows.
- Those three Littledata-triggered flows alone accounted for 12.9% of all email-attributed revenue in the window.
- Program-wide, the rebuild attributed €122,211 (82.3% from flows, and roughly 29% of total store revenue), with open rates up from 13.3% to 45.0% and the list growing from 6.5K to 33K subscribers.
