Segments

Segments let you save reusable audience logic instead of rebuilding the same recipient filters every time you send. Use them when you need to define who should qualify for a newsletter or campaign, inspect membership trends over time, or troubleshoot why certain contacts are included or excluded. See the email segmentation and audience builder for the broader product capabilities behind these workflows.

Before you start

• Make sure the contact data you want to target already exists in Contacts.
• Create any missing fields in Workspaces -> Data -> Fields before building filters that depend on them.
• If you use tags to organize related segments, review Workspaces -> Data -> Tags first.

Manage the segments list

Open Segments from the main dashboard sidebar to reach the saved segments table.

From this screen you can:

• search for a segment by name
• filter the table by assigned Tags
• review each segment’s contact count
• click Segment in the top-right corner to create a new segment
• open the row actions menu to view, edit, or delete a segment

Each row also shows the segment description when one exists, which makes it easier to separate operational segments from campaign-specific or temporary audience groups.

Create a segment

Build segment rules

When you open a segment, the Overview tab contains the segment filter builder.

The builder supports nested logic with:

• AND groups, where all rules must match
• OR groups, where any rule can match
• additional nested groups when one level of logic is not enough

You can reorder rules inside a group and add more groups as the segment definition becomes more specific.

Available rule types

Leadpush supports several kinds of segment conditions.

Attribute rules

Use attribute rules when membership depends on contact fields such as email, phone, first_name, or custom workspace fields. These rules support text comparisons, numeric comparisons, existence checks, list-style matching, and date or datetime comparisons.

Examples:

• email starts with a company prefix
• loyalty_points is greater than a threshold
• last_seen_at is after a specific date
• signup_date is between two dates

Filter JSON fields

JSON fields can be filtered without writing a raw dot path. Select the JSON field, choose Has property, and enter each property name in the order Leadpush should traverse it. Property names are preserved exactly, including numeric names such as 6.

For this contact value:

{
  "preferences": {
    "6": "weekly"
  }
}

Build the rule as preferences -> Has property -> 6 -> Text -> Equals -> weekly.

Choose Object property as the value type to continue into another object. For example, shopper_history.location.city can be built as:

1. Select shopper_history.
2. Add the location property.
3. Choose Object property.
4. Add the city property.
5. Choose Text, then select an operator and value.

Choose Array items when a property contains an array. JSON array rules match when at least one item satisfies the condition. Arrays can contain scalar values or objects:

• stores_visited can match when at least one text item equals Toronto.
• orders can match when at least one object has an amount greater than 100.

Each JSON rule can traverse one array. After entering an array, choose Object property to filter a property inside each item.

For JSON timestamps, choose Date or Datetime. Leadpush accepts ISO-8601 strings and supports the same absolute and relative date comparisons available for regular date fields. Values that cannot be parsed as dates do not match date comparisons.

Exists requires the selected property to be present and non-null. Doesn't exist matches either a missing property or a null value.

Subscription rules

Use subscription rules when you want to match either:

• subscribed contacts
• unsubscribed contacts

This is useful when a send should only target currently eligible recipients or when a team is auditing records that opted out.

Event rules

Use event rules when a segment should depend on custom contact events. You can:

• check whether an event happened
• check whether an event did not happen
• require an event count
• add property filters against event payload fields
• limit the rule to a recent time window

This works well for product or lifecycle audiences such as contacts who triggered a named event in the last 30 days.

Message rules

Use message rules when the audience depends on email behavior. These rules can target contacts based on message activity such as:

• delivered
• opened
• clicked
• clicked a specific URL
• bounced
• complained
• unsubscribed

You can scope the rule to any email activity or to a specific message record, and you can optionally add a recent time window.

Segment membership rules

Use segment membership rules when one segment should depend on another, such as:

• is in segment
• is not in segment

This is useful for building exclusion audiences and layered targeting logic without recreating the same base conditions.

Review a segment after saving

After a segment is created, the detail page shows:

• the segment name
• optional description
• any assigned tags
• an actions menu for Edit and Delete Segment

The detail view is split into two tabs.

Overview

The Overview tab contains the filter builder where you save and refine the segment logic.

On larger screens, the right sidebar also shows:

• Membership, an area chart of total contacts in the segment over time
• Membership Change, a chart showing contacts added and removed over time

If the segment is being recomputed, the charts show a recomputing state until the updated membership is ready.

Contacts

The Contacts tab shows the current contacts in the segment and includes a count in the tab label. From this table you can:

• search the current members
• sort by name, email, phone, subscription, or created date
• open any contact record
• edit, subscribe, unsubscribe, or delete a contact from the row actions

Edit or delete a segment

Use the actions menu on the segment detail page or in the segments table when you need to:

• rename the segment
• update its description
• change tags
• remove the segment entirely

If you edit the filter rules, Leadpush recomputes the segment membership so the saved audience reflects the new logic.

Best practices

• Name segments after the audience meaning, not just the current campaign using them.
• Add descriptions for segments that other teammates are likely to reuse.
• Use tags to separate evergreen segments from temporary campaign audiences.
• Build base audiences with one segment, then reference them from other segments when you need layered logic.
• Check the Contacts tab after changing rules so you can confirm the updated audience still matches your intent.
• Keep field names and event names consistent across imports and API integrations so segment rules stay reliable.

Troubleshooting

Related guides

• Contacts
• Newsletters
• Campaigns
• Fields
• Tags