Consent and provenance
When someone asks where you got their details, you need more than the contact record in front of you. LeadScale keeps information about where records came from and how they were processed, with evidence of the form submission where that recording is set up.
The LeadScale Engine™ records source, timestamp, lineage and a consent audit trail for records captured through a programme. On forms set up to capture a snapshot, it also records what the person submitted and what the form showed at that moment. Consent information held in client systems can be brought into the Engine and applied through configured rules.
What was the person shown?
Your CRM may record that a contact opted in. If that person later questions it, your team needs to understand how the status was recorded: which form they used, when they submitted it and what wording they saw.
The status and the details of the submission answer different questions. Keeping both gives the team more to work with when it reviews the record.
Follow the record from capture to delivery
For records captured through a LeadScale programme, the Engine records the source, timestamp, lineage and consent audit trail. Lineage is the record’s path from its source through processing. Audit trails continue through delivery.
If a buyer questions a record’s origin, this history provides the source and the route through the programme. The contact details alone would not tell the receiving team how the record reached them.
Keep evidence of what was on the form
A record may show that someone submitted a form without showing the wording presented at the time.
On forms set up for capture snapshots, LeadScale records the submission and what the form showed, including the privacy policy or terms present. A later review can refer to evidence from the submission itself.
This recording needs to be in place on the form. Records arriving through other routes do not automatically have a snapshot.
Put the consent information you already hold to use
Consent information in your CRM or consent platform may need to affect how a programme handles a record. The technical work brings that information into the Engine so it can be used during processing.
The Engine can take in supplied consent information and apply it through rules agreed for the programme, alongside screening against consent and suppression data. It works with the consent information in your systems; LeadScale does not provide a replacement consent management platform.
For how the technical team turns those requirements into processing rules, see the Engine configuration page.
What about records you already hold?
A file from your systems may already contain source and consent information. The programme can keep that supplied history and record what happens after receipt.
What you can show about the earlier period depends on the evidence supplied with the data. Passing a record through the Engine does not recreate its original submission or verify that earlier history.
Connect the sources, evidence and rules
- Establish where records and consent information come from. Identify the capture points and the client systems supplying data to the programme.
- Set up the recording and processing. Configure provenance recording, capture snapshots where required, and the rules that apply supplied consent information.
- Retain the trail through delivery. Keep the origin and processing information with the programme’s records as they move into the receiving systems.
More context when a record is questioned
When a record is questioned, your team has its recorded source and processing history to examine. Where the form was set up for snapshots, there is also evidence of the submission. That makes it possible to distinguish what was recorded at capture from information supplied later.
Capture evidence has a defined purpose
A snapshot records what happened at capture. It does not, on its own, establish valid consent or determine whether a particular use is permitted. The Engine applies the programme’s configured rules; it does not make that legal judgement.
Frequently asked questions
Is provenance the same thing as consent?
No. Provenance concerns where a record came from and its history. Consent information is part of the context a programme may hold and apply. Knowing the source alone does not establish what someone agreed to.
Will every record have a snapshot of the original form?
No. A snapshot is available where that capture functionality was implemented. Records supplied through other routes may carry different supporting information.
Can you work with consent information held in our systems?
Yes. The Engine can take in that information and apply it through the rules specified for the programme. The technical data services page describes how the connections retrieve information from your systems.
Explore related pages
- Technical data services— how the technical team connects your systems to the Engine.
- Engine configuration— how requirements become processing rules.
- Deduplication and suppression— repeat-response rules and exclusions using client data.
What do you need to know about a record?
Bring the questions your team needs to answer, the places you capture data and the systems holding your consent information. We can work through what the programme needs to record and apply.