Governance
Consent, Global Suppression and CEM Classification
A single, platform-wide mechanism lets customers opt out of all commercial communications in one action, and a template-level classification governs which messages carry consent and unsubscribe obligations and which do not. Both are native, live capabilities backed by an auditable change log.
This page answers
- How quickly does an opt-out take effect?
- Does an opt-out on one brand apply to other brands in the group?
- How does the platform tell a service message apart from a commercial one?
- Where does consent and preference data live?
- Is there a record of consent and preference changes?
Universal opt-out and global suppression
The Global Unsubscribe and Preference Center gives customers a single, transparent action to stop all commercial communications. Every promotional email includes a one-click unsubscribe option next to the sender address, in addition to any unsubscribe link in the template itself. Clicking it updates the customer's status in the Unified Customer Database immediately; no manual step is required.
Once a customer is in the global unsubscribe state, campaign audiences respect it automatically: the Unsubscribe Groups segment lets any campaign or journey exclude suppressed recipients as a standard targeting rule, so suppression is enforced at send time across every campaign rather than managed as a one-off list. There is no batch delay.
Suppression mechanisms
| Mechanism | What it does |
|---|---|
| Global Unsubscribe page | Customer-facing page that records a full opt-out; status updates in the profile without manual intervention. |
| Subscription Preferences Center | Lets customers manage preferences by category or channel instead of opting out entirely, synced to the profile in real time. |
| One-click unsubscribe (List-Unsubscribe header) | Present on every promotional email; supports the Gmail and Yahoo one-click standard so mailbox providers can action the opt-out directly. |
| Unsubscribe Groups segment | Standard targeting segment any campaign or journey can reference to exclude suppressed recipients automatically. |
| SMS and WhatsApp unsubscribe methods | Link- or keyword-based opt-out (STOP), processed automatically whether or not the keyword is shown in the message. |
From the click to the next send
- CustomerThe customer actsAn unsubscribe click, a preference update, an SMS keyword reply or an API call.
- PlatformThe profile updatesThe status is written to the customer profile immediately, whichever surface the change came through.
- PlatformSend time enforces itThe next campaign or journey step evaluated excludes the suppressed recipient as a targeting condition.
- PlatformBrands see the flagIn a group, the suppression flag is readable by every other brand workspace without merging the brands' data.
- PlatformThe change is loggedWhen and how the status changed is recorded, for a defensible audit trail.
Multi-brand propagation
For a group operating several brands, a single opt-out needs to apply everywhere the customer is known. The multi-workspace architecture keeps each brand's data and campaigns isolated for governance while still allowing a suppression event to propagate: a customer's opt-out from one brand is reflected as a suppression flag readable by every other brand workspace in the group, a single group-wide effect without merging the brands' underlying data.
Service versus commercial (CEM) classification
| Template type | Consent requirement | Unsubscribe requirement |
|---|---|---|
| Service | Opt-in bypass applies; sends proceed regardless of marketing opt-out status. | Not required, since the message is transactional rather than promotional. |
| Commercial (CEM) | Requires active marketing consent; blocked for suppressed or opted-out recipients. | Required; an unsubscribe link and preference options must be present. |
Set at design time
Every outbound template is typed as either a Service message (order confirmations, delivery updates, account notices) or a Commercial Electronic Message (promotions, offers, newsletters). The classification is set at design time, before the template can be used in a live send, so downstream consent and unsubscribe rules apply automatically and a commercial message is not sent under a service exemption.
Consent and preference data model
- Subscribe and unsubscribe APIs: manage opt-in and opt-out status for email, SMS and WhatsApp at scale.
- Consent APIs: record and update consent status (GDPR-style opt-in) alongside identifier and attribute data.
- Profile export and deletion: retrieve or remove a customer's stored data on request.
- Changes through a customer-facing surface and through an API write to the same profile, so there is one consistent record regardless of the channel the change came through.
Audit trail and governance
Consent and preference changes are logged as they occur, whether the change came from an unsubscribe link, a preference-centre update, an SMS keyword reply or an API call. The exact fields captured and the specifics of cross-brand propagation should be confirmed with the implementation team against the group's brand structure and regulatory obligations.
In TemasCRM
Every claim is compared with this product: what is live, what is partial, what is planned and what is not applicable by this product's design.
5 Live1 Planned1 Not applicable
- One global opt-out enforced at send timeLive
The do-not-contact flag on a person stops every commercial send; each send is checked at the moment of sending and a refusal is logged with its reason (opted_out, consent_missing, consent_denied). There is no batch.
Consent ledger - Public preference page for the customerLive
Every message carries a preferences link; the public page reads the state from its token alone and records the stop without a sign-in.
- Service versus commercial typed per templateLive
Every template carries a message type, service or commercial, set before it can be used; a campaign whose type disagrees with its template is refused (message_type_mismatch).
Templates - Consent APIs alongside the panelLive
Consents are recorded and checked through the API's consent routes; the ledger screen reads the record, and the send gate every message passes, a campaign's included, checks it. A connected Shopify shop's marketing state is not read: neither its customers connector nor its orders connector writes a consent, so a subscription at the shop grants nothing here and an unsubscribe there stops nothing here. In the other direction, a refusal recorded here on SMS, CALL or EMAIL leaves the product for one place: its address goes to the national registry, IYS, as a refusal, reported by the scheduler while it is on. A permission is never uploaded.
Consent ledger - Audit trail of consent changesLive
The consent ledger lists every change with its channel, status, source and time, per person.
Consent ledger - One-click List-Unsubscribe headerPlanned
The email provider integration does not set the header yet; the in-body preferences link is present on every message.
- Propagation of a suppression flag across brandsNot applicable
Tenant isolation is a legal boundary here: no flag and no read crosses a workspace, and the isolation report proves it. A group-wide opt-out would be a decision for the workspaces' owners, not a platform feature.
Isolation report