How consent works in Releva
Releva keeps one consent record per profile in your shop. Campaigns and workflows read it before every send. This page explains what the record holds, which messages it gates, and which setting decides who owns it: Releva or your shop.
Three facts on a profile
Section titled “Three facts on a profile”| Fact | Where you see it | Meaning |
|---|---|---|
| Marketing status | Marketing messages on the profile page | Subscribed: the customer opted in. Unsubscribed: the customer opted out. Not subscribed: neither has happened yet. The since time is when the status last changed. |
| Subscriptions | Subscriptions under Audience & membership | The topics the customer is subscribed to, stored exactly as your shop or integration sent them (marketing, weeklyNewsletter). Use them in segment rules to target a topic. They apply on every channel. |
| Push permission | Separate from Marketing messages | A browser or a device opts in to web push or app push on its own. |
Subscribing marks the profile Subscribed; unsubscribing marks it Unsubscribed. The marketing status decides who can be sent to; the subscriptions are for targeting.
Every campaign and workflow has a Campaign Scope that says how it uses the status:
| Campaign Scope | Who it reaches on email, SMS, Viber, WhatsApp and webhooks |
|---|---|
| Opt-in Marketing | Only Subscribed profiles |
| Opt-out Marketing | Everyone except Unsubscribed profiles |
| Transactional | Everyone, whatever the status. Never use it for marketing messages. |
Push notifications, Facebook Ads and Google Ads do not check the marketing status at all. A segment that feeds those channels needs its own condition on the status if consent matters there.
User-visible subscriptions
Section titled “User-visible subscriptions”Under Settings › Messaging › User Visible Subscriptions you choose which subscriptions your customers see on the Subscription preferences page, and the caption each one gets. By default that is one entry, marketing, shown as General marketing. Subscriptions your integration writes but you never switch on stay hidden: useful for segments, invisible to the customer.
Two rules follow from this list:
- Default fill. When a customer subscribes and ends up with none of your user-visible subscriptions, Releva adds all of them. With the default list, a customer who subscribes without choosing a topic gets
marketing. A customer who was already subscribed and changes their topics keeps exactly what they chose. - Unsubscribe clears only what the customer could see. Opting out removes the user-visible subscriptions and leaves the rest. A profile with
marketingandweekly-deals, where onlymarketingis visible, keepsweekly-dealsafter an unsubscribe. The Unsubscribed status still blocks every Opt-in Marketing and Opt-out Marketing send.
Internal or External
Section titled “Internal or External”Subscription Management in Settings › Messaging decides who owns consent.
- Internal: Releva owns it. Unsubscribe links in messages open Releva’s Subscription preferences page, profile pages get a Subscribe / Unsubscribe button, and you define the user-visible subscriptions and what sign-up forms do. Send email and SMS only through Releva, because an unsubscribe here does not reach other tools.
- External: your shop owns it. Unsubscribe links in messages go to your shop’s unsubscribe page (Email Unsubscribe URL, or a link per customer that your integration sends). Your shop must mark the customer unsubscribed and report the opt-out to Releva. If you leave Email Unsubscribe URL empty, customers without their own link are skipped by Opt-in Marketing and Opt-out Marketing campaigns; Transactional campaigns still reach them.
Sign-up forms and double opt-in
Section titled “Sign-up forms and double opt-in”With Internal management, Subscription Request Behavaior decides what a sign-up from your site does:
- Subscribe right away: the customer is subscribed at once. Simple, but anyone who copies your shop’s public access token can subscribe any address.
- Wait for confirmation (double opt-in): Releva records a Subscribe Request Submitted event and subscribes nobody yet. A workflow triggered by that event sends an email with the
{{subscribeLink}}merge tag, and the customer is subscribed when they open it.
Subscribing from a profile page, or from your shop’s server, always subscribes right away.