Player 360 profiles with identity, consent, devices and interaction history.
Jurnexus Profiles creates a pseudonymous operational view of each player while preserving source, assurance and time. It connects anonymous behaviour only through explicit identity evidence and never treats browser activity as transactional truth.
Connect anonymous sessions, authenticated player identifiers and native installations through explicit, tenant-scoped bindings. Playtech can be one identity provider without becoming the permanent data model.
Pseudonymous stable player identifier
Audited merges and unbinds
No account mixing on shared devices
02
A current view with source-level evidence
Attributes, audiences, consents and technical destinations show when and where they were last updated. The timeline links events to campaign and journey decisions.
Attribute provenance and freshness
Current audience memberships
Campaign, delivery and journey history
03
Mobile installation and destination posture
Associate multiple iOS, Android and web destinations with the correct player. App version, operating system, locale and push destination lifecycle support segmentation and delivery diagnostics.
Multiple devices per player
Application and version metadata
Active and invalid destination states
From design to evidence
A clear operating path for every capability.
Unified player context uses the same identity, versioning, decision and audit boundaries as the rest of Jurnexus.
01
Connect
Define sources, contracts, identity and permissions before activating data.
02
Configure
Build rules, content or flows and validate the result before publication.
03
Execute
Apply current state, idempotency and explicit routing at action time.
04
Explain
Inspect outcomes, reasons and evidence linked to the version that ran.
PA
ILLUSTRATIVE PROFILEplayer_•••91F2 Active now
Identity assuranceServer verifiedCurrent audiences6 activeBound devices2 verifiedJourneys in motion3 active
Live interaction timelineLatest explainable moments
Game category explorednow
Audience membership updated6m
Journey condition evaluated10m
Mobile action authorised14m
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.