Create a segment
The Create Segment screen is where you describe an audience. You name it, add filter rules, and Netmera restates the rules in plain language and tells you how many users match before you commit.
Path: Targeting > Segments > Create Segment
Step 1: Name and describe the segment
Name
Up to 100 characters. Name it after the audience logic, not the campaign that first used it.
Description
Up to 500 characters. This is what colleagues read in the segment list before reusing it.
Step 2: Add a filter rule
Under Audience, click Add Filter Rule. The filter picker opens with categories on the left and their values on the right, and a search box for finding a value inside a long category.
The categories cover who the user is, how they can be reached, what they did, and what they are using:
Reachability
Channel Permission, Platform Permission, Advertising ID Permission, Blacklist
Who the user is
Profile Attribute, Tag, Segment, Promotion
What they did
Behavior, Response, Message Category, Location Tracking, App Tracking (Android Only)
What they use
Platform, Device Type, Device Model, Device Count, Operating System, App Version, App Installation, Installation Source, Android Provider, Operator
A filter can only match on data Netmera already holds. A Behavior rule needs the event to be tracked, a Profile Attribute rule needs the attribute to be collected, and a location rule needs users whose location has been recorded. When a rule you expect to work returns nobody, check the data behind it before rewriting the logic.
Step 3: Shape the rule
Each rule appears numbered inside a group. A behavior rule reads left to right as a sentence — for example Did / Open App / more than / 0 / in the last / 30 / Day.
The count and the time window are what make the rule specific. More than 0 times in the last 30 days is “did it at all, recently”; raising the count turns it into a frequency rule, and shortening the window turns it into a recency rule. Both change the audience far more than most people expect — adjust one at a time and recalculate.
Two refinements are available on behavior rules:
+ attribute filter — narrows the event by one of its attributes, as attribute / operator / value. Add more than one when the event needs several conditions.
Apply time restriction and Apply location restriction — limit when and where the behavior counts.
Time restriction
Select the weekdays the behavior must fall on, and optionally a start and end time. Use it for rules like “opened the app on a weekday during business hours”.
This filters the moment the behavior happened, not the moment a message goes out. Send timing belongs to the campaign, not the segment.
Location restriction
Enter a latitude, longitude, and radius in kilometers, or find the place on the map and let the coordinates fill in. Use it for rules like “triggered this event within 5 km of a store”.
Only users whose location was recorded with the event can match, so the audience is naturally smaller than the same rule without the restriction.
Step 4: Combine rules with AND / OR
Rules live inside a group, and the group's operator decides how they combine:
AND — a user must match every rule in the group. Each rule narrows the audience.
OR — a user matching any one rule qualifies. Each rule widens the audience.
When the logic needs both operators, click Add Filter Group and put the alternatives in their own group. For example, buyers from either of two cities:
Group A (AND) — Behavior: purchased in the last 30 days
Group B (OR) — Profile Attribute: City is Istanbul / Profile Attribute: City is Ankara
A rule is removed with the bin icon on its row; a whole group with the bin icon on the group header.
Step 5: Check the audience before saving
The right side of the screen answers two questions while you build:
Rule Description restates the rules as sentences, grouped the way you built them — for example Behavior Did Open App greater than 0 times in the last 30 day. Read it back before saving; it is the fastest way to catch a rule that does not say what you meant.
Audience size shows Number of Users. It stays empty until you ask for it — click Calculate exact size to run the count against the current rules.
The count is a snapshot of the rules as they stand. Change a rule and it no longer applies — recalculate before drawing a conclusion from it.
Step 6: Export or save
Export audience — exports the users matching the current rules without saving the segment. The export runs in the background and the file is emailed to you.
Save — stores the segment and returns to the list, where it calculates and then shows as Ready.
Cancel — discards the definition.
After saving, the segment appears in the list as Calculating and becomes Ready once the audience is resolved. It is selectable in campaign targeting, journeys, and analytics filters from that point on — see Segment details for the full view of one segment.
Before you save
Does Rule Description match the audience you intended to describe?
Are AND and OR in the right places — and does anything need its own group?
Is the calculated size plausible? A count of zero usually means contradictory rules in an AND group.
Do the time and location restrictions really belong, or do they narrow the audience more than intended?
Will a colleague understand this segment from its name and description alone?
Example recipes
Recently active users
Group A (AND)
Behavior — Did Open App more than 0 times in the last 30 days
Reachable by email
Group A (AND)
Profile Attribute — Email exists
Channel Permission — Email
Engaged buyers on one platform
Group A (AND)
Behavior — Did Purchase more than 0 times in the last 30 days
Platform — iOS
Last updated
Was this helpful?