Connect Reteno to SiteOps

This guide is for teams that already live in Reteno — building segments, running lifecycle flows across email, push and in-app messages. If that is you, the connection is small and the payoff is direct: SiteOps sends its scheduled emails through the same account, to the same well-kept segments.

Here is the honest division of labour. SiteOps drives the email channel: it drafts, schedules, and — once you approve — sends through Reteno, reading back the sent, opened and clicked counts. Everything else Reteno does stays Reteno's: your push notifications, in-app messages and lifecycle flows keep running exactly as you built them, untouched. SiteOps is a new sender using your Reteno pipe, not a replacement for your Reteno setup.

One pairing worth understanding: Reteno knows your contacts through its own web SDK and event stream, while SiteOps builds cohorts from the SiteOps SDK's events on your site. They complement each other — the SiteOps SDK does not replace Reteno's, and neither feeds the other. When an email is planned, you pick the audience: everyone, a SiteOps cohort, or one of your Reteno segments, referenced by name so its membership is always current at send time.

One key per integration — revocable without touching the rest

Set it up, step by step

0 of 8 done

What a fresh Reteno domain asks of your DNS — SPF and DKIM
Copy each record exactly as shown, and watch the classic trap: some registrars append your domain to the host field on their own, doubling it.
1. Project settings
2. API keys
1. Project settings
2. API keys
3. Create key
1. Settings
2. Reteno
3. Save

Let an agent do it

An agent with access to your DNS can add Reteno's domain verification records for you, if your sending domain is not verified yet.

Prompt for your agent

Add the Reteno domain verification records to my DNS.

1. My Reteno project's email settings list the DNS records needed to verify <my sending domain> — SPF and DKIM entries. Here they are exactly as displayed: <each record: type, host, value>.
2. Open the DNS zone for the domain at <my DNS host, e.g. Cloudflare or the registrar> and add each record with the exact type, host and value. Watch for the host trap: if the DNS host auto-appends the domain, enter only the prefix, so the host does not end up doubled.
3. Check each record resolves: dig TXT <host> +short for every entry.
4. Tell me when they resolve so I can confirm verification in Reteno.

Creating the Reteno key and pasting it into SiteOps stay with you — and if your domain is already verified, there is nothing here for an agent at all.

If something does not work

The key saved but my emails still sit as drafts: The from address is the missing half. Open the Email section in SiteOps settings and set the sender name and address — on the domain verified in your Reteno project. The draft's note says exactly which half the gate is waiting on.
My Reteno segment does not show up as an audience: SiteOps lists the segments your key's project can see, refreshed periodically. If a brand-new segment is missing, give it a few minutes and reopen the audience picker. Also check the key belongs to the same Reteno project as the segment — keys and segments are per project.
Will this interfere with the lifecycle campaigns we run in Reteno?: No. SiteOps sends its own approved emails through your account and reads back their counts — it never touches your campaigns, flows, push or in-app messages. The one thing worth coordinating is frequency: your readers receive both streams, so glance at the Reteno calendar before approving a big send.
Do I still need the SiteOps SDK if Reteno already tracks my users?: For cohort audiences, yes. Reteno's tracking feeds Reteno's segments; the SiteOps SDK feeds the cohorts SiteOps builds from your site's events. They complement each other and neither replaces the other — and with both connected you can pick whichever audience fits each email.
I connected Reteno and another email provider — which one sends?: Whichever provider the 'Sends go through' picker in SiteOps Settings names. Several mailers can stay connected at once — only the picked one sends, and the rest stay readable, so your Reteno segments remain pickable audiences even when another service does the sending.

Before you start

A Reteno account with a project — reteno.com. If your team already runs lifecycle campaigns there, you have everything; this connection changes none of it.
A verified sending domain in your Reteno project's email settings. If your team already sends email through Reteno, this is done; if not, it is a few DNS records, pasted once.
Access to the project's settings, where API keys are created. If a teammate owns the Reteno account, do this step together.
Five minutes once the domain is verified.

Quick links

What SiteOps reads

Delivery counts for the emails SiteOps sent — sent, opened, clicked (read).
Your segment names and sizes, so they can be offered as audiences when an email is planned (read).
The emails you approve in the queue, sent through your Reteno project (write — only what you explicitly approve, never anything else).
The key's validity, so the connection status stays honest (read).
Nothing beyond email. Your Reteno push notifications, in-app messages, lifecycle flows and contact data stay entirely in Reteno — segments are referenced by name, never copied out, and SiteOps never edits them.

Connect Reteno to SiteOps

Set it up, step by step

Let an agent do it

If something does not work

Set up once, see everything every morning