Target population limitation
Actito lets you apply an additional filter to limit the number of profiles finally retained in an already-defined target. Located in the targeting interface, below all the blocks, this filter is off by default.
This filter is available in all uses of the targeting interface, except when the targeting is used to feed a segmentation.
Once the filter is enabled, you have four options.
A maximum number of randomly selected profiles
You define the absolute number of profiles you want in the target; Actito picks them randomly from among all the profiles meeting your targeting conditions.
If the final target contains fewer profiles than the maximum you set, it simply means there were fewer profiles matching your conditions.
A percentage of the population meeting the conditions
You define the percentage of the profiles matching your conditions that you want to retain; Actito picks them randomly from among them.
Since this percentage applies to a population that changes over time, the total number of profiles may differ between an estimate made today and the campaign sent a few days later.
A number of profiles selected on a specific criterion
You define the absolute number of profiles you want and select them based on a specific criterion. You can thus retain the "most recent", "least recent", "first" or "last" profiles, based on a numeric or date attribute, taken from the profile table or from a linked-data table related to it.
Only linked-data tables with a 1-1 relationship (one data entry corresponds to one profile) are available. Data from Interaction tables is not accessible.
In practice, Actito sorts all the profiles matching your conditions by the chosen attribute, then retains the first ones up to the defined number. If several profiles share the same value, the choice is made randomly among the last selectable profiles. The sort direction determines what "first" means:
| Sort | By date | By numeric / integer | By profile age* |
|---|---|---|---|
| Ascending | from oldest to most recent | from smallest to largest | from youngest to oldest |
| Descending | from most recent to oldest | from largest to smallest | from oldest to youngest |
*Sorting by age is only available if the "BirthDate" attribute exists in the table.
Examples
Case 1 — The X most recent clickers. To target the last X profiles who clicked in one of your email campaigns: set the maximum number, select the last email click attribute of the "Profile" table, and sort in descending order. → You obtain the X profiles who clicked most recently.
Case 2 — The X first registrants. As part of an acquisition drive, to congratulate the first contacts who reacted: set the maximum number, select the creationMoment (creation time) attribute of the "Profile" table, and sort in ascending order. → You obtain the first X profiles (from your targeting) registered in your database.
Case 3 — Your X biggest customers. With a linked-data table "Aggregate" storing the profile's yearly turnover: set the maximum number, select that attribute of the "Aggregate" table, and sort in descending order. → You obtain the X profiles (from your targeting) with the highest yearly turnover.
A percentage of profiles selected on a specific criterion
This option works exactly like the previous one — same sort logic, same attribute types, same examples — but on a percentage of the target population instead of an absolute number. The same constraints apply (linked-data tables in a 1-1 relationship only, Interaction tables excluded; see Understanding the different types of tables).
As with any percentage-based limit, the final number of profiles may vary over time, since the population matching your criteria evolves on its own.