This section contains a description of the basic mechanisms for implementing a loyalty program using the Sailplay marketing automation platform.
This guide is a compilation of the integration algorithm with links to the relevant Sailplay API methods.
For all questions related to integration, it is recommended to contact [email protected], as well as to your assigned account manager
Data flow with Sailplay is performed through the REST API integration. Numerous API methods are available via HTTPs requests through a backend-to-backend integration.
Sailplay uses several basic concepts, which form the basis of the entire integration:
Client
Customer account in the Sailplay system. The user ID can be a phone, email, and/or origin_user_id (the user ID in your system).
Tags
Each client can be assigned an arbitrary number of tags. Tags can be perceived as labels that are attached to the user when performing certain actions: registration (the “Registration” tag), filling out the profile (the “Filled the profile” tag). Tags can represent any user characteristics (gender, age, interests, fields from your database, etc.). Tags can be assigned both from the backend and from the frontend. Some of the tags are added automatically (for example, “The email “Email title” was sent to the user”, “The user opened the email “Email title”, etc.). Tags are used for:
- targeting of bulk campaigns;
- launch of triggered scenarios;
- discounts and processing;
- analytics;
- segmentation.
Departments
A department is any constituent (or logical) part of a business. A department can represent a store, warehouse, region, a subdomain of the e-commerce platform, entire e-commerce platform, or any other point of sale. Accordingly, store_department_id is the identifier (ID) of the partner's department in the SailPlay system.
Purchase
An object that contains the contents of a customer's order or purchase with additional characteristics such as promotional codes, payment or delivery method, and customer identification.