Features / Profiles
See one known person without erasing where each detail came from.
A Knownry profile brings together the identifiers, attributes, consent, and activity your workspace already has. The underlying source records remain available when somebody needs to check the match.
Sam Rivera
Profile KN-1842
Product reference
customer_2048
Source: connected product
Merge history retained
The match rule and both source records remain available for review.
In practice
What happens when you use it.
- 01
Receive a known identifier
An import or authorized product supplies an email, phone number, or product reference with its own source attached.
- 02
Match by a stated rule
Knownry normalizes the identifier and connects it to a profile only through the workspace's defined identity rules.
- 03
Review the whole person
Open the profile to see its identifiers, sources, consent state, segments, and activity without jumping between product databases.
A profile in context
One person, three records, no mystery merge.
A signup from Frontroom and an order from a connected product share the same declared email. Knownry can place both on one profile while keeping the signup, order, and match operation separately inspectable.
- Matched on
- Declared email
- Sources retained
- Frontroom + product
- Review path
- Profile → source record
The record
What Knownry keeps
- The profile status and workspace that owns it
- Each normalized identifier and its source product
- Profile attributes with the source that supplied them
- Merge and split operations that changed the profile
Why that record matters
Two systems can know the same email for different reasons. Keeping the profile and its source records together lets the team use a shared identity without pretending every fact came from the same place.
The line Knownry does not cross
Knownry resolves declared identifiers. It does not fingerprint anonymous visitors or buy outside identity data to fill gaps.
Keep exploring