At Splio, we provide a powerful platform for customer engagement and loyalty management. As a developer, this portal will be your gateway to harnessing the capabilities of our platform and integrating it seamlessly into your applications before starting your Loyalty project. Let's dive into the key concepts of Splio:
A universe is a tenant logically isolated from the others, corresponding to a set of data with a key for each data entity. Each universe is distinct and operates independently, ensuring data privacy and separation.
You have two approaches to interact with Splio, which you can use them separately or together:
- Flat files (CSV) via SFTP: Import and export data files using our Datahub functionality. Get the details in our documentation:
- REST API: Communicate programmatically with Splio through our REST APIs. Find all the API details here.
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)
- triggered by events with conditions (on the data)
- and giving outcomes: attribution of points or rewards
- with a validity period and execution limits.
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.
Splio follows a robust relational data model focused on commerce. The main entities are:
|Memberships||card_code, nq_points, q_points and tiers||GET Membership|
|Rewards and rewards attributions||GET List rewards|
|Products||Records in the ||GET Products|
|Stores||Data related to your physical stores and e-commerce store.||GET Stores|
|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|
|Order items||Records in the “ordersitems” scope can't be updated. Instead, you need to be prepared to reimport all orders items for each “order_id” you update in the “orders” or “abandonedcarts” scope. Updates to these two scopes always result in Splio purging all associated order items (it is one of the initial steps of import).|
|Interactions||Custom events you can send to Splio to trigger specific use cases such a loyalty points credit.||POST Interactions|
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.
Detailed description of main properties in this article : https://support.splio.com/hc/en-us/articles/360015018319-Overview-of-database-fields
Updated 5 months ago