SALESmanago CDP: why most implementations stall
Plenty of stores have SALESmanago, but around 80% of the implementations we see don't use it as a CDP. Sending a newsletter from SALESmanago is very different from running a system that knows what a customer looked at ten minutes ago and changes the offer it shows them.
Why SALESmanago often underdelivers
A typical scenario: the store buys a licence, connects a signup form, adds a pop-up with 10% off and considers SALESmanago implemented. The data stays scattered. Product events never reach the customer profile, purchase history sits in the ERP and segments are built on newsletter opens.
As a result, workflows fire at the wrong moment, recommendations are random and marketing reports the number of emails sent instead of conversion. The cause is usually the data architecture underneath, not the tool itself.
The product event model
Before we switch on any workflow, we build an event map: what the customer does in the store, where each signal comes from and how it reaches the 360° profile. Product views, add-to-cart, checkout start, purchase and return are all recorded with context: product, price, category and session source.
Without this data, SALESmanago personalises on guesswork. With it, the system knows where the customer is in the purchase journey and what they are interested in. The difference in conversion usually shows within the first month after the data is connected properly.
Three workflows that pay back the implementation
An abandoned-cart message with dynamic content. Instead of a generic 'You left something behind', the customer gets something like 'One left shoe in size 42 is still waiting. It's the last one in stock today.' An RFM-based winback that reaches customers at the point where we statistically start to lose them. Cross-sell based on real purchase history instead of a generic 'others also bought'.
Configured properly and fed by a reliable event model, these three workflows pay back the cost of a SALESmanago implementation in the first quarter. We measure the results in conversion and revenue.
What official SALESmanago partner status gives you
As an official SALESmanago partner we get early access to new features, a dedicated Technical Account Manager and the option to negotiate better licence pricing for our clients.
More useful in practice is experience with edge cases that the public documentation barely covers. They come up in integrations with Medusa.js, Comarch ERP and Akeneo: inconsistent product IDs, data conflicts between channels, API rate limits on large catalogues. It is better to hit them during a sprint than the night before Cyber Monday.
- SALESmanago works as a CDP only once product events reach the 360° profile
- Abandoned cart, winback and cross-sell pay back the implementation in the first quarter
- Partner status means better licence terms and knowledge of undocumented edge cases