Splio Customer Platform - Main Concepts

As a developer, this documentation will be your gateway to harnessing the capabilities of our platform and integrating it seamlessly into your applications.

Please read first "How Splio Customer Platform works" to have an overview before diving into the main concepts behind it.

1. Tenant

Splio Customer Platform is multi-tenant Software as a Service. Each tenant is logically isolated from the others, corresponding to a set of data with a key for each data entity. Each tenant is distinct and operates independently, ensuring data privacy and separation.

A tenant is called:

A universe in the context of Marketing Auto & Loyalty
A domain in the context of CDP & Predictive AI
An organization in the context of Mobile Wallets

2. Splio Data Input & Output

You have three approaches to integrate with Splio Customer Platform, which you can use separately or combined:

REST API: Integrate programmatically through our REST APIs. Find all the API details here.
Flat files: Import and export data through CSV files via SFTP. Get the details in our documentation:
- Imports through Datahub
- Exports through DXP
Splio Connectors: Built by Splio or Partners to ease the integration with your technical ecosystem. Check our catalog to find the one you need!

3. Relational Commerce-Oriented Data Model

Splio follows a robust relational data model focused on commerce. The main entities are:

Entity	Detail	API reference
Contacts	Data related to a contact also known as end-user. It is commonly known as prospect when the contact is not linked to any order or a customer when it is linked to at least one order.	GET Contact
Lists	Used to manage consent to a service via a channel. More info in Managing lists and unsubscriptions.	POST Subscribe a contact to list(s)
Order and order items	Data in the “orders” scope may be updated with a later upload. If you import an order which has the same ID as an existing one, the new order will replace the existing one, and all orderitems linked to the existing order will be deleted. Splio will reject any "orderitem" record if the linked order is not created yet.	GET Orders
Products	Records in the `products` scope represent items which can be purchased. `Products` are then related to `orders` (representing orders) via `ordersitems` (individual items in each order).	GET Products
Stores	Data related to your physical stores and e-commerce store.	GET Stores
Interactions	Custom events you can send to Splio to trigger specific use cases such a loyalty points credit.	POST Interactions
Memberships	card_code, nq_points, q_points and tiers	GET Membership
Rewards and rewards attributions		GET List rewards

Splio's data model allows for customization to meet your specific requirements. It includes two types of fields: system fields and custom fields.

System fields are predefined and consistent across all tenants in Splio. They provide essential attributes and functionalities available within the platform.
Custom fields offer flexibility by allowing you to create fields tailored to your unique needs. They capture additional information specific to your business or industry.

You can find a detailed description of your database fields in this article

4. Loyalty Engine

Splio's Loyalty Engine empowers you to design and implement one (or more) loyalty program(s). It supports both simple and tiered programs with global settings. Key features include:

Simple or tiered having global "settings"
- non-qualifying points (convertible into rewards attributions)
- qualifying points (in the context of a tiered program)
Rules
- triggered by events with conditions (on the data)
- and giving outcomes: attribution of points or rewards
- with a validity period and execution limits.

5. Loyalty Web Kit

Splio provides you with a Loyalty Web Kit to ease the integration of your Loyalty program on your e-commerce. You can read more on the general introduction in this article.