Re:Eloquis: Early in the market and targeted the wrong custo...
by roynal on Friday January 26, 2018 @04:54PM
(#16243199)
Well, the example is a very simplistic one for the purpose of this interview. The vision, if you could call it that, was to package other signals e.g. weather, geography, and demography into personalizing a message. Having come from a background of e-commerce I definitely know personalization has a positive impact on cart values, engagement, and conversions. Considering all of that our hope was that we would be that kind of a personalization software for mobile apps.
Re:Eloquis: Early in the market and targeted the wrong custo...
by devit on Friday January 26, 2018 @05:24PM
(#16243403)
But how does that work in practice?
Does their system determine those signals or are they fed to it as input?
How can it possibly provide a generic solution to "personalizing a message" that works across all apps and is not just something trivial like the example in the interview?
On the web the kinds of "personalization" I can think of are public account profiles, targeted advertisements, recommendation engines ("you may also like...", "products like this...", etc.), algorithmic newsfeeds and history-sensitive search. If their software does any of those, maybe they should just say what it does.
Apparently it turns "hello user" into "Hello Bob, itβs great to meet you on a wonderful December day" but it's not at all clear how that's packaged into something that's useful and non-trivial.
That seems like it could have been one of the main problems.