How an app stack grows.
- Reviews widgetwidget.reviews.exampleAdding revenueLoads forEveryone, on product pages41,820sessions loaded1,163orders with it on
- Student discount checkverify.exampleMeasuring · day 9 of 28Loads forCountry is United Kingdom, on every page22,410sessions loaded604orders with it on
- Live chatchat.exampleNo clear differenceLoads forTraffic is paid, on every page9,375sessions loaded288orders with it on
- 1
It starts with a case study.
A reviews app shows a lift in conversion. A chat widget shows bigger baskets. Each pitch was measured on someone else's store, and each one sounds worth a monthly fee.
- 2
The stack grows, one app at a time.
Shopify counts six apps on the average merchant's store. Every paid one renews each month, whether it earned its fee or not.
Shopify Partners, Feb 2022(opens the source) - 3
Every app weighs on every page.
Its scripts load for every shopper on every page, whether or not the app helps there. And on mobile, faster pages have gone with more retail conversions.
Deloitte (commissioned by Google), Mar 2020(opens the source) - 4
At renewal, you guess.
The vendor's report says it's working. Reports like that often credit the app with every shopper who used it, and the shoppers who click are the ones most likely to buy anyway.
NBER (Blake, Nosko and Tadelis), May 2014(opens the source)
What most teams try
- You could take the vendor's word for it. Their report often counts the shoppers who used the app, not the sales it added.
- You could switch an app off for a month. Promotions, seasons and ad spend change in the same month, so the difference isn't only the app's.
Or you could run every app through Benson.
Load each one only where it pays, hold it back from a random share of shoppers, and get one answer at a planned end, from your own orders.







