How sender verification and click tracking work
Settings › Messaging is one form with seven tabs: General, Emails, Text Messages, Viber Messages, Push Notifications, Webhooks and WhatsApp. Every tab edits the same shop settings and the single Save button under the tabs saves all of them. This page explains the two things on it that every channel depends on, the sender domain and its two DNS records, and the daily limits. The per-channel provider settings are covered by the channel pages linked at the end.
One sender domain for every channel
Section titled “One sender domain for every channel”The Email Sender Address on the Emails tab does more than name the sender of your emails. Its domain part, for example demo-store.example.com in news@demo-store.example.com, is your sender domain, and Releva derives two hostnames from it:
| Record | Host | Points to | Used for |
|---|---|---|---|
| DKIM | <token>._domainkey.<sender domain> |
<token>.dkim.<releva host> |
Signs your emails so mailbox providers can confirm they really come from your domain. |
| Click tracking | click.<sender domain> |
tr-<id>.<releva host> |
Every link in every message, on every channel, is rewritten to this hostname so Releva can record the click and redirect to your page. |
Both are CNAME records. A shop set up before CNAME-based DKIM may still see a TXT row for DKIM instead; add it with the type the table shows. The exact values are unique to your shop; copy them from Settings › Messaging › Emails › details… (both records) or from the Click Tracking card on the General tab (click-tracking record only). The guide Set up your email sender and DNS records walks through publishing them.
When you save a sender address whose domain differs from the previous one, Releva discards the old sender identity and creates a new one with a new DKIM token. Both records change and have to be published again. Changing only the mailbox part before @ changes nothing.
What each record gates
Section titled “What each record gates”The two records fail independently and block different things:
- Click-tracking record missing. Campaigns and workflows cannot be activated on any channel: email, SMS, Viber, push notifications and WhatsApp all route their links through
click.<sender domain>, and Releva refuses to send a message with dead links. The channel lists show Campaign sending is disabled until the click-tracking DNS record is in place for your sender domain, and campaign cards show Click tracking not ready - check Click Tracking settings. - DKIM record missing. Only email is blocked. The lists show Email sending is disabled until the DKIM DNS record is in place for your sender domain. Other channels keep sending.
Sender verification on the Emails tab is successful only when both records resolve.
How the checks run
Section titled “How the checks run”Opening the Emails tab, the details… window or the General tab looks the records up in DNS. Re-check DNS Records and Re-check repeat the lookup; nothing else happens, so you can press them as often as you like. DNS changes usually show up within a few hours.
The click-tracking record is checked in two stages:
- Does the CNAME resolve? Until it does, the row is red and the box under the table reads Not checked - the CNAME is not published yet. Releva does not probe the host before the record exists.
- Is Releva answering on it? Once the record resolves, Releva requests a page from
https://click.<sender domain>and reports the result: The click-tracking host is serving (all good), Nothing answered on the click-tracking host (usually the TLS certificate is still being issued; clears on its own), A different server is answering for this hostname (the CNAME points at a parked page, your web host or a CDN) or The click-tracking host answered that it is unhealthy (temporary, on Releva’s side).
Releva issues the TLS certificate for click.<sender domain> itself, as soon as the record resolves. That is why a freshly published record can pass stage 1 and fail stage 2 for a while.
The grey note Could not look up where mail for your sender domain is delivered under the table is informational and needs no action.
Cloudflare and other proxies
Section titled “Cloudflare and other proxies”Releva checks that click.<sender domain> and the DKIM host resolve as CNAME records. A Cloudflare record set to Proxied (orange cloud) answers with Cloudflare’s own addresses instead, so the check fails and clicks never reach Releva. Set both records to DNS only (grey cloud). Cloudflare can also flatten CNAME records on subdomains; if the row stays red with the record set to DNS only, check the CNAME Flattening setting of the zone and keep flattening to the root only. The same applies to any DNS provider that flattens CNAME records on subdomains.
SPF and DMARC
Section titled “SPF and DMARC”Releva’s sender verification checks DKIM and click tracking only. It does not show, require or check SPF or DMARC records. Mailbox providers still use them to decide where your mail lands, so keeping one valid SPF record and one _dmarc TXT record on your sender domain remains good practice. Follow your mail provider’s instructions for them; the Releva admin has no values to copy for these.
Daily limits
Section titled “Daily limits”Releva caps how many marketing messages one profile receives per day. The caps live on this page:
| Tab | Setting | Range | Default |
|---|---|---|---|
| General | Max Messages Per Day (across all channels) | 1 to 30 | 10 |
| Emails | Max Emails Per Day | 1 to 10 | 3 |
| Text Messages | Max Text Messages Per Day | 1 to 10 | 3 |
| Viber Messages | Max Viber Messages Per Day | 1 to 10 | 3 |
| Push Notifications | Max Push Notifications Per Day | 1 to 10 | 3 |
| Webhooks | Max Webhooks Per Day | 1 to 10 | 3 |
| Max WhatsApp Messages Per Day | 1 to 10 | 3 |
Each message decides for itself what happens to a profile that already reached the cap (reschedule, send anyway or skip). How that choice works is explained per channel in How emails work, How SMS work and How Viber messages work.
The other email settings
Section titled “The other email settings”- Optimize for: Delivery Rate (the default) pauses briefly between emails, which lowers the chance of landing in spam; Sending Speed sends without the pause.
- Bypass Plus Addressing: when on, mail to
john+folder1@example.comis delivered tojohn@example.cominstead, so a customer’s filing rule does not hide your email. - Email Reply-to Address: where customer replies go. Use a mailbox somebody reads.
If your shop’s email is delivered through Klaviyo, the Emails tab shows Email delivery for this domain is handled by Klaviyo instead of these fields: Releva’s own email sending is off for the shop, email steps in campaigns fire a “Releva Send Email” event that a Klaviyo flow delivers, and every other channel works as usual. Releva staff set this connection up with you.
What else is on this page
Section titled “What else is on this page”- Click Tracking (General): the click-tracking record and host check described above.
- Subscription Management and Subscription Request Behavior (General): see Choose how Releva manages subscriptions.
- Message Sender and credentials (Text Messages, Viber Messages): the SMS or Viber gateway Releva sends through. See How SMS work and How Viber messages work.
- App Type, iOS APNs environment and Firebase Service Account Credentials (Push Notifications): see How push notifications work.
- WhatsApp account setup is not here but under Settings › Facebook & Whatsapp: see Connect WhatsApp through a Business Solution Provider.
A separate page, Settings › AWS, stores the AWS access key that S3 pipelines write with.