Audiences (New Builder)

Build audiences with the redesigned Lytics audience builder

📘

New audience builder

This page documents the new audience builder, which replaces the legacy builder being sunset on May 4, 2026. The original Audiences page still covers the legacy builder until then. After the legacy builder is retired, this page becomes the canonical audiences doc.

Introduction

Audiences are central to creating personalized marketing using Lytics. They group users who share characteristics so you can target them in campaigns, personalize experiences, export to downstream tools, and explore user behavior. Audiences stay up to date automatically — as users' behavior changes, they join or leave audiences in real time.

The redesigned audience builder keeps all your favorite features from the legacy builder — live audience size preview, sample profiles, groups, Expires After — with a more modern feel, and consolidates rule creation into two tabs: Attribute and Audience. New in this builder:

  • Geolocation rules — define audiences based on user location (country, region, city, radius-from-point).
  • Enable for Personalization toggle — replaces the legacy "API Accessible" checkbox.

Access the audience builder from the left navigation: Using Profiles → Audiences, then click + Create Audience.

Audiences index page

Creating a New Audience

An audience consists of two parts: details (name, description, configuration) and a definition (the rules that decide who belongs).

Audience Details

The top of the builder collects metadata about the audience.

Audience details — Name, Description, Groups, Slug, Expires After, Access
FieldRequiredPurpose
NameYesHuman-readable name shown across the Lytics UI.
DescriptionNoOptional longer explanation of what the audience targets.
GroupsNoAssign to one or more groups for organization. Groups are managed from the Audiences list page.
SlugNoA unique, URL-friendly identifier used when referencing this audience via APIs or SDKs. If left blank, one is generated from the name.
Expires AfterNoOptional expiration date. The audience is deactivated on this date. Note: if a downstream dependency (export, campaign, other audience) uses this audience, expiration will fail.
Access: Enable for PersonalizationNoWhen on, the audience is surfaced by the personalization API and available to Experiences, Pathfora, and tag-based personalization. Leave off for audiences used only in exports or internal reporting.
📘

Naming tip

A Lytics account often ends up with dozens or hundreds of audiences. Use a consistent naming convention — a common prefix per campaign or category (e.g. Holiday Promo: Tech Lovers, Holiday Promo: Loyal Shoppers) keeps related audiences grouped together in the list and easier to find.

Defining Rules

The Definition section is where you specify which users belong to the audience. Every audience has at least one Rule set containing one or more rules.

Each rule is configured through the Configure rule panel, which offers two tabs:

  • Attribute — build rules based on user profile fields (the most common case).
  • Audience — reference another existing audience as a building block.

As you add and edit rules, the This audience panel on the right updates in real time with the current user count and percentage of total users. The Sample Profiles panel shows a preview of matched users.

Attribute Rules

The Attribute tab lets you build rules on any user profile field.

Attribute tab with field list

Filter the field list to find the right field:

FilterWhat it does
Search for a FieldText search against field names.
SourceLimit to fields from a specific data stream.
CoverageLimit to fields populated on at least X% of profiles, so you don't build rules on sparsely-populated fields.

Click a field to open its configuration, choose an operator and value, then click Add rule. Numeric fields show a histogram of value distributions and a table of sample values you can pick from.

Configuring a numeric rule — Total Number of Visits, with operators and value distribution

Rules work differently depending on the field type — see User Field Types below.

Audience Rules

The Audience tab lets you use an existing audience as a rule. This is the replacement for the legacy "Existing Audience" tab.

Audience tab showing existing audience selector

Filter with:

FilterWhat it does
Search for an AudienceText search against audience names.
Audience TypeLimit by type (All, Behavioral, Characteristic, etc.).
Audience GroupLimit to audiences in a specific group.

Select an audience to add it as a rule.

📘

Content Affinity and Topics

Content Affinity no longer has a dedicated tab. Affinities, Topics, and related interest signals appear in the Attribute tab alongside other user fields — search by the Affinity or Topic name to find them. See Affinities and Topics for how interest data is modeled.

