Dynamic audience segmentation

Build iGaming audiences from behaviour, profile and technical eligibility.

Jurnexus Audiences combines event windows, profile attributes, application posture and saved segments in one explainable rule model. Preview who matches before the audience is used by a campaign or journey.

  • Combine AND/OR rules without SQL
  • Estimate profiles, devices and destinations
  • Explain why an individual player matches
01

Rules that match the way teams ask questions

Create nested rule groups across attributes, event presence or absence, counts, recency, device information, applications and existing segments.

  • Profile and identifier criteria
  • Behaviour within time windows
  • Application, OS and app-version posture
02

Preview before activation

Audience preview separates matching profiles from bound devices and active channel destinations. Current counts remain distinct from final action-time eligibility.

  • Estimated matching profiles
  • Bound-device and destination counts
  • Pseudonymous sample with reason trace
03

Versioned definitions for reproducible decisions

Published audience versions keep the exact rule structure used by a campaign or journey. Editing creates a new version instead of silently changing historical execution.

  • Immutable published definitions
  • Reusable exclusion audiences
  • Membership history where materialised
From design to evidence

A clear operating path for every capability.

Dynamic audience segmentation uses the same identity, versioning, decision and audit boundaries as the rest of Jurnexus.

  1. 01
    Connect

    Define sources, contracts, identity and permissions before activating data.

  2. 02
    Configure

    Build rules, content or flows and validate the result before publication.

  3. 03
    Execute

    Apply current state, idempotency and explicit routing at action time.

  4. 04
    Explain

    Inspect outcomes, reasons and evidence linked to the version that ran.

FAQ

Implementation questions.

Can this capability be introduced in phases?

Yes. Scope can begin with one use case, environment, data source or channel while retaining the contracts and boundaries required to evolve.

How is production activation controlled?

Configuration passes through validation, immutable versions and permissions. External effects use explicit connections, current decisioning and auditable evidence.

Must the current platform be replaced?

No. Jurnexus is designed as a provider-neutral engagement layer connected through approved APIs, SDKs and contracts.

A practical next step

Turn one marketing question into an explainable audience.

Bring a real segment definition and we will map its data sources, timing assumptions and destination counts.

Book a product conversation