Capture
An approved form, the wording shown beside it, and an identifier for where it ran.
Data management
Lead data you can act on.
Validation, consent records, suppression, delivery and retention for every lead that moves through a program.
What a lead record contains
Contact details, the campaign and placement that produced the lead, the page the consumer was on, the consent language they were shown, and the timestamp. This is stored on the record itself rather than in a separate log that has to be joined to it later.
Validation
Every lead is checked for required fields, formatting, duplicates inside an agreed window, geographic eligibility and any criteria specific to the campaign. Leads that fail are not delivered, and the source is told which field failed and how many records it affected.
Opt-outs and suppression
Opt-outs, do-not-contact requests and campaign exclusions are written to suppression and applied before the next send. Suppression data is used to prevent contact and for nothing else.
Delivery
Leads are delivered into your CRM, through an API, or by secure transfer, in the format agreed during setup. Each program has one destination, and no secondary copy is sent anywhere else.
Retention
Records are deleted on a schedule set per program. The job runs on its own whether or not the program is still active, and there is no archive tier holding a copy after the retention period ends.
Lifecycle
Capture, validate, deliver, delete.
Four stages. Each one has an owner and a control.
Validate
Field checks, formatting, duplicates, and whether the consumer is eligible at all.
Deliver
One agreed destination, in the agreed format.
Delete
Scheduled retention, with no archive copy kept.
Get started
Tell us the target.
We will build the program around it.
Tell us the audience, the channels you are considering, where the leads need to land, or the inventory you have to place. We will say whether it is a fit and what the first steps would be.