In this article, you will find some more details on the most important terms which can be found in the Marketing Automation and Loyalty modules throughout the platform.
The action, or sending, is the part of a campaign that determines which message is sent on which channel for the defined population. A suite of multiple actions equals a scenario.
The category is a value that you can add at a campaign level (during the first step of yout campaign scenario) and can later be used within a contact filter. You can for example create filters based on behavioural criteria (such as openings, clicks and emails received from a specific campaign). A possible use case of the campaign category can be for retargeting campaigns.
Are used to display (or not) content in your email designs, based on specific conditions that your contacts match or do not match. You can refer to our dedicated article on blocks here.
A control group is a selection of contacts from the targeted recipients of an operation's campaigns that will be excluded of the targeting. This can for instance be used in the context of an ROI campaign.
Custom fields, as opposed to system (default) fields will be unique to your universe. By default a custom field can be up to 255 characters, however, we recommend to keep the lenght of the field name as short as possible and to avoid characters such "-", and spaces.
Deduplication is the process of removing all contacts duplicates to avoid creating the same action on the same contact twice. A deduplication is done on the unique key when importing contacts, and when creating a campaign's initial population.
In a loyalty program, the holding period for points prevents individuals from spending them until the holding period is over. It is a setting that helps you have better control over how points are used and spent by members. By default, the value is set to 0 and there is no holding period unless configured otherwise.
Products & store loops
Is a type of customization which can be used in your email designs when you wish to display for example several products or stores linked to a contact.
A temporary file is a contact file imported into Splio outside of the main contact table. Temparory files can be only used to include or exclude contacts in a campaign, and cannot be segmented in Target.
Are used to display products in an order or an abandoned cart within your emails in the case of a post-purchase campaign for instance. To find more information on transactional loops, you can refer to our dedicated article.
The operation code is used to group several campaigns in a report. It is an optional value that you can add during the setup of your manual and automatic campaigns.
In a loyalty program Q (qualifying) points are used to move loyalty members up & down tiers within your loyalty program(s). They are called "qualifying", because they enable members to qualify to specific tier(s).
NQ (non-qualifying) points are meant to be accumulated over time and burnt when the loyalty members select rewards and redeem them; in this case, the NQ points corresponding to the cost of the rewards will be deducted from each member's balance. They should be considered as the currency of your loyalty program.
Q points are available only in tiered programs and NQ points in both simple and tiered programs.
In target, a relative date is calculated in hours/days/weeks/months starting from an event date (ex: subscription date). It is called relative because it is moving dynamically across the date range set on. The opposite would be the "fixed date" or "calendar date".
Is the field of a table which has only unique values. Each table has a unique key in order to avoid duplicates in the database. (i.e. if the unique key of contact table is "email", you cannot have twice the same email address in your database).
A universe is an instance of Splio platform. Most clients have one universe, but you may have several universes (for example one per currency as we do not currently support multi-currencies or one per country). Note, that you will need to know your universe name to log in.
Are used to display the value of a field in a design. Variables are written with a "$" before and after the name of the field: for example: "Dear, $firstname$....".
For more details on variables, you can refer to our documentation on this topic.