The Multi-Consent feature in CamBuildr helps you stay compliant with data protection laws by allowing users to give separate, traceable consents for different communication tracks – such as newsletters, events, campaigns, or donation appeals. It’s ideal for organizations offering multiple email products or communication streams while needing to ensure proper opt-in procedures.
Why Multi-Consent?
Under regulations like the GDPR, each use of personal data requires clear and verifiable consent. When a person signs up for multiple types of communication, you must ensure that each consent:
was given intentionally,
is documented,
and – if required – was confirmed via Double Opt-In (DOI).
CamBuildr’s Multi-Consent feature enables you to manage this process securely and transparently.
How It Works
1. Consentable Tags
Once the Multi-Consent feature is enabled, specific tags in CamBuildr can be marked as “consentable.” These tags include:
an internal and external label
a consent text (HTML supported)
Setting that defines whether a consent requires email verification (DOI).
The setting for whether a consent is required or optional is configured on the form or app level, not on the tag itself.
Want to get started? Reach out to your CamBuildr contact to enable Multi-Consent for your workspace.
2. Double Opt-In (DOI)
If a consentable tag is configured to require DOI, the behavior depends on whether the person is new or already in your database.
a) New People
The submission is stored in a quarantine zone (not yet saved in the database).
A DOI email is sent containing all required consents that were newly accepted.
Once the person confirms:
they are saved to the database
all accepted tags are saved as confirmed consents
b) Existing People
The person is not duplicated or overwritten.
Only the new consentable tags that require DOI are put in quarantine.
Once confirmed via email, these new tags are added to the person’s profile.
Important: There is always only one DOI email template. A dynamic block inside this email updates automatically based on which tags still require confirmation.
If you are switching from the standard DOI to the Multi-Consent DOI, the block needs to be added to the email. If the block is missing, the email’s content cannot be saved.
Configuring in Forms
In your forms or apps, you can:
define which tags should be shown for consent
configure which ones are required
The texts for each consentable tag are managed centrally in the tag settings and are not editable in individual forms or blocks.
If consents are set to “implicit”, the checkbox will disappear, and the tag will be automatically assigned to everyone who signs up using this form.
Implicit tags can still be consentable and may even require double opt-in (DOI) approval.
Be aware that in such cases, the DOI process will be triggered, and the consent text, although not explicitly clicked, will still appear in the confirmation email.
This setup will not make sense in most use cases.
Consents set to “implicit” are typically those that are required under any circumstances and should not be revokable — for example, the processing payment data in the context of a donation.
Consents from outside CamBuildr
Signups that reach CamBuildr from another system follow the same rules, as long as the channel can express that somebody accepted the consent:
People API — each entry of the
tagsarray can carryconsent_accepted, so consents work exactly as they do in a CamBuildr form, including the double opt-in and the quarantine zone. See API: People/Actions.Webhooks (Typeform, VideoAsk) — add the
consentable_tagsparameter to the webhook URL. The consent is recorded for every submission of that form, with the double opt-in when the tag requires one. The olderperson_tagsparameter cannot carry a consent: a consentable tag placed there is set only when it does not require DOI, and ignored when it does. See Typeform Integration.Workflows — an automation cannot give a consent on somebody's behalf. When a workflow attaches a tag that requires DOI, CamBuildr asks the person to confirm by email instead, and grants the tag once they click.
Whichever channel you use, only send a consent when the form the person filled in actually asked for it. A webhook URL is the same for every submission, so it suits a consent the form requires; for an optional one, use a CamBuildr form or the People API, where the answer can be passed per submission.
Consent Management & Unsubscribes
Every accepted or revoked consent is logged.
The system tracks who revoked the consent (user or admin).
Each consentable tag automatically includes a dedicated unsubscribe link.
A global unsubscribe-all link remains available.
Revoking a consent or using the global unsubscribe stops the communication and is logged, but it deletes no stored data: the person’s record, fields, tags and history all stay, and they keep counting toward your contact limit. If somebody asks to have their data erased, see Deleting people and cleaning up your database.
Technical Notes
The feature is off by default and must be activated by the CamBuildr team.
Once activated, the tag settings are extended to include consent logic (DOI required, text, etc.).
The standard DOI email includes a dynamic consent block that updates based on user input.
Each tag includes a subscribe link, useful for manual re-engagement.
Consents are sortable and the order can be customized.
Tags can be configured to not require DOI if preferred.
Additional Notes
If you use Multi-Consent, we recommend disabling the default consent disclaimer in forms.
All consent text is centrally managed and do not support multiple languages.
You can trigger multiple opt-in flows (e.g., for different campaigns), but they always use the same email template with a dynamic content block showing only the relevant tags.