Definition
A consent record is the evidence an organisation keeps that a person gave a particular marketing permission. It sits with the contact in the CRM or email platform and records the details that the bare permission leaves out: the channel the permission covers, the source where it was given, the time it was given, the wording the person saw and the choices they made.
The guide to list building and consent frames the point practically. Rules on electronic marketing differ between countries, and the UK's Information Commissioner's Office publishes direct marketing guidance explaining when consent is needed, but whatever the jurisdiction, a marketer can build the record. A list that can answer "how did this person get here and what were they told?" for every row is far easier to defend than one that cannot.
What a consent record holds
Following the site's email and CRM guides, a complete record for each permission holds:
- The channel: email, text message, post or push, recorded separately, because a permission for one is not a permission for another.
- The source: the form, page, checkout, event or integration where the permission was given.
- The timestamp of the permission, and where Double Opt-InA sign-up process in which the subscriber confirms through a link sent to the address given. is used, the timestamp of the confirmation.
- The wording the person saw at the time, kept as it was, since the wording on a form changes.
- The choices made, such as the topics ticked.
- Later changes: an unsubscribe or objection, with its own date and source.
A consent record is not the same as the organisation's decision about its Lawful BasisOne of the six grounds the GDPR accepts for processing personal data, such as consent, contract or legitimate interests, chosen for each purpose.. Where consent is the basis for a purpose, the record is the evidence of it; where another basis applies, that decision is recorded separately by whoever owns data protection.
In practice: imports, migrations and syncs
Consent records are easy to keep in one system and easy to lose between systems. The tutorial on importing contact lists into the CRM starts each import by asking where the list came from and what the people were told: an export from an old platform is usually fine when its consent records travel with it, while a file from sales or an event depends entirely on what people were told at the time.
The tutorial on moving to a new CRM treats consent as one of the categories that always moves, and it moves as a record, not a yes or no: channel, source, date and wording, loaded after the suppression entries so that nobody suppressed in the old system arrives as reachable in the new one. When two systems share contacts, the tutorial on syncing the CRM and the marketing platform sets the conflict rule for consent fields as the most restrictive value wins, whichever system recorded it, and keeps contacts with no consent record out of the marketable set until one exists.
The same idea applies outside marketing lists. The tutorial on participant information and consent for research keeps a record of what each research participant agreed to, including optional uses such as recordings, quotes and clips, usually in the recruitment log.
A florist finds the gaps before it migrates
Neppory Florists was moving its 6,300 email contacts to a new platform. Before exporting, the owner checked what each contact record held. About 4,200 had a source, a sign-up date and the wording of the checkout box or the newsletter form they had used. The remaining 2,100, a third of the list, had been typed in from order notes and event sign-up sheets over several years, with no source and no wording. Those 2,100 were loaded into the new platform as non-marketable and sent a single re-permission message asking them to confirm. 540 confirmed, and their new records carried the date, the message and the wording they agreed to. The rest stayed out of marketing sends.
Related terms
A Double Opt-InA sign-up process in which the subscriber confirms through a link sent to the address given. adds a confirmation step, and its timestamp becomes part of the consent record. The Lawful BasisOne of the six grounds the GDPR accepts for processing personal data, such as consent, contract or legitimate interests, chosen for each purpose. is the ground an organisation chooses for each purpose; consent records evidence it when the basis is consent. A Suppression ListA list of addresses or contacts excluded from every send, such as unsubscribes, hard bounces and spam complaints. is the other half of the picture: the record of people who must not be contacted, kept rather than deleted so that a later import cannot revive them. And every consent record is itself Personal DataAny information relating to an identified or identifiable living person, such as a name, email address, location data or an online identifier., held under the same rules as the contact it belongs to.
Common confusions
- A "subscribed" field is a consent record. A yes or no flag records the outcome, not the evidence; without the source, date and wording it cannot answer how the person came to be on the list.
- Consent covers every channel. A permission is recorded per channel; email consent says nothing about texts or push notifications.
- Records can be rebuilt after a migration. Evidence that was not carried across is usually gone; it has to move with the contacts.
- The newest value should win in a sync. For consent, the most restrictive value wins, so an old "subscribed" value never overwrites a newer objection.
- A consent record settles the legal question. It is evidence; whether consent was needed, and whether it was valid, is a question for the regulator's guidance and whoever owns data protection.