📘 Geolocation rules

The new builder adds geolocation fields (country, region, city, radius-from-point) in the Attribute tab. Search for geo or the specific field name to find them.

User Field Types

How you configure a rule depends on the type of the user field. Expand the sections below for the supported operators and UI behavior of each type.

Numeric User Fields

Numeric field rule configuration

Numeric fields (e.g. Total Number of Visits, Total Pageview Count) support these operators:

  • equals — exact match
  • is greater than / is at least — minimum thresholds
  • is less than / is at most — maximum thresholds
  • equals one of — match any of a list
  • exists — include everyone with a value

The value distribution bubble chart shows which values are most common across your user base; click a bubble or select from the Selected/Value/User Count table to pick a value. Use View sample values to inspect matching profiles before saving.

Text User Fields

Text field rule configuration

Text fields (e.g. First Name, Last Visit City) support these operators:

  • equals — exact match (case-sensitive)
  • contains — substring match anywhere in the value
  • is like — pattern match with * as a wildcard (e.g. test* matches "testing", "test" matches "my test case")
  • equals one of — match any of a list of values
  • exists — include everyone with a non-empty value

Pick a value from the bubble chart or the sample values table, or type one into This Value. The bubble chart sizes values by user count.

Date User Fields

Date field rule configuration

Date fields (e.g. Time of First Visit, Time of Last Visit, Created Timestamp) support these operators:

  • is after — match values after a given date
  • is before — match values before a given date
  • is between — match values within a date range
  • exists — include everyone with a non-null date

Pick Relative Date for windows that slide with "now" (e.g. visited in the last 7 days), or Specific Date for fixed points in time (e.g. created after 2024-01-01). Relative dates come with shortcuts for 1 day, 7 days, 30 days, 90 days, and 1 year in either direction (in the past / in the future).

Set User Fields

Set field rule configuration

Set fields (e.g. Web Domains Visited, All URL Paths Ever, Followed Sports) collect multiple values per user over time. Operators:

  • contains — match users whose set contains the given value
  • is like — wildcard match with *
  • equals one of — match users whose set contains any of a list of values
  • exists — include everyone who has any value in the set

Tick values in the sample list to include them, or type into These Values to supply your own. The Set type: []string pill at the bottom tells you the element type of the set.

Map/Nested User Fields

Map field — selecting a key

Map fields (e.g. Web Events By Hour, Events By Device, Signup Date for Event) store values grouped by a key, giving you a two-step rule:

  1. Search for a key — pick which slice of the map the rule operates on. For Web Events By Hour the keys are hours (0–23); for Events By Device the keys are device types; etc.
  2. Condition — once a key is picked, the rule becomes a condition on the value at that key, using the operators appropriate to the value type (numeric, string, date). The Map type: map[string]intsum pill at the bottom tells you the key type and value type.

Use Map Exists (No Key Needed) to match users who have any entry in the map, regardless of key.

Combining Rules

A Rule set groups one or more rules with a shared connector (AND or OR) and a shared Include/Exclude disposition. An audience can contain multiple rule sets, which are themselves combined with AND or OR — this lets you express precise logic like "(visitors from US AND engaged last 7 days) OR (known email AND abandoned cart)".

AND: users must match every rule

By default, additional rules are joined with AND — users must match all rules in the set. The connector toggle between rules shows "and" (grey).

Two rules combined with AND

OR: users must match at least one rule

Click the connector toggle between rules to switch to OR — users match if they satisfy either rule. The audience size updates in real time.

Two rules combined with OR
📘

The connector applies to the whole rule set — you can't mix AND and OR within a single set. To combine both, split into multiple rule sets.

Included / Excluded: invert a rule

Each rule has an Included / Excluded toggle on its right side. When a rule is Excluded, users who match the rule are kept out of the audience.

Rule toggled to Excluded

The same toggle exists at the rule-set level. Excluding a whole rule set removes everyone who matches it from the final audience.

