Segments

A segment is a reusable audience definition. You describe who belongs to it with filter rules — behavior, profile attributes, tags, message responses, platform, location — and Netmera keeps working out which users match.

Once a segment exists, you select it by name wherever an audience is needed: campaign targeting, journeys, and analytics. The rules live in one place, so a change to the definition reaches every campaign that uses it.

Path: Targeting > Segments

Segment types

The list holds every segment in the app, whatever created it. The type filter separates them:

Type	Where it comes from
Standard	Built by hand from filter rules on the Create Segment screen.
Predictive	Generated by an AI model that scores users on how likely an event is.
Product	Built around product or catalog data.
Connector	Synced in from an external tool through a connector.

Start here (most-used topics)

What you want to do

Browse, filter, and manage the segment list

Open

Segment list

What you want to do

Build a new segment from filter rules

Open

Create a segment

What you want to do

Inspect one segment and its audience

Open

Segment details

What you want to do

Import or sync segments through connectors

Open

Connector segments

What you want to do

Predict who will convert or churn (AI-based)

Open

Predictive segments

Quickstart: build a segment you can target

1

Start from the question you want to answer

Examples:

• “Who opened the app in the last 30 days?”

• “Who has an email address on file?”

• “Who added to cart but did not purchase?”

2

Click Create Segment

Name the segment and describe what it is for. The description is what the next person reads before reusing it.

3

Add filter rules

Pick a filter category, then the value. Combine several rules in a group with AND or OR, and add more groups when the logic needs nesting.

4

Check the audience before saving

Rule Description restates your rules as sentences, and Calculate exact size returns the real number of users the rules match.

5

Save and use it

Saved segments are selectable in campaign targeting, journeys, and analytics filters.

How a segment stays current

A segment stores rules, not a fixed list of users. The membership is resolved by calculation, so the number you see is the result of the last run rather than a live count.

• Update Date in the list tells you when that run happened.

• Refresh forces a new calculation when you need the audience to reflect something that just changed.

• Pause stops recalculation and moves the segment to Not Active. The definition is kept, so resuming picks up where it left off.

This is why a rule change reaches every campaign using the segment: campaigns reference the segment, and the segment resolves to users at calculation time.

Key concepts

• Filter rule — one condition, such as a behavior, a profile attribute, or a channel permission.

• Filter group — a set of rules joined by AND or OR. Groups are what let a segment mix both operators.

• Rule Description — the plain-language restatement of the rules, shown while you build.

• Audience size — the number of users matching the rules, on demand rather than continuously.

• Reachability — how many of those users can actually be reached on each channel.

• Tags vs segments — tags are static labels you attach to users; segments are rules that resolve to users.

Related: Tags.

Related prerequisites

Segments can only filter on data Netmera already holds. Before a rule can work, the underlying data has to exist:

• Behavior and Response rules need tracked events — see Events.

• Profile Attribute rules need attributes collected on the user — see Profile attributes.

If a rule returns nobody, the data behind it is the first thing to check.