Loading
Consent management records what each person has agreed to receive — product news, event invitations, research requests — along with when and where they agreed or withdrew. In Treepie Flow consent is held on the contact for each purpose, with its date, source and legal basis, and every product that sends email checks it before sending. A preference centre lets contacts change their own choices.
Because consent usually lives in the marketing tool. When someone objects, the answer has to be assembled from three systems, and the one that is missing is the one that sent the email.
Consent is held per contact per purpose — marketing, product updates, research — each with the date it was given or withdrawn and the form or conversation it came from.
Consent state sits on the contact record itself, so every product reads the same values. Withdrawal takes effect immediately everywhere, and the full history of changes is kept.
A contact objects to marketing email. Their record shows consent given through a pricing-page form in March, a preference change in August, and the three sequences that stopped the moment it changed.
It records and enforces what you have configured. Which lawful basis applies to your business, and how long you may keep a record, are decisions for you and your advisers.
Sequences check it before sending, Growth excludes non-consenting contacts from campaigns, segments can filter on it, and the audit trail keeps every change with its actor.
| An opt-in checkbox | Email-tool unsubscribes | Treepie Flow | |
|---|---|---|---|
| What is recorded | Yes or no | Subscribed or not, in one tool | An answer per purpose |
| Proof | None | The email tool’s log | Date, source, wording and recorder |
| A withdrawal reaches | Wherever someone updates it | That one tool | Every product, at once |
| Transactional email | Blocked by mistake, or ignored | Often blocked | Contract basis, keeps sending |
| Self-service | None | Unsubscribe only | A preference centre per purpose |
Yes. Enrolment is checked at send, not only at enrolment.
Yes, via import or API, with the source recorded so it is not indistinguishable from a form fill.
Yes. Erasure removes personal data while keeping the anonymised financial record Books is required to hold.
Any you need — typically product news, event invitations, research and partner offers. Each has a name, a description shown to contacts and a legal basis.
Each form records which purposes it asked about, the wording shown and the answer, straight onto the contact.
Yes. A team member records it on the contact, and the record shows who did so and when.
A page linked from every email, branded to your company, listing each purpose with a switch. Changes apply straight away.
It stops anything sent under that purpose, including sequences. One-to-one replies in an ongoing conversation are not affected.
Yes. A contact’s full history exports in one click, for subject access requests or audits.
It records what you need to show consent and honour withdrawals. Which purposes need consent is a decision for you and your advisers.
Both histories are kept, and the most recent answer for each purpose applies.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.