Features / Sources
Keep the source beside the fact, not buried in an import log.
Knownry records which product or import supplied a profile detail, activity event, or consent change. That context stays useful long after the first sync finishes.
Identifier evidence
- Source
- Frontroom / signup-form
- Collected
- Aug 31, 2026 at 10:42
- Consent
- Marketing email granted
In practice
What happens when you use it.
- 1
Name the sender
Every authorized product identifies itself when it contributes a record or activity event to Knownry.
- 2
Keep its reference
The source's own record or event reference is stored with the Knownry record, preventing duplicate ingestion and preserving a path back.
- 3
Use the source in review
Operators can distinguish a customer-entered preference from an imported field or a product-reported event before acting on it.
A source in context
The value is useful. Its origin makes it correctable.
An imported job title and a download bought on a Frontroom page can sit on the same profile. When either is wrong, an operator can see which system supplied it and fix the record at the right source.
- Fact
- Download bought
- Supplied by
- Frontroom page
- Stable reference
- Order ID
The record
What Knownry keeps
- The source product or import that supplied the record
- The source's stable reference and ingestion time
- The profile and workspace the record was attached to
- Relevant source metadata retained for later inspection
Why that record matters
A current value answers what Knownry knows. Its provenance answers why the workspace should trust it and where to correct it when the source was wrong.
The line Knownry does not cross
Knownry records the source it was given. It does not certify that an imported claim is true simply because the import completed successfully.
Keep exploring