| Workflow | A directed graph of Nodes that defines personalisation logic — what content to show, to whom, and when. |
| Datasource | A connection to an external data feed that Reelevant fetches, parses, and stores for use in personalisation. |
| Content | A visual template (banner, email section, landing page) designed in the Content Editor. |
| Node | A single processing unit in a Workflow graph. Types: Channel Node, Data Node, Logic Node, Output Node. |
| Channel | The entry Node of a Workflow that defines the delivery medium (Email, Web, Mobile, Landing Page). |
| Branch | A unique execution path through a Workflow, from a Channel to an Output Node. |
| Output Node | A terminal Workflow Node that produces the final response (Visual Content, JSON Template, Empty). |
| Data Node | A Workflow Node that fetches or provides data (Datasource query, URL Parameter, Geolocation, Weather, Transform). |
| Logic Node | A Workflow Node that controls flow with multiple outgoing paths (Condition, Split, Real-Time Testing). |
| DataHub | The platform’s data management center for importing and configuring external data. |
| Content Editor | The visual drag-and-drop editor for designing Content templates with dynamic data bindings. |
| Team | An organisational unit (Resource Group) for controlling access to Workflows, Contents, and Datasources. |
| Runner | The backend service that executes a Workflow and returns personalised content. |
| Field Mapping | The configuration that maps raw data fields to standardised Reelevant types. |
| Variable Profile | A reusable set of URL parameters (UTM, tracking) applied when integrating a Workflow. |
| Real-Time Testing | A Logic Node that splits traffic between multiple Branches for A/B or multivariate testing. |
| Transform | A Data Node that applies transformations (string, number, date, array operations) to data within a Workflow. |