Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Analytics › Expert

Checkpoint: Consent Maps, Retention and Privacy Operations

Scenario questions set at an invented garden design studio test the second expert analytics module: why consent fails between tools while the banner passes its checks, what a consent map records, where a withdrawal came undone, retention set by purpose, the records kept on purpose after deletion, deletion that reaches every copy and the changes that reopen the map. Each answer gives the reasoning and the page behind it, so a miss leads straight back to the reading.
CheckpointExpert levelModule 2: Consent and retention across the stack4 minUpdated

What this checkpoint covers

Strevaunt Garden Design is an invented garden design studio with a CRM, a newsletter, a consent banner and paid social fed by a monthly customer list upload. The studio manager owns data protection. The questions apply the tutorial on mapping consent across the stack, the guide to data retention across marketing tools and the privacy and consent operations playbook. They concern how a stack acts on decisions about Personal Data, not legal advice.

Illustrative example — not a real result

Strevaunt Garden Design: a withdrawal test that came undone

A marked test contact was logged in the CRM on Monday as objecting to direct marketing, an objection taken by phone. The CRM and the email platform sync both ways, and the most recent edit wins.

DayWhat happenedResult
MondayObjection flag set in the CRMExcluded from the newsletter
ThursdayThe test contact downloads the planting guide through a gated formEmail platform marks it subscribed; the sync clears the CRM flag
Month endCustomer list file built from the email platform's subscribersTest contact in the file

Task

  • Commit to an answer and the reason behind it for each question before reading on; the reason is marked as well as the choice.
  • Reread the linked section for each miss.

Questions

  1. The banner passed its checks, so the studio manager says consent is in order. Yet an enquirer who left the newsletter box unticked receives the newsletter, because the sync adds every enquiry to the main list. Why?
  2. A draft consent map has one row per tool, each marked "consent: yes". What is wrong, and what should a row record?
  3. Read the test above. Why did the objection come undone, and what stops it happening again?
  4. The studio manager wants one deletion age in the CRM and another in the email platform, both borrowed from another studio's privacy notice. What instead?
  5. A retention run deletes old enquiries, including the entries of people who objected. Later a garden show's visitor list is imported and one of them receives the newsletter. What should the run have kept?
  6. A past client asks to be deleted. The email platform removes her, the next sync restores her, and nothing shows what was done. What order, and what record?
  7. Next quarter brings text reminders, a quiz widget collecting email addresses, new banner category wording, a new designer and a new newsletter template. Which reopen the map?

Answers explained

  1. The banner covers one kind of permission. It records choices about cookies and tags and passes them through Consent Mode; the newsletter permission lives in the form, CRM and email platform, and it did not travel with the enquiry. Map consent by purpose so both kinds sit in view. See why consent breaks between tools.
  2. It maps tools, and "yes" records nothing. Each purpose needs a row: the permission or other basis and where it was captured, with wording and evidence; the system holding the record; each reader and how it reads; the withdrawal route; tag behaviour; a test; an owner. The basis is the studio manager's decision. See the steps that build the map.
  3. The sync let a newer permission overwrite the objection. For consent the most restrictive value wins, and an objection sits in the one system that holds the record, where a later sign-up cannot overwrite it, with a Suppression List that every sending tool checks. Build the file from that record and rerun the test contact. See naming the system that holds the record.
  4. Periods by purpose, set by the data protection owner. Old enquiries, lapsed subscribers and upload files are different purposes. The studio manager sets each period and records what starts the clock and what happens at the end. A borrowed period fits another business, and a rule in one tool is undone by the next sync. See setting periods by purpose.
  5. The suppression entries, with only what recognises the person. Keep the identifier, the reason and the date, so a returning address is blocked while minimisation holds, and name suppression and consent records in the schedule as kept on purpose. See records you keep on purpose.
  6. Owner, route, every copy, record. The request goes to the studio manager, as the marketing opt-out request SOP sends deletion requests to the data protection owner. Stop or filter the sync before deleting downstream, or remove the person at the system that holds the record so the sync carries the deletion downstream; either way the upload files are included and a suppression entry is kept. Log tools, date and count without personal data: the GDPR expects the business to show compliance. See deletion that reaches every copy.
  7. The texts, the widget and the banner wording. A new channel needs a purpose row with a tested withdrawal route, a widget receiving personal data is a new reader, and a category change reopens its tag rows and goes through the consent banner QA checklist. The designer is an access question; the template matters only if the sign-up wording changes. See triggers that reopen the consent map.

Where to go next

If questions one to three caught you out, rework the wine club consent and retention exercise; the data flows these routes follow were traced at the advanced analytics level. Then start module three with the exercise on a tracking outage and a wrong report.

Pages this lesson applies

Terms used on this page

Also related

Related