GrabSaubhagya AwaneeshProblem & solution
How Grab is accelerating growth with real-time personalization using Customer Data Platform scenarios
Summary
Grab’s Customer Data Platform (CDP) introduced Scenarios to address the limits of daily batch attributes for real-time personalization across marketing and user journeys. The capability combines Scribe event triggers, geo-fencing, optional historical CDP data, and predictive models, with a self-serve GUI for configuring and validating event sequences and APIs for programmatic management. Incoming events are processed through Flink, with historical data evaluated in StarRocks and outputs written to Kafka, Amphawa, or both for downstream consumption; configured Scenarios become available within an hour and are designed for latency under 15 seconds. More than 12 implementations are live, including a Grab Unlimited abandonment intervention that notified users 15 minutes after signup drop-off and produced over a 3% uplift in subscriber conversions versus non-real-time acquisition campaigns. Planned work includes scalable Scenario sharding, multiple output destinations, and delayed triggering.
Context
Grab’s existing personalization framework relied primarily on batch user attributes updated once daily, making it unsuitable for immediate responses. Real-time personalization also required substantial engineering effort, limiting scalability, experimentation, and the ability of marketers and product teams to act on dynamic user events enriched with historical data.
Approach / What changed
CDP Scenarios combine Scribe events, geo-fencing, optional historical CDP attributes, and predictive models through a self-serve GUI and headless APIs. Flink processes incoming events, StarRocks supplies historical data, and results are sent to Kafka or Amphawa for downstream services. Scenarios are validated with synthetic data and become available for real-time consumption within an hour.
Takeaways
Scenarios support real-time triggers based on Scribe events and geo-fencing, with optional enrichment from historical CDP attributes and pre-trained or custom predictive models.
The architecture uses Flink for event processing, StarRocks for historical data evaluation, and Kafka or Amphawa for synchronizing outputs to downstream services; target latency is under 15 seconds.
A Grab Unlimited signup-abandonment Scenario sent follow-up notifications after 15 minutes and achieved more than a 3% uplift in subscriber conversions versus non-real-time acquisition campaigns.
Source and freshness
- Source
- engineering.grab.com
- Published
- Added to Yomu
- Last updated
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.