I think WebEngage Customer Data Platform can be improved if they work with AI segmentation. I believe there is still room for improvement on their AI features because sometimes the AI segmentation and timing do not perform as well in A/B testing, as the manual segmentation and timing still deliver better results in terms of click rates. Regarding WebEngage Customer Data Platform's AI capabilities, I believe I can trust their compliance as they have the necessary security certification. Unfortunately, for the accuracy and reliability of WebEngage Customer Data Platform's AI output, I think they still need to improve because my A/B testing with manual methods yields better results in terms of click-through rate and delivery rates than using AI segmentation and delivery time.
I would suggest a notification inbox feature as a separate channel with WebEngage Customer Data Platform. Let's assume that a user is getting a push notification through an app and you want that particular notification that was triggered a while ago, yesterday, a week back, two days back, or whenever, to be stored in your app's notifications. I think that should be a separate channel rather than a particular feature inside another channel. Notification inbox is not actually a separate feature, though it has been mentioned in the documentation guide as a separate channel. However, it has been treated as an in-house feature of push and web push. If this feature were available as a separate channel with WebEngage, I would have stuck with WebEngage entirely rather than going to any other solution. Regarding metrics, I am able to reach my targets with WebEngage Customer Data Platform. Obviously, it depends on user activity, as some users would be active during certain months and there would be some idle or dull months. During dull months, WebEngage makes sure that I meet my targets at least 85 to 90 percent of the time, which means I have the best service providers and channels coming in. Regarding attendance, there was a lesson drop where the benchmark for lesson one was around 60 percent and for lesson two was around 50 to 55 percent. For lesson three, it was around 50 percent. When we understood the metrics with WebEngage, we discovered that lesson three was falling short by 5 to 10 percent, which was concerning. Since WebEngage was able to share these metrics with me, I was able to create campaigns to ensure people came back and took their lessons for lesson three, getting my attendance back to 50 to 55 percent. From an operations perspective regarding WebEngage Customer Data Platform, I do not find many issues. However, if you do not make up your payments, they keep on pointing out popups that annoy you on every click. If you have not made a payment for WebEngage services and it is overdue, payment reminders will keep popping up, which is annoying. I am not sure if WebEngage can come up with some alternative options to ensure this is not impacting users or organizations.
One major issue that I face is while handling large data segments for creating these workflows. Sometimes it lags or hangs a bit. Apart from that, I have not faced any issue with this platform. Only while handling large segments, it feels slow, but apart from that, it is a great platform.
WebEngage Customer Data Platform can improve in areas like advanced reporting customization, dashboard simplicity, and enterprise-scale analytics visibility. Some clients feel the platform has a learning curve initially, especially when managing complex journeys and large-scale data orchestration.The platform could improve integration flexibility for highly customized enterprise ecosystems and make third-party connector management smoother. Some customers often request faster support resolution during complex implementations or campaign issues.
One thing that I really think can be improved in WebEngage Customer Data Platform is that it lacks a robust analytics platform. I wish WebEngage Customer Data Platform had more options of templates. Another needed improvement for WebEngage Customer Data Platform is that building sales intelligence via auto-recommendation should be improved.
Learn what your peers think about WebEngage Customer Data Platform. Get advice and tips from experienced pros sharing their opinions. Updated: July 2026.
WebEngage Customer Data Platform empowers businesses with data-driven insights to effectively engage their audience. With advanced segmentation and personalization capabilities, it helps organizations optimize customer interactions and maximize value.As a comprehensive tool, WebEngage Customer Data Platform offers a suite of features designed to enhance customer engagement strategies. Utilizing customer data, businesses can craft personalized campaigns, ensuring relevant communication that...
I think WebEngage Customer Data Platform can be improved if they work with AI segmentation. I believe there is still room for improvement on their AI features because sometimes the AI segmentation and timing do not perform as well in A/B testing, as the manual segmentation and timing still deliver better results in terms of click rates. Regarding WebEngage Customer Data Platform's AI capabilities, I believe I can trust their compliance as they have the necessary security certification. Unfortunately, for the accuracy and reliability of WebEngage Customer Data Platform's AI output, I think they still need to improve because my A/B testing with manual methods yields better results in terms of click-through rate and delivery rates than using AI segmentation and delivery time.
I would suggest a notification inbox feature as a separate channel with WebEngage Customer Data Platform. Let's assume that a user is getting a push notification through an app and you want that particular notification that was triggered a while ago, yesterday, a week back, two days back, or whenever, to be stored in your app's notifications. I think that should be a separate channel rather than a particular feature inside another channel. Notification inbox is not actually a separate feature, though it has been mentioned in the documentation guide as a separate channel. However, it has been treated as an in-house feature of push and web push. If this feature were available as a separate channel with WebEngage, I would have stuck with WebEngage entirely rather than going to any other solution. Regarding metrics, I am able to reach my targets with WebEngage Customer Data Platform. Obviously, it depends on user activity, as some users would be active during certain months and there would be some idle or dull months. During dull months, WebEngage makes sure that I meet my targets at least 85 to 90 percent of the time, which means I have the best service providers and channels coming in. Regarding attendance, there was a lesson drop where the benchmark for lesson one was around 60 percent and for lesson two was around 50 to 55 percent. For lesson three, it was around 50 percent. When we understood the metrics with WebEngage, we discovered that lesson three was falling short by 5 to 10 percent, which was concerning. Since WebEngage was able to share these metrics with me, I was able to create campaigns to ensure people came back and took their lessons for lesson three, getting my attendance back to 50 to 55 percent. From an operations perspective regarding WebEngage Customer Data Platform, I do not find many issues. However, if you do not make up your payments, they keep on pointing out popups that annoy you on every click. If you have not made a payment for WebEngage services and it is overdue, payment reminders will keep popping up, which is annoying. I am not sure if WebEngage can come up with some alternative options to ensure this is not impacting users or organizations.
One major issue that I face is while handling large data segments for creating these workflows. Sometimes it lags or hangs a bit. Apart from that, I have not faced any issue with this platform. Only while handling large segments, it feels slow, but apart from that, it is a great platform.
WebEngage Customer Data Platform can improve in areas like advanced reporting customization, dashboard simplicity, and enterprise-scale analytics visibility. Some clients feel the platform has a learning curve initially, especially when managing complex journeys and large-scale data orchestration.The platform could improve integration flexibility for highly customized enterprise ecosystems and make third-party connector management smoother. Some customers often request faster support resolution during complex implementations or campaign issues.
One thing that I really think can be improved in WebEngage Customer Data Platform is that it lacks a robust analytics platform. I wish WebEngage Customer Data Platform had more options of templates. Another needed improvement for WebEngage Customer Data Platform is that building sales intelligence via auto-recommendation should be improved.