Adding another rule set

Click + Add rule set below the existing set to start a new set. Rule sets are combined with AND or OR using the same connector pattern. Use rule sets to express logic that can't fit in a single flat list of rules.

Saving the Audience

Click Save at the bottom of the builder. Save is disabled until the audience has a Name and at least one valid rule in the Definition.

After saving, you land on the audience's summary page.


Managing Audiences

The Audiences list page lets you browse, search, filter, group, edit, and delete audiences.

Audiences list page

Browsing and Searching

The list has a Search box that fuzzy-matches against audience names and slugs, and sortable columns for:

ColumnWhat it shows
NameHuman-readable name with the slug rendered below in code style.
SizeMost recent user count (refreshed periodically — not real-time).
Last ModifiedWhen the definition was last changed.
APIWhether the audience is exposed via the personalization API (the Access: Enable for Personalization toggle).
ManagedLytics-managed prebuilt audiences are flagged here.
Download CSVTrigger a CSV export of the audience's users.

Click any column header to toggle sort. Pagination controls sit below the list; use Show All to disable pagination.

Groups

Groups organize audiences into logical buckets. The right-hand Groups panel lists built-in groups plus any custom groups you've created.

Groups panel

Built-in groups Lytics computes automatically:

  • All — every audience in the account.
  • Interest Audiences — audiences built on content-affinity rules.
  • Lookalike Audiences — audiences generated from the Lookalike Models feature.
  • My Audiences — audiences you've created or edited recently.
  • Recently Created — audiences added in the last 7 days.
  • Recently Updated — audiences whose definitions changed in the last 7 days.
  • Unused — audiences not referenced by any export, campaign, or other audience.

Creating a custom group

Click the + next to Groups to create a custom group, give it a name, and save.

Adding audiences to a group

There are two ways to add audiences to a group:

  1. From the audience builder — set the Groups field while creating or editing the audience.
  2. From the list — select audiences via checkbox, click Select an action, and choose Add to Groups. Pick the target group(s) to apply.

Editing or deleting a group

Hover the group name in the Groups panel to reveal the edit (pencil) and delete (trash) icons. Deleting a group removes the group assignment from its audiences — it does not delete the audiences themselves.

Audience Summary

Click any row in the Audiences list to open the audience's summary page. It shows the audience name, ID, slug, created/updated dates, API access status, and the Export / Edit / ⋯ actions.

Audience summary page

Four tabs below the header give different views of the audience:

  • Metrics — headline user count and audience share, plus an activity graph of audience size over time. Useful for spotting growth from a campaign or a sudden drop after a rule change.
  • Details — exports and jobs currently using this audience, plus a sample of recent users you can drill into.
  • Characteristics — a breakdown of who's in the audience by behavior, web activity, content affinity, and campaign interactions. Helpful for sanity-checking whether the rules are catching who you expected.
  • Logs — recent events on the audience: creation, edits, sync runs, and errors.

Editing an Audience

From the summary page, click Edit to reopen the audience in the builder. Make changes, then Save. Edits are picked up by downstream exports on the next refresh.

Duplicating an Audience

From the summary page, click the ⋯ menu and choose Duplicate. You'll get a new audience with the same definition; adjust the name and rules as needed.

Summary page options menu (Duplicate / Delete)

Deleting an Audience

Deleting a single audience

From the summary page of the audience you want to delete, open the ⋯ menu and choose Delete. You'll be asked to confirm.

Deleting multiple audiences

Tick the checkboxes on the rows you want to remove. A blue action bar appears at the bottom showing the selection count.

Audiences list with two audiences selected

Click Select an action, then Delete Audiences. You'll be asked to confirm, and Lytics will check for downstream dependencies before deleting.

Batch action menu — Add to Groups / Remove from Groups / Delete Audiences
📘

If any of the selected audiences are used by an active export, campaign, or another audience, Lytics prompts you to choose between deleting the dependents as well or skipping the deletion.


Activating Audiences

Audiences can be activated in several ways: