Features / Segments

Build a reusable audience from facts your workspace can explain.

Create manual or rule-based segments from profile fields, sources, consent, and recorded activity. Preview the result before another product resolves the final audience for a specific purpose.

Example Knownry segment rule with a consent-gated membership preview.
Example record

Segment rule

Launch audience

SourceisFrontroom
Customer statusisActive
Campaign emailisGranted

Current preview

401 eligible profiles

In practice

What happens when you use it.

  1. 1

    State the rule

    Combine profile attributes, source products, consent state, or recorded activity into a readable segment definition.

  2. 2

    Preview membership

    Check who currently matches and refine the definition before the segment is used by another product.

  3. 3

    Resolve for a purpose

    When a product requests an audience, Knownry applies the required consent class to the current segment membership.

A segment in context

A useful audience remains a question, not a frozen list.

A team defines people who joined through Frontroom and completed an order in the last 90 days. Membership updates as the underlying records change, then campaign consent is checked when PostDesk resolves the audience.

Definition
Source + recent activity
Membership
Evaluated now
Permission
Checked at resolution

The record

What Knownry keeps

  • The segment name, mode, and current definition
  • Versioned rule changes or explicit manual members
  • The profile facts and activity available to evaluate membership
  • The consent class applied when an audience is resolved

Why that record matters

Segments change as profiles change. Keeping a readable definition makes that movement understandable and lets each consuming product ask for an audience under the right consent purpose.

The line Knownry does not cross

A segment describes who matches a rule. It is not permission to contact them, and Knownry applies consent again when the audience is resolved.