Skip to main content

​
Request Lifecycle

Reelevant is the only content-first personalisation engine. Build Content once — the platform creates millions of individualised versions at the moment of interaction, not at send time. The following sequence diagram shows the end-to-end flow from a user opening an email (or visiting a page) to receiving personalised Content.

​
Lifecycle Steps in Detail

  1. Request: Your ESP/website/app includes a Reelevant URL (https://reelevant.run/{workflowId}?uid={customerId}). The user’s client requests it.
  2. Edge routing: The CDN terminates TLS and routes to the nearest execution region.
  3. Customer identification: The URL contains a customer identifier (query parameter) mapped to Datasource records. This identifier is public by design — use opaque IDs.
  4. Data retrieval: The Runner fetches the customer’s current data from connected Datasources (from in-memory cache with live fallback).
  5. Workflow execution: The DAG evaluates Conditions, retrieves additional data via Data Nodes, and traverses Branches to select the appropriate Output Node.
  6. Content rendering: The selected Content is rendered with individual data (product images, prices, offers, text) and returned as image, HTML, or JSON.
  7. Event capture: An impression event is recorded. Click interactions are captured via redirect URLs for future Workflow logic and analytics.

​
Infrastructure Guarantees

​
Next Steps

Data Ingestion

DataHub source types and ingestion modes.

Integration Channels

Email, web, mobile, and JSON API patterns.