Understanding objects and fields
In this guide, we are presenting you with the required data to make Splio work as intended.
You can read more details on how to import data into Splio using our technical documentation.
In the schema, you can see the objects we expect to receive in your import files, and how they are linked together. Some of them are mandatory, and the others are optional. We have also divided them between events, happening on a precise date (purchases, page views), and dimensions, defining the objects involved in the event (users, products, stores).
Object name | Definition | Category |
User | An individual, customer, or prospects | Mandatory |
Purchase | An event in which a user buys one or several products | Mandatory |
Product | Product Catalog | Mandatory |
Store | Physical and web stores | Mandatory |
Cart | An event in which a user adds one or several products to a cart | Optional |
Refund | An event in which a user returns one or several products (with a negative amount) | Optional |
Page View | An event in which a user consults a page of the e-commerce | Optional |
Custom Event | An event that is not a purchase, a cart, a refund, or a page view. Example: a product review on the e-commerce | Optional |
Custom Dimension | An object expanding the user description with related entities | Optional |
Each of the objects you import contains a certain amount of fields, also called attributes. Some of these fields are mandatory, others are recommended, and you can add more if it is useful for you.
All this data allows you to have a 360 view of your database in Splio, and it enables the following features:
planning your campaigns and finding the right customers to send them to
creating your audiences with pre-computed attributes, and exporting them to other tools
analyzing your database, audiences, and campaigns with powerful dashboards and analytics