Consent and provenance
Know where a record came from, what someone was shown when they submitted it and what happened to it afterwards. LeadScale helps you build that evidence into your data journey, so the information is available when your teams and connected systems need it.
The LeadScale Engine can bring together submission evidence, source information, timestamps, consent details and processing history to create a provenance record. That record can support your governance requirements, inform decisions during processing and accompany data into other platforms as part of a composed journey.
Build a clearer picture of each submission
A contact record in your CRM may tell you that someone opted in, but not where they came from, which form they used or what they saw when they submitted it. Those details matter when a customer asks about their information or your team needs to investigate a record.
LeadScale can capture and bring together the available evidence behind a submission, rather than leaving your team to piece it together from separate systems. Our Technical Services team works with you to decide which details are needed, where they come from and how they should be recorded and used.
Keep the audit trail as data moves
For records captured through a LeadScale programme, the Engine records source, timestamps, lineage and consent audit information. As the record passes through configured checks, enrichment, routing and delivery, audit logs can show the processing steps, decisions and system hand-offs. This creates a fuller history of its journey, not just a record of where it ended up.
That history can help your teams investigate a disputed record, understand why a decision was made or trace a delivery issue. Permissions and controlled processing support governance, while audit logs and alerting provide visibility into the activity taking place between connected systems.
Capture what the person actually saw
A consent status on its own cannot show the wording presented to someone at the point of submission.
Where a form is configured for capture snapshots, LeadScale can retain evidence of the submitted information and the form as it appeared at that moment, including relevant privacy wording or terms. This provides useful context alongside the submission timestamp and source.
Snapshot capture must be configured at the point of collection. Records received from other systems do not automatically include an original form snapshot, and we cannot recreate evidence that was never collected.
Use existing consent and provenance data in your journey
You may already hold consent preferences, suppression information or source details in a CRM, consent platform or another client-controlled dataset. We can connect those sources to the Engine so the information can be checked and applied as records move through your process.
For example, a consent preference might affect whether a record is eligible for a particular destination, while a suppression match may prevent a new acquisition record being delivered. Our Technical Services team agrees the sources, matching rules, permitted uses and outcomes with you, then configures the journey accordingly. LeadScale works with your existing consent management arrangements rather than replacing them.
Those same details can be made available to other connected platforms where the receiving system supports them and you have agreed what should be shared.
Bring existing records into the same approach
Provenance is not limited to newly captured leads. We can onboard records and supporting information from your systems, including existing CRM data, and use that information in processing checks, suppression and onward routing. The Engine can preserve the history supplied with a record and track the steps taken after it enters the journey.
The earlier history is only as complete as the evidence provided. Processing a record through the Engine does not independently prove its original source or consent, or recreate missing capture evidence.
Design provenance into a composed journey
- Define the evidence. Agree what your teams need to know about each record, from its source and submission details to consent information and later processing outcomes.
- Connect and configure. Bring in the relevant capture points and client datasets, set up snapshots where appropriate and define the rules for checking, retaining and sharing provenance information.
- Track and orchestrate. Record the processing and delivery steps, then pass the agreed provenance fields or outcomes to CRM, marketing automation and other connected systems where supported.
Provenance that supports the wider ecosystem
A provenance record can do more than answer a question about an individual submission. In a composed journey, the information can help determine the next step, support a human review or accompany a record into the systems responsible for follow-up. Across a wider ecosystem, the Engine can coordinate that information with validation results, consent rules, delivery statuses and downstream outcomes to provide a traceable view of the record’s progress.
Evidence supports governance; it does not replace legal judgement
LeadScale’s ISO 27001-certified information security management system, controlled access and audit capabilities provide a governed framework for this processing. But a form snapshot or audit trail does not, by itself, establish that consent was legally valid or that a particular use is permitted. You define the applicable requirements and rules; our team helps implement them.
Frequently asked questions
Is provenance the same thing as consent?
No. Provenance describes the origin and history of a record, including available submission evidence and the processing it has undergone. Consent information may form part of that history, but knowing where a record came from does not establish permission for every use.
Will every record have a snapshot of the original form?
No. A form snapshot is available only where that capture functionality was configured. Other records can carry source, consent or other evidence supplied by your systems, and the Engine can track what happens after receipt.
Can you work with consent information held in our systems?
Yes. We can connect to the relevant client-controlled sources and apply the information through rules agreed with you, including consent-based routing and suppression checks.
Related capabilities
- Technical data services How our team designs, configures and operates connected data journeys.
- Engine configuration How your requirements become processing, routing and audit rules.
- Ecosystem orchestration How records, provenance and outcomes move across connected systems.
You define the outcome. We compose the journey.
Build the evidence into your data journey
Tell us what you need to know about a record, where your data is collected and which systems need access to that information. Our Technical Services team can help design the provenance, processing and delivery rules around your requirements.
Or request a free audit of leads from a recent programme.