Definition
A consent map is a single table for the marketing stack with one row per purpose rather than per tool: email, text messages, site analytics, ad measurement, personalisation, uploads of customer lists and anything else the business does with personal data. A tool that serves several purposes appears in several rows, and the same email address can sit behind many of them. The consent mapping tutorial draws the map and keeps two kinds of permission apart on it: the choices a visitor makes about cookies and tags, and the basis for each processing purpose, with the separate rules for electronic marketing read alongside.
The map does not decide which lawful basis applies to a purpose. That choice is for whoever owns data protection, taking legal advice as needed; the map writes it into the row and shows whether the tools act on it.
What a row records, from capture to withdrawal
- Purpose. What the data is used for.
- Basis and capture point. What the business relies on for that purpose and where it comes from, such as a banner category, a checkbox at checkout, a preference centre or a sign-up form, with the words shown at that moment and where the proof is stored. Where another basis applies, the row says who chose it.
- Holding system. The one system whose record counts for the purpose. Every other tool reads from it or receives updates from it.
- Readers. Each tool that acts on the data, and how it learns the state: by reading the holding system, by a scheduled sync, through a file someone builds, or not at all.
- Withdrawal route. How an unsubscribe, a withdrawn permission or an objection travels from wherever it is made to every reader.
- Tag behaviour. For rows that rely on tags, what they do when a visitor accepts, rejects or has not answered.
- Test and owner. A check with a marked test record that proves the row works, its latest result, and the person who answers if it fails.
A reader that never learns the state, or a route that depends on someone remembering, is the gap the map exposes.
In practice: opt-outs, sign-up sources and changes that reopen the map
- Opt-out requests. When someone asks by phone, by reply or in person to stop marketing, the opt-out request SOP uses the map to find every tool that holds the person, records the change once in the holding system and on the suppression list, and hands any route that failed to the owner of that row. If the map is missing or stale, the SOP honours the request anyway and notes the gap.
- Sign-up sources. The email sign-up source register takes the map's single email row and splits it by source: each form, pop-up or import that adds subscribers, and what people were told at each.
- Keeping it live. The privacy and consent operations playbook treats the map as a working document: a new tool, form, banner setting, customer list upload, channel or change of basis reopens it before going live, and each row's latest test result is filed beside it.
- Measurement. The guide to privacy, consent and measurement covers what tags may observe under each consent state; the map carries that record past the site's tags.
A pet supplies shop finds where text objections stop
Grethaan Pet Supplies, an invented pet supplies shop, drew a consent map with 5 rows. The text message row looked sound: customers who replied to a text asking for no more marketing at all were opted out in the messaging tool within minutes. The advertising row was not. Its weekly customer list upload was built from the CRM, and the messaging tool never told the CRM about objections, so the route for that row ended at the messaging tool. Of 37 customers who had objected by text over 2 months, 31 were still in the latest upload file, and so still in the audience the shop's ads were shown to. The CRM owner set the messaging tool to sync objections to the CRM nightly, the upload file is now built after the suppression filter, and the row's test adds a marked customer who objects by text and checks that they are missing from the next file.
Related terms
A Consent RecordThe stored evidence of a marketing permission: the channel, the wording the person saw, the date and the source of each opt-in, kept with the contact record. is the evidence behind one contact's permission: the channel, the wording, the date and the source. The map works a level above it, per purpose. The CMPSoftware that collects, stores and passes on visitors' consent choices for cookies and tracking. holds the record for the cookie and tag rows and passes the visitor's choice to the tags; marketing permissions given at checkout or objections made to customer service sit elsewhere. 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. for each purpose is written into its row by the data protection owner. A Suppression ListA list of addresses or contacts excluded from every send, such as unsubscribes, hard bounces and spam complaints. that every sending tool checks is what keeps withdrawals and objections in force across tools, and the map shows which tools actually check it. The Integration RegisterOne standing record of every connection between marketing tools: what moves, which way, keyed how, on what schedule, with whose credentials and owner. lists the connections data moves along; its consent filter column says what each one excludes, which the map reads when it fills in a row's readers.
Common confusions
- The banner is the consent map. The banner covers cookie and tag choices, one kind of permission among several. Marketing permissions and objections are held in other systems and need rows of their own.
- Each tool's own opt-out list is enough. Separate copies drift, so a withdrawal logged in one tool can go unheard in another.
- One contact's consent history is the map. That is a consent record. The map describes systems and routes for every purpose, not any one person's permissions.
