--- title: "SFMC Relay: Send Insider One Email Through Your Salesforce Marketing Cloud Account" slug: "sfmc-relay" description: "SFMC Relay lets you build promotional emails in Insider One and send them through your own Salesforce Marketing Cloud account with Trigger Send" updated: 2026-11-16T11:49:39Z published: 2026-11-16T11:49:39Z canonical: "academy.insiderone.com/sfmc-relay" --- > ## Documentation Index > Fetch the complete documentation index at: https://academy.insiderone.com/llms.txt > Use this file to discover all available pages before exploring further. # SFMC Relay: Send Insider One Email Through Your Salesforce Marketing Cloud Account SFMC Relay lets you build, personalize, and schedule your promotional emails in Insider One and send them through your own Salesforce Marketing Cloud (SFMC) account. Your emails go out from your SFMC account, with your own sending domains, IP addresses, and SFMC settings. > [!NOTE] > SFMC Relay is currently available for a limited number of accounts only. To ask for access, contact the Insider One team. This guide explains the following concepts: - [How SFMC Relay Integration works](/docs/SFMC-Relay#how-sfmc-relay-integration-works) - [Before you start: what you need in SFMC](/docs/SFMC-Relay#before-you-start-what-you-need-in-sfmc) - [Set up SFMC Relay in Insider One](/docs/SFMC-Relay#set-up-sfmc-relay-in-insider-one) - [Create a campaign](/docs/SFMC-Relay#create-a-campaign) - [Unsubscribes](/docs/SFMC-Relay#unsubscribes) - [Results and reporting](/docs/SFMC-Relay#results-and-reporting) - [What is not supported yet](/docs/SFMC-Relay#what-is-not-supported-yet) - [Client Secret expiration and reminders](/docs/SFMC-Relay#client-secret-expiration-and-reminders) - [Change your MID, Client ID, or Subdomain](/docs/SFMC-Relay#change-your-mid-client-id-or-subdomain) - [Troubleshooting](/docs/SFMC-Relay#troubleshooting) - [FAQ](/docs/SFMC-Relay#faq) ## How SFMC Relay Integration works **Insider One does:** - Audience, segments, and targeting - Email content: the editor, templates, personalization, and recommendations - Rendering the final email for every recipient - Scheduling when each email is sent **Your SFMC account does:** - Sending, through a Trigger Send you create in SFMC - Sender name, From and Reply-To addresses (set on the Trigger Send) - Sending domains, IP addresses, and sender reputation - Suppression handling - Analytics reporting For each recipient, Insider One sends four values to the Trigger Send you select: the email address, the Subscriber Key, the rendered email content (HTML__Content), and the subject line (Subject). > [!NOTE] > SFMC Relay works for promotional bulk emails only for the moment. > [!NOTE] > When a campaign shows emails as **sent** in Insider One, it means your SFMC account accepted them. Delivery happens inside your SFMC account from that point. ## Before you start: what you need in SFMC Your SFMC administrator completes these steps in your SFMC account. ### Step 1: Create an Installed Package 1. In SFMC, go to **Setup > Platform Tools > Apps > Installed Packages** and create a new package. 2. Add an **API Integration** component and choose the integration type **Server-to-Server**. > [!NOTE] > Use a Server-to-Server integration. A Web App integration does not work, because Insider One sends in the background, without a signed-in user. > [!NOTE] > If you use the SFMC User Data Migrator, create a separate package for SFMC Relay. The migrator's package is a Web App integration with different scopes and does not work for sending. ### Step 2: Select the API scopes In the API Integration component, under **Channels > Email**, select: - **Read:** Lets Insider One list your Trigger Sends. - **Write and Send:** Salesforce requires both to fire a Trigger Send. ### Step 3: Collect your connection details You need these values for the setup in Insider One: | Value | Where to find it | | --- | --- | | **Client ID** | The API Integration component of the Installed Package. | | **Client Secret** | The API Integration component of the Installed Package. | | **Client Secret expiration date** | The date you set for the Client Secret in SFMC. | | **Subdomain** | The unique part of the base URIs shown in the API Integration component. For https://mcabc123.auth.marketingcloudapis.com/, enter only mcabc123. | | **MID** | The ID of the SFMC business unit that will send the emails. | ### Step 4: Allow Insider One's IP addresses If your Installed Package restricts IP addresses, add **all three** of these Insider One IP addresses to its allowlist: - 52.213.194.109 - 52.19.197.71 - 3.248.68.7 Both the connection test and the email sending use these addresses. If one of them is missing, some requests fail and Insider One shows an IP restriction error. ### Step 5: Prepare your Trigger Sends Every Insider One campaign sends through a Trigger Send that you create in SFMC Email Studio, under Interactions (SFMC calls it a Triggered Send). Each Trigger Send you plan to use must: - Be **Active** (started) in SFMC. New (never started) or paused Trigger Sends are shown in Insider One but cannot be selected. - Use a **Commercial** send classification. With a Transactional send classification, SFMC does not apply unsubscribes, so people who unsubscribed could receive your promotional emails. - Use an email whose body is the HTML__Content value and whose subject line is the Subject value. Insider One sends only these two values with the email address and Subscriber Key, so do not make any other attribute required. > [!TIP] > Create a separate Trigger Send for each Insider One campaign. You can select the same Trigger Send in more than one campaign, but SFMC reports results per Trigger Send. A separate Trigger Send keeps each campaign's results apart, and lets Insider One show results per campaign in the future. With a shared Trigger Send, only combined results are possible. > [!NOTE] > Salesforce allows up to 500 triggered send and transactional send definitions per business unit in 7 days. Plan the number of new Trigger Sends with this limit in mind. > [!NOTE] > If you delete an active Trigger Send that an Insider One campaign uses, sending for that campaign is directly affected. ### Step 6: Agree on your Subscriber Key SFMC identifies each person by a Subscriber Key, and SFMC's unsubscribes are tied to it. By default, Insider One uses the Insider One user ID as the Subscriber Key. If you use a different key in SFMC today, tell the Insider One team which attribute holds it, so the same person is not treated as a new subscriber in SFMC. > [!NOTE] > Users without a Subscriber Key are skipped and do not receive the email. ### Step 7: Check your Salesforce API limits Insider One makes one API call to your SFMC account for every recipient. These calls count toward your Salesforce limits, together with your other integrations: - Salesforce applies a soft limit of 2,500 synchronous REST API requests per minute. - Your SFMC edition comes with a yearly API call allowance, e.g., Salesforce lists Pro at 2 million, Corporate at 6 million, and Enterprise at 200 million calls per year. A campaign to 1 million recipients uses 1 million calls. Check your allowance with your Salesforce account executive before your first large campaign. ## Set up SFMC Relay in Insider One ### Step 1: Insider One turns on SFMC Relay for your account After your access is approved, Insider One turns on SFMC Relay for your account and sets your sending rate. You cannot turn it on yourself. Tell the Insider One team the size of your largest campaign and any time-critical sends, so your sending rate fits your plans and your SFMC account. ### Step 2: Enter your connection details > [!NOTE] > Only Administrator users can open this tab. 1. Go to **Email Settings > Delivery Provider**. 2. Enter your **MID**, **Client ID**, **Subdomain**, **Client Secret**, and the **Client Secret expiration date**. 3. Click the **Save** button. Insider One tests the connection to your SFMC account. If the test fails, an error is shown and the details are not saved. > [!NOTE] > MID, Client ID, and Subdomain cannot be changed after the first successful save, because changing them moves your sending to another SFMC account or business unit. See [Change your MID, Client ID, or Subdomain](/docs/SFMC-Relay#change-your-mid-client-id-or-subdomain). You can update the Client Secret and its expiration date at any time. ### Step 3: Import your unsubscribe list Export your unsubscribe list from SFMC and import it into Insider One with the Global Unsubscribe import, so Insider One does not target people who already unsubscribed. Repeat this import regularly, and agree with the Insider One team how often. ### Step 4: Send a test email Create a test campaign, select an Active Trigger Send, and send a test email. Check it in a real inbox: sender, subject, content, links, and the unsubscribe link. ### What you do not need For promotional email through SFMC Relay, you do not need IP assignment, domain authentication, link branding, or an IP warm-up in Insider One. You need to handle this within your SFMC account. ## Create a campaign You build the campaign as usual: audience, editor, personalization, and schedule. The difference is on the **Design** step. 1. On the **Design** step, open the **Trigger Send** selector. It takes the place of the sender address. 2. Select a Trigger Send from the list. The list shows the Trigger Sends in your SFMC account, and only Active ones can be selected. 3. Continue and launch the campaign as usual. Good to know: - SFMC Relay has no default Trigger Send. Select one in every campaign. - You can select the same Trigger Send in several campaigns. We recommend a separate one for each campaign. See [Step 5: Prepare your Trigger Sends](/docs/SFMC-Relay#step-5-prepare-your-trigger-sends). - If the Trigger Send you need is not in the list, create and start it in SFMC, then come back to the campaign. - The sender name, From and Reply-To addresses come from the Trigger Send in SFMC. They are not set in Insider One. - Test emails also need an Active Trigger Send. - A campaign cannot be launched without an Active Trigger Send. If the Trigger Send is not Active when a scheduled campaign starts, the campaign is not sent and goes back to draft. ## Unsubscribes - Unsubscribes are handled by your SFMC account. SFMC makes the final check before every email, as long as the Trigger Send uses a Commercial send classification. - Use your SFMC unsubscribe link in your email content, e.g., %%unsub_center_url%%. - Insider One's unsubscribe link, preference link, and unsubscribe groups cannot be used on this path. A campaign that contains them cannot be launched. - Insider One also skips people it already knows as unsubscribed, including the ones from your imported unsubscribe list. > [!NOTE] > Importing your SFMC unsubscribe list is not a one-time step. Repeat the Global Unsubscribe import regularly, so Insider One keeps skipping people who unsubscribed in SFMC. See [Step 3: Import your unsubscribe list](/docs/SFMC-Relay#step-3-import-your-unsubscribe-list). ## Results and reporting | You want to know | Where to look | | --- | --- | | **Was the campaign sent?** | Campaign status in Insider One. "Sent" means your SFMC account accepted the emails. | | **Delivered, bounced** | Your SFMC account. | | **Opens and clicks** | Your SFMC account. Opens and clicks are not available in Insider One yet. | | **Unsubscribes and spam complaints** | Your SFMC account. | | **Results per campaign** | Your SFMC account, per Trigger Send. | ## What is not supported yet These features are not available for emails sent through SFMC Relay: - Analytics reporting and metrics in Insider One, e.g., opens and clicks (use your SFMC reports) - Architect journey emails through SFMC (support is coming, and this page will be updated) - A/B tests and automatic winner selection - Send Time Optimization - Plain text version - AMP emails - Attachments - Custom email headers - Insider One unsubscribe links, preference links, and unsubscribe groups - Double opt-in emails - Sending some promotional campaigns through SFMC and others through Insider One's own delivery in the same account ## Client Secret expiration and reminders Your Client Secret has an expiration date set in SFMC. When it expires, Insider One cannot send emails for your account until the secret is renewed. Insider One reminds you before this happens: - The **Delivery Provider** tab shows a warning from 7 days before the expiration date. - Your Administrator users get reminder emails 30 days, 7 days, and 1 day before the expiration date, and 1 day after it. To renew: 1. Your SFMC administrator creates a new Client Secret in the Installed Package in SFMC. 2. An Administrator user opens **Email Settings > Delivery Provider** in Insider One, enters the new **Client Secret** and its **expiration date**, and clicks the **Save** button. The connection is tested again on save. > [!TIP] > Add the renewal date to your team calendar when you set up SFMC Relay. ## Change your MID, Client ID, or Subdomain MID, Client ID, and Subdomain are locked after the first successful save, because a change moves your sending to another SFMC account or business unit. To change any of them, contact the Insider One team, who request the change for you. ## Troubleshooting | What you see | Likely cause | What to do | | --- | --- | --- | | **The connection test fails when you save** | A connection detail is wrong, the integration is not Server-to-Server, or a scope is missing. | Check the MID, Client ID, Client Secret, and Subdomain (subdomain only, not the full URL). Check that the package is Server-to-Server with Email Read, Write, and Send. | | **IP restriction error (HTTP 403)** | Your Installed Package restricts IP addresses and an Insider One IP address is missing. | Add all three IP addresses in [Allow Insider One's IP addresses](/docs/SFMC-Relay#step-4-allow-insider-ones-ip-addresses). | | **"API Permission Failed"** | The Installed Package is missing a required scope. | Select Email Read, Write, and Send in the API Integration component, then send a test email again. | | **Sending stopped for all campaigns, or the Trigger Send list does not load** | The Client Secret has expired. | Renew the Client Secret. See [Client Secret expiration and reminders](/docs/SFMC-Relay#client-secret-expiration-and-reminders). | | **The Trigger Send list is empty** | No Trigger Sends in the business unit, or a missing scope. | Create and start a Trigger Send in SFMC, and check the scopes. | | **A Trigger Send is listed but cannot be selected** | It is new (never started) or paused. | Start it in SFMC. | | **A campaign cannot be launched, or a scheduled campaign went back to draft** | No Trigger Send is selected, the Trigger Send is not Active, or the content has an Insider One unsubscribe link. | Select an Active Trigger Send. Replace Insider One unsubscribe links with your SFMC unsubscribe link. | | **The campaign shows as sent, but emails did not arrive** | Your SFMC account accepted the emails, and delivery happens in SFMC. | Check the Trigger Send's tracking in SFMC. For problems inside SFMC, open a case with Salesforce Support. | | **An unsubscribed person received an email** | The Trigger Send uses a Transactional send classification, or the person is not unsubscribed in SFMC. | Set the Trigger Send to a Commercial send classification and check the subscriber's status in SFMC. | | **Wrong sender name or address** | The sender is set on the Trigger Send. | Update the Trigger Send's sender profile in SFMC. | | **Fewer emails in SFMC than the audience size in Insider One** | Some users have no Subscriber Key or are unsubscribed. | This is expected for those users. If the difference is large, contact the Insider One team. | For anything not listed here, contact the Insider One team. ## FAQ **Who can use SFMC Relay?** It is currently available for a limited number of accounts only. Contact the Insider One team to ask for access. **Do I need to warm up IP addresses or set up domains in Insider One?** No, your emails are sent from your SFMC account, with the domains and IP addresses you already use there. **Who creates the Trigger Sends?** You do, in SFMC. Insider One does not create or change anything in your SFMC account. It sends through the Trigger Send you select. **Can several campaigns use the same Trigger Send?** Yes, they can. We recommend a separate Trigger Send for each campaign, so each campaign's results stay apart. **Can I send transactional email?** Yes, but not through SFMC. Transactional email is sent from the same Insider One account through Insider One's own email delivery. **Can I see opens and clicks in Insider One?** Not yet. Use your SFMC reports for now. **Can I use SFMC Relay in Architect journeys?** Not yet. Support for journey emails through SFMC is coming, and this page will be updated when it is available. **Who sets the sending speed?** Insider One sets your sending rate during onboarding. Tell the Insider One team about your largest campaigns and time-critical sends. **Is this the same as Insider One Channels in Salesforce Journeys?** No, it is not. That integration lets your SFMC journeys use Insider One channels. SFMC Relay sends the campaigns you build in Insider One through your SFMC account. **What happens if my SFMC account cannot accept emails?** Insider One retries for a limited time. Emails that still cannot be handed to your SFMC account are not sent. They are never sent through another email provider instead.