The comms preference centre is where customers control what types of communications they receive from your brand. It is built into the Profile Portal and does not require custom development.Documentation Index
Fetch the complete documentation index at: https://docs.omneo.io/llms.txt
Use this file to discover all available pages before exploring further.
What customers can manage
The preference centre exposes the communication consent fields stored on the Omneo profile:| Field | What it controls |
|---|---|
email_optin | Global email marketing opt-in |
sms_optin | SMS marketing opt-in |
push_optin | Push notification opt-in (if app is active) |
| Category preferences | Opt in or out of specific communication categories (e.g., new arrivals, sale alerts, event invites) |
How it works in the Profile Portal
The Profile Portal includes a pre-built Preferences section accessible from the customer’s account navigation. The page renders dynamically based on which consent fields your instance has configured. Customers can:- Toggle global email/SMS opt-in on or off
- Select which email categories they want to receive (if category preferences are enabled)
- Save changes with a single click
Australian Spam Act compliance
For Australian brands, the comms preference centre supports compliance with the Spam Act 2003 requirements:- Customers must have consented before receiving commercial electronic messages
- An unsubscribe mechanism must be available in every commercial message — the Profile Portal preference centre link serves this purpose
- Unsubscribe requests must be honoured within 5 business days — Omneo applies opt-out changes immediately
Consent fields in reactions
Reactions that send marketing communications should filter on opt-in status. For example, a reward earned notification would still send (transactional), but a promotional campaign should filter to only send to profiles whereemail_optin = true.
Example reaction filter:
Syncing preferences to your comms platform
When a customer updates their preferences in the Profile Portal, Omneo can fire a reaction onprofile.updated to sync the new preferences to your comms platform (Klaviyo, SFMC, Braze, etc.). This keeps your suppression lists in both systems aligned.
The target payload for a preference sync should include:
- Email address (as the comms platform identifier)
- Current value of all consent fields
Category preferences
If your brand sends multiple distinct communication types (new arrivals, sale alerts, event invitations, replenishment reminders), you can configure category-level consent. Each category maps to a custom attribute on the Omneo profile, and the preference centre renders a toggle for each active category. Category preference configuration requires setup by your Omneo implementation partner to define the custom attribute fields and configure the Profile Portal preference centre UI.Bounce handling
Email bounces should be fed back to Omneo via your comms platform. Hard bounces (invalid email address) should trigger a profile update that setsemail_optin = false and notes the bounce reason. This prevents continued send attempts to known-bad addresses.
Your comms platform can send bounce events to Omneo via a target (webhook in reverse), or your implementation partner can configure a sync to handle this automatically.