Instead of Bloomreach and Dynamic Yield
Run Bloomfield against the widget you have now, on your own traffic. See the extra revenue per visitor, with an honest range. Keep it if it wins.
We read what customers say about these tools, and started from their complaints.
Their complaint: "recommendations drove 30% of revenue" proves nothing
Randomly chosen visitors see nothing, or your old widget. The headline is the difference in revenue per visitor. Who clicked is shown separately, and labelled for what it is.
Their complaint: you find out if it worked after you've signed
Half your visitors see your current widget, half see Bloomfield. Nothing else changes, and nobody has to take our word for it.
Their complaint: three to nine months to implement
One line on your site and the feed you already have. Your Dynamic Yield and Bloomreach calls keep working as they are.
Their complaint: months before recommendations get good
Upload your past orders, and "bought together" works before your next visitor arrives.
Their complaint: a huge rule catalogue nobody touches after setup
If they've been here before, picked for them. Otherwise, bought together. Plus a handful of rules: never show, show more of, pin.
Their complaint: one bad column fails the whole feed
What's wrong is named in plain words, and only that row is left out. If a feed suddenly shrinks, it's held back instead of emptying your shop.
| Bloomreach, Dynamic Yield | Bloomfield |
|---|---|
| Attributed revenue, and attribution windows to set up | Revenue per visitor, against a random holdout |
| Export to a BI tool to understand results | A sentence, a number and a range. It says "too early" when it is. |
| Recommendations you take on trust | Every product says why it's there |
| A dedicated specialist | Four screens |
| Priced by traffic, modules and data volume | A tenth of what you pay, and our engineers do the move for free |
The demo is a small coffee roaster mid bake-off, with a pretend shop you can browse and buy from. Watch the numbers move.