---
title: "Populations"
slug: "populations"
updated: 2026-04-02T22:22:21Z
published: 2026-04-02T22:22:21Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.technolutions.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Populations

A **population**is a group of records with like attributes that are assigned a common label in through population rules in the rules editor.

Populations can include person records, application records, or dataset records, and records can be included in multiple populations at the same time.

## Targeting multiple records at once with rules

Records are included in a population when they meet the criteria defined by a population rule. If a record no longer meets the criteria of the population rules, it is removed from the population upon the next update to the record.

Populations can be used in many ways in Slate:

- As filters in queries to easily return records that belong to a selected population
- As the foundation for drip marketing campaigns
- Managing user access to records

## Step 1: Creating a population

A population in Slate is just a label for a group of records. Population rules are required to define and enroll records in populations.

To create a new population:

1. Go to **Database → Populations**.
2. Select **Insert**.
3. Configure the following settings:
  - **Status**: Active
  - **Folder:**Select an existing folder, or select **Other** and enter a name for a new folder.
  - **Name**: Enter a name for the population. Displays name of the Population to appear in the [Campaigns](/docs/build-a-drip-marketing-campaign) section of Deliver and in the Populations section on the Dashboard of the person record.
  - **Scope**: Select a scope for the population:
    - **Person/Application**: Records can be added to the population by either a person population or application population rule.
    - **Person**: Records can be added to the population by a person population rule only.
    - **Application**: Records can be added to the population by application population rule only.
    - **Dataset**: Dataset records can be added to the population by a dataset population rule.
4. Select **Save**.

## Step 2: Creating a population rule

As long as a population rule is active, new records will be enrolled in the population when they meet the filter criteria of the rule. Existing records will leave the population if or when they no longer meet the filter criteria of the rule.

To create a population rule:

1. Go to **Database → Rules.**
2. Select **New Rule**.
3. Configure the following settings:
  - **Name**: Give the rule a name that corresponds to the population.
  - **Type**: Configurable Joins
  - **Category**: Records
  - **Base**: Person
  - **Rule Type**: Person Population
  - **Folder**: Select an existing folder to help keep your rules organized. Choose **Other** to create a new folder.
  - **Exclusivity Group**: Leave this blank, because records might be enrolled in multiple populations at the same time, and an exclusivity group for population rules is most likely not needed.
  - **Status**: Preview ![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/image(309).png)
4. Select **Save**.
5. In the **Filters** section, choose the criteria to define the records that should be included in the population.
6. In the **Action** setting, select the population where the rule should enroll records.
7. Select **New Query** to create a quick query (a **Quick Query** page appears in a new browser tab) to review the rule and preview the records that will be enrolled in the population.
8. If you are satisfied with the rule, return to the browser tab where you created the rule, and select **Edit**. An **Edit Details** popup appears.
9. Set **Status** to **Active**.
10. Select **Save** to return to the summary page for the rule.
11. Run a query on the rule and perform a retroactive refresh to enroll records in the population.

> [!TIP]
> ⭐ Perform the refresh outside of peak hours (for example, at the end of the business day) to avoid a rule backup.

## Population filters

The *Timestamp Days* filter on the *Population*base looks at how long a record has existed in a population.

The day a record joins a population is considered “day zero.” If a record joins a population at 11:59 PM ET today, it would be in the population for 1 day at 12:01 AM ET tomorrow; the duration doesn't count the total number of hours, but instead the number of ***unique days***.