Capturing consented data from your audience
Build the record history at the point of registration. LeadScale's Engine captures source and consent audit information with each record it creates, and applies the checks and repeat rules agreed for your audience programme.
The LeadScale Engine™ records source labels, timestamps, lineage and a consent audit trail when it creates audience records. Agreed contact checks and repeat controls can also run before onward delivery. Together, these mechanisms provide capture history and processing evidence for assessing records against a programme's requirements.
Design the record as well as the registration journey
When a reader submits their details, agree what the record needs to carry into later processing. That includes the contact fields, capture history and consent information required for the intended programme.
- Specify the submission. Identify the fields and evidence needed from the journey, with wording and intended uses reviewed by your team.
- Agree the checks. Select the relevant name, email, phone or postal-address checks and their order.
- Capture the history. When the Engine creates the record, it records source, timestamp, lineage and a consent audit trail.
- Set the response. Define what happens after a failed check or repeated registration. Deduplication and frequency controls follow the programme's rules.
Audience inventory with its origin visible
Consider registrations arriving through two different journeys. A later buyer requirement may concern records from a particular source, or your team may need to examine a question about one submission. Source and capture history help place the record in context.
The programme's checks and repeat rules establish another part of its usefulness. A new registration may be a useful further response from an existing reader; the handling should reflect that purpose.
Together, capture history and agreed processing provide information for assessing new records when they are prepared for a programme. For existing inventory, the held-data page explains counting and preparation against a buyer's specification.
LeadScale's own first-party publishing
LeadScale Labs originates and monetises its own first-party data using the Engine as its processing layer.
Review the use before the journey goes live
Agree what the registration asks of the reader and what information the record will carry. Review the intended use against the capture evidence. Where a consent-management platform is used, preference management remains with that system.
Questions about new audience records
Which checks should a registration use?
Start with the fields the receiving programme needs, then agree the checks and handling. A warning, correction opportunity or another response depends on the programme's configuration.
How should another registration from the same reader count?
Define whether it represents a useful new response or a repeat you want to control. Set the deduplication and frequency rules around that decision.
What consent evidence is recorded?
The Engine records a consent audit trail when it creates the record. Confirm its contents and presentation against your reviewers' requirements, including any additional capture evidence needed.
What should each new record carry?
Bring your capture journey, required fields and intended uses. We'll discuss the history, checks and delivery your programme needs.