Using Personalised Stories API
Overview
Personalised Stories provides real-time access to enriched player profiles, built from behavioural and transactional data over time.
Unlike event-based APIs or request-driven endpoints, Personalised Stories delivers continuously evolving player narratives that can be used to power lifecycle marketing, CRM journeys, and personalised content experiences.
These profiles are typically consumed by CRM and messaging platforms (for example via Movable Ink) to deliver dynamic, story-driven communications across channels.
For a full product overview, capabilities, and use cases, refer to our:
Personalised Stories Knowledge Base Article
How It Works
Player data is ingested during the Data Transfer process, where it is processed and used to build continuously evolving profiles based on behavioural and transactional activity. These profiles are exposed as real-time story data points via an API layer, which your platform (such as CRM, messaging, or frontend systems) can consume. This data is then used to dynamically render personalised content at the point of delivery, for example when an email is opened or a message is triggered.
When to Use Personalised Stories
Personalised Stories should be used when you want to build narrative-driven campaigns that go beyond simple triggers, enabling richer and more engaging player communications. It is particularly effective for driving long-term engagement and retention by delivering player-specific recaps, summaries, and milestones. The API can also be used to enhance CRM journeys with deeper behavioural context, helping create more personalised and relevant experiences across channels.
Integration Patterns
Most integrations follow one of the following patterns:
1. CRM / Campaign Platform Integration
-
Fetch player story attributes via API
-
Inject into email, push, or messaging templates
-
Render dynamically at send or open
2. Dynamic Email Rendering (Movable Ink)
-
API is called at email open
-
Content is personalised in real time
-
Ensures up-to-date player state
3. Backend Aggregation
-
Your backend retrieves story data
-
Combines with internal attributes
-
Passes into downstream systems
Access & API Specification
Personalised Stories API access and schema documentation are coming soon to the Developer Hub.
As part of this release, you will be able to:
-
Access API specifications and example schemas
-
Explore available data points for storytelling and profiling
-
Understand integration patterns across CRM and messaging platforms
-
Test and validate outputs within your environment
Personalised Stories is designed to support flexible, use-case driven implementations, with schemas that can be tailored to your configuration and campaign needs.
In the meantime, to get early access or discuss integration:
