OneTrace.pro Help center

Messaging rules

Messaging rules protect your customers from unwanted messages and protect you from complaints and unsubscribes. Here you define who you can message without an explicit subscription, when messages must not be sent, and how many messages one person can receive. The rules apply to all channels, journeys, and campaigns in the project.

Open the page from the menu: Settings → Messaging rules. Owner and Administrator can change the rules.

Messaging rules page

Subscription

By default, all customers receive messages except those who have unsubscribed. If you turn on Send only to subscribed profiles (opt-in), marketing messages only go to profiles with an explicit subscription to the channel. Turn this mode on if your policies or the law require confirmed consent.

A profile gets a subscription when:

  • your website or server sends it through the consent API, for example from a subscription form or a customer account. See Server integration;
  • the customer taps Start in the Telegram bot, subscribes to the Viber bot, starts the MAX bot or shares their phone number in it, writes to the VK community or allows its messages, writes in Instagram Direct, or allows browser notifications;
  • subscriptions are carried over when moving from another platform.

An unsubscribe happens automatically when the customer:

  • unsubscribes in the preference center from a link in a message, or clicks Unsubscribe in their email client;
  • sends /stop to the Telegram bot, blocks it, or writes "stop" in WhatsApp;
  • unsubscribes from the Viber bot;
  • stops the MAX bot or deletes the chat with it;
  • blocks messages from the VK community or writes "stop" in Instagram Direct.

In addition, an address or number is unsubscribed if an email bounces with a permanent error or the provider reports that the number doesn't exist.

The Advertising consent is stored separately from messaging: whether the customer's data may be sent to ad platforms for conversions and audiences. By default it's allowed for everyone except those who denied it. Turn on Send data to ad platforms only with explicit consent to send only customers who allowed it themselves: in the preference center, through the API, or in identify. Unsubscribing from messages doesn't affect this consent.

A profile's current subscriptions and unsubscribes, with their source and date, are shown in the Subscriptions block on the profile card. See Profiles.

Subscription topics

A customer can unsubscribe from a single topic instead of the whole channel: for example, stop getting news but keep getting personal offers. Topics are collected in a list in the Subscription topics block.

Subscription topics list

Topics from templates, forms, and consents appear in the list by themselves, with the key instead of a name. To make it clear to customers what a topic is about, click the pencil and fill in:

  • Name for customers and Description: in each project language. Common keys (marketing, news, loyalty, and others) have standard names in all languages;
  • Channels: the channels in which the topic is shown in the preference center, for example news only in email and Telegram. Empty means all of them;
  • Show in the preference center: turn it off for service topics, for example order confirmations that the customer receives anyway.

The arrows change the order of topics in the preference center. You can delete a topic only if no template or form uses it; customer consents for it are kept. To add a new topic, click Add topic: the key can contain Latin letters, digits, _, and -, and it can't be changed after creation. A project can have up to 100 topics.

You choose a message's topic in the template: from the list or as a new key.

Preference center

The unsubscribe link in a message opens the preference center: a page on your brand's domain, in the language of the message. On it, the customer can:

  • unsubscribe from this message's topic with one button;
  • select the topics they want to receive in each of their channels: email, SMS, Telegram, browser notifications, and others;
  • choose how often to receive marketing messages: as usual, at most once a week, or once a month;
  • pause messages for 30 or 90 days;
  • unsubscribe from all messages at once, including channels you connect later;
  • add the loyalty card to Wallet. The link is shown if Wallet cards are connected;
  • clear the Personalized ads checkbox so their data isn't sent to ad platforms. The checkbox is shown if an ad platform for audiences or conversions is connected in integrations.

Preference center opened from an email link

The preference center shows the channels the customer is subscribed to or has received messages in over the past year, as well as the channels of connected integrations for which the profile has an address. A channel you can't message, because the address doesn't exist or the customer stopped the bot, is shown dimmed.

Frequency and pause apply to all channels together and only to marketing: transactional messages are sent as usual. If the customer chose "at most once a week", marketing messages aren't sent within a week of the previous one; in the history they're marked with the frequency chosen by the customer reason. Changes made in the preference center are shown on the profile card with the preference center source, and the event history shows the $preferences_updated event.

How to give the customer the link:

  • in the email builder: the Footer block with the Unsubscribe link and the “Manage subscriptions” link (you can change the link text in the block properties);
  • in your own HTML and in other channels: the {{ unsubscribe_url }} and {{ preferences_url }} variables. Both open the preference center.

Email clients with an Unsubscribe button (the List-Unsubscribe header) unsubscribe in one click from the email's topic only, without opening the page.

You set the text at the top of the page in the Preference center block, in each project language. Empty means the standard text.

In your store's customer account

You can offer the same choices in your store's customer account:

  • WooCommerce: the My account → Newsletters tab, turned on with the plugin's "Newsletters in My account" setting;
  • Magento 2: My Account → Communication preferences, with the "Communication preferences in My Account" setting;
  • 1C-Bitrix: the onetrace:preferences component on the customer account page.

The store's secret API key needs the View profiles and Edit profiles and import permissions (profiles.read, profiles.write). Your own website connects to the same data through the API: GET and PUT /api/v1/profiles/{type}/{value}/preferences. The response also contains a link to the customer's preference center page, valid for 30 days.

Brand voice and rules

In the Brand voice and rules field, describe how your brand writes: how you address people, sentence length, emoji, and what you must not promise. Up to 1000 characters. AI in the email editor always follows these rules: in subject lines, text editing, emails from a description, and A/B test variants. For example: "We address people as 'you', friendly and brief. No caps or exclamation marks in subject lines. We don't promise discounts or delivery times that aren't in the email."

Brand voice and rules

Approval

The Launch campaigns and journeys only after approval switch turns on approval: the author submits a campaign or journey for review, and a member with the approval permission approves it or returns it with a comment. A campaign can only be launched and a journey only published once approved, and any change after approval sends it back to review. Approval is off by default.

Approval in messaging rules

Transactional messages

The Transactional message checkbox in a template is for order confirmations, password resets, and delivery notifications. These messages are sent without checking subscription, frequency limits, or quiet hours. Don't mark promotional emails this way: it violates recipients' rights and damages your sender reputation.

But even a transactional message isn't sent if the channel is closed for the recipient: the mailbox or number doesn't exist, the Telegram bot is blocked, or "stop" was sent in WhatsApp. Learn more in Transactional messages and cascades.

Quiet hours

  1. Turn on Do not send at night.
  2. Set the from and to times in HH:MM format, for example from 22:00 to 08:00.
  3. Click Save.

Times are in the project's time zone, which is shown next to the fields and can be changed in the project settings. A message that was due during quiet hours isn't lost: it gets the Scheduled status and is sent as soon as the window ends. Transactional messages go out without delay.

Frequency limits

A limit sets how many messages one customer can receive in a period.

  1. Click Add limit.
  2. Fill in the row: At most 3 messages per 24 h.
  3. Choose a channel or all channels together.
  4. Click Save.

Frequency limits and quiet hours

An example rule set for an online store:

Rule Why
at most 1 message per 24 h, SMS SMS is expensive and annoys people more often than email
at most 3 messages per 24 h, Email abandoned cart, recommendations, and a campaign won't all arrive at once
at most 10 messages per 168 h, all channels together an overall weekly cap

Good to know:

  • The window is rolling: messages from the last N hours before the send are counted.
  • A message over the limit is skipped, not delayed. In the profile's message history and in reports, it appears with the Skipped status and the frequency limit reason.
  • Transactional messages and test sends don't count toward the limit.
  • You can set up to 10 rules, with a window from 1 to 720 hours.

Extensions

The Extensions block lists the capabilities connected in the project: channels (Email, SMS, Telegram, WhatsApp, and others), ad platforms, data sources, and moving from other platforms. Clear the checkbox for an extension you don't need, and it disappears from the project's integrations, templates, and journeys. This keeps things simpler for a team that, for example, doesn't use Viber.

Why a message wasn't sent

If a customer didn't get a message, find it in the message history on their profile card and check the reason:

Reason What to check
not subscribed the profile is unsubscribed from the channel or topic, or opt-in is on and there's no subscription
frequency limit the customer already received the maximum number of messages for the period
the customer paused messages the customer chose a pause in the preference center; you can remove it on the profile card
frequency chosen by the customer the customer asked to receive messages at most once a week or once a month, and that period hasn't passed yet
no recipient address the profile has no email, phone, or chat for the channel

For more about reports, see Analytics and reports.