Skip to main content

Segments

Segments are groups of people in your workspace defined by shared attributesA key-value pair that you associate with a person or an object, like a person's name the date they were created in your workspace, or a company's billing date. You can use attributes to target people and personalize messages. and eventsSomething that a person in your workspace did. Events can trigger campaigns, add people to segments, etc, and you can use properties from events to personalize messages.. Use segments to build targeted audiences, trigger campaigns, and measure outcomes over time.

How it works​

Segments connect your data to your messaging workflows:

  1. Your data comes in: people are created and updated through imports or integrations (including identify and track).
  2. Rules evaluate membership: data‑driven segments automatically add or remove people when they match (or stop matching) your criteria.
  3. Segments power messaging:
    • Campaign triggers: start a campaign when someone enters or leaves a segment.
    • Broadcast audiences: send a one‑time message to people in a segment.
    • Goals and reporting: measure when people enter/leave a segment as conversions.

If you’re not sure what data is available yet, check your workspace’s Data Index to see recently received attributes and events.

Before you begin​

Segments work best when you have:

  • Stable identifiers: people are consistently identified (for example by external ID or email).
  • Useful attributes: profile data like created_at, plan_name, or is_active (see Attributes).
  • Meaningful events: actions like signup, order_completed, or pricing_viewed captured by your sources.

Segment types​

Conviso supports two segment types.

Data-driven segments update automatically based on the rules you define.

  • Join/leave behavior: people join when they match your conditions and leave when they no longer match.
  • Best for:
    • Lifecycle stages (new, active, at‑risk)
    • Behavioral targeting (visited pricing, abandoned cart)
    • Value‑based targeting (high LTV, paid plan)

Manual segments​

Manual segments are static lists that you manage directly.

  • Join/leave behavior: people only change membership when you add/remove them.
  • Best for:
    • Event attendee lists
    • Beta tester cohorts
    • Temporary suppression/exclusion lists

Create a segment​

Create a data-driven segment​

  1. Go to Segments and click Create Segment.
  2. Choose Data-driven.
  3. Add a name (and optional description).
  4. Build your rules using one or more conditions.
  5. Click Save.

People will begin joining/leaving as their profiles and events match the rules.

Create a manual segment​

  1. Go to Segments and click Create Segment.
  2. Choose Manual.
  3. Add a name (and optional description).
  4. Add people using one of the supported methods:
    • CSV upload (bulk add)
    • API (programmatic add/remove)
    • Workflow actions inside a campaign

Build segment conditions​

You can combine conditions using AND / OR logic to express exactly who should belong in the segment.

Person attributes​

Use attributes to describe who someone is or what state they’re in.

Examples:

  • plan_name equals "pro"
  • phone_number exists
  • lifetime_value is greater than 500
  • created_at is within the last 7 days

Attribute names are case sensitive—use consistent naming (prefer lowercase snake_case).

Events (behavior)​

Use events to describe what someone has done.

Common patterns:

  • Occurrence: has performed Viewed Pricing
  • Frequency: performed Logged In at least 5 times
  • Recency: performed Purchase within the last 30 days
  • Event properties: performed Purchase where price is greater than 100

Segment membership​

You can include (or exclude) people based on whether they are currently in another segment—useful for suppression lists or layered lifecycle logic.

Page views, screen views, and device data​

If you use Conviso’s SDKs, you can also segment based on:

  • Pages/screens visited (high intent pages, onboarding screens)
  • Device attributes like platform, app_version, or last_used

Use segments in campaigns and broadcasts​

  • Campaign triggers: use a segment trigger to start a campaign when someone enters or leaves a segment. See Triggers, filters, and frequency.
  • Broadcast audiences: send a broadcast to “people matching conditions” using segment membership. See Broadcast.
  • Goals: campaigns (and broadcasts) can treat “enter/leave segment” as a conversion. See Campaign goals.

Examples​

Segment nameExample rules
New signups (last 7 days)created_at is within the last 7 days
High value & at risklifetime_value > 500 AND has not performed Logged In in the last 30 days
Power usersperformed Created Project at least 10 times AND plan_name equals "pro"
Onboarding incompletecreated_at > 3 days ago AND profile_completed is false

Best practices​

  1. Use consistent naming: prefer lowercase snake_case for attributes and event names.
  2. Send correct data types: booleans as booleans, numbers as numbers (avoid "true" or "5" as strings).
  3. Include created_at: this enables reliable lifecycle segments like “new in last 7 days”.
  4. Keep rules intentional: avoid building segments on sensitive data you don’t need.
  5. Validate with real profiles: use a known test person to confirm that membership matches expectations before depending on a segment for automation.