Skip to content

Salesforce Marketing Cloud

Send Salesforce Marketing Cloud email data to SEINō with daily Data Extension exports

Connect Salesforce Marketing Cloud Engagement to SEINō to see how your emails perform across campaigns and journeys. SEINō brings sends, opens, clicks, bounces, and unsubscribes together in your workspace, where you can explore the results and build reports. Your team sends this data through daily exports. An optional account connection helps verify access, but it does not bring in campaign results on its own.

Tell support@seino.ai which email results and audiences you want to analyze. We will agree on the data to include and where your team should send the daily files. We can provide a Google Cloud Storage destination or arrange another location. Your Salesforce Marketing Cloud administrator can then follow the setup steps below.

SEINō puts Salesforce Marketing Cloud email activity in the Campaigns dataset. A dataset is the collection of fields and metrics you can use in reports. The tables show what you can compare and measure. Send log details and clicked-link fields appear only when your exports include them.

Dimension Description
Email name Name of the email in SFMC.
Journey name Name of the journey, when the send belongs to one.
Journey activity name Name of the sending activity in the journey.
Journey version Version of the journey, when available.
Subject Subject from the send log, or the email subject when the send log has none.
Preheader Preview text from the send log, when exported.
Preview View-online URL from the send log, when exported.
Link name Name of the clicked link.
Link URL URL recorded for the click.
UTM source utm_source value in the clicked URL.
UTM medium utm_medium value in the clicked URL.
UTM campaign utm_campaign value in the clicked URL.
UTM term utm_term value in the clicked URL.
UTM content utm_content value in the clicked URL.
Send date Date the message was sent.
Event date Date of the recorded response.

The export can also include additional send log columns. SEINō must map those columns before they become reporting dimensions. Contact support@seino.ai to plan the mapping.

You can add subscriber details and list membership to your reports. These need extra daily exports. A subscriber file can contain IDs and the attributes you choose. To follow a list, send a file of its members each day. SEINō uses that file as a snapshot and reads the list name from its file name. You still manage the list in Salesforce Marketing Cloud.

Tell support@seino.ai which subscriber fields and lists you want before setting up these exports. They are not included automatically with campaign data.

The daily files bring your campaign data into SEINō. Your Salesforce Marketing Cloud administrator schedules them in Automation Studio and sends them to a location we agree on together. SEINō can provide a Google Cloud Storage bucket. Connecting the account through the API is optional: it verifies access and shows the bucket details in SEINō, but the exports still provide the reporting data.

Your Salesforce Marketing Cloud administrator creates the daily files from Data Extensions in Automation Studio. This works without an API connection. The administrator needs access to create Data Extensions, SQL queries, extracts, and file transfers, plus the destination and path agreed with SEINō.

Configure a Google Cloud Storage destination

Section titled “Configure a Google Cloud Storage destination”
  1. Ask SEINō for the bucket name, relative path, and service account key for your workspace. The SFMC integration screen shows bucket details after an API account is connected; for an export-only setup, get them from support@seino.ai.
  2. In SFMC, open Setup → Data Management → File Locations and create a Google Cloud Storage location. Enter the supplied bucket name and relative path, then upload the service account key. Do not add a leading or trailing slash to the relative path. See Salesforce’s Google Cloud Storage file location guide.
  3. Save the file location and use it as the destination for the automation’s file transfer activities.

Other SFMC file location types include cloud storage and SFTP. If you want to send files somewhere other than the SEINō bucket, agree the transfer into SEINō with support before configuring the automation.

Prepare message, response, and send log data

Section titled “Prepare message, response, and send log data”

Create three Data Extensions for the daily export. Use SQL query activities to populate them from SFMC data views and your send log Data Extension. Keep the field names in the table: SEINō’s file importer expects them.

Export Source Required fields
Messages _Sent, joined to _Job and optionally _Journey and _JourneyActivity EventDate, AccountID, JobID, BatchID, SubscriberID, SubscriberKey, Domain, EmailName, EmailSubject. Include JourneyName, JourneyActivityName, and JourneyVersion when available.
Responses _Open, _Click, _Bounce, _Complaint, and unsubscribe activity Event, EventDate, AccountID, JobID, BatchID, SubscriberID, SubscriberKey. Include LinkName, LinkContent, and BounceCategory where relevant. Use open, click, bounce, complaint, and unsubscribe as event values.
Send log Your send log Data Extension JobID, BatchID, SubscriberID. Include EventDate, Subject, Preheader, ViewOnlineUrl, and any custom fields you want SEINō to map.

The messages and send log files are joined on JobID, BatchID, and SubscriberID. If your send log uses SubID, rename it to SubscriberID in the export query. When a send log subject is empty, SEINō uses EmailSubject from the messages file.

Use a query window that overlaps the previous day’s export so late SFMC events can be included. The internal SEINō setup uses a 30-hour lookback and filters out test sends. Test the queries and inspect one row of each Data Extension before scheduling the automation. Salesforce describes how to build a SQL query activity.

In Automation Studio, create a daily automation in this order:

  1. Run the SQL query activities that populate the three Data Extensions.
  2. Add a Data Extension Extract activity for each one. Include column headers and use a tab delimiter. In SFMC, use the file naming patterns %%Year%%-%%Month%%-%%Day%%_messages.csv, %%Year%%-%%Month%%-%%Day%%_responses.csv, and %%Year%%-%%Month%%-%%Day%%_send_log.csv. The resulting files use a YYYY-MM-DD date prefix.
  3. Convert the extracted files to UTF-8 if your SFMC extract workflow requires a File Convert activity.
  4. Add File Transfer activities that move the files from Safehouse to the agreed destination. Match each transfer’s file name to its extract’s file name.
  5. Run the automation once manually. Confirm that all three files arrive and then enable the daily schedule.

Salesforce documents the Data Extract activity and the File Transfer activity.

To add subscriber data, arrange a daily full snapshot of subscriber IDs with SEINō. The standard file name is YYYY-MM-DD_subscribers.csv. For named list snapshots, export one file per list using YYYY-MM-DD_subscribers_<list-name>.csv. Each list file needs an Id column containing the subscriber ID; use a consistent ID across days. SEINō reads the list name from the part of the file name after subscribers_.

Send the files to the same agreed integration path as the campaign exports. The exact subscriber attributes and lists depend on your SFMC setup, so confirm the columns and file names with support@seino.ai before scheduling them. See Multiple integrations in one workspace if this workspace combines Salesforce with another platform.

You need permission to create an installed package in SFMC and access to Workspace settings → Integrations in SEINō.

  1. In SFMC, go to Setup → Apps → Installed Packages and create a package with an API Integration component. Choose a server-to-server integration.
  2. Give the component read, write, and execute access to Automations, and read and write access to Data Extensions and File Locations. SEINō checks these permissions when you connect. See Salesforce’s installed package instructions.
  3. Copy the Authentication Base URI, Client ID, and Client Secret. Salesforce shows the client secret when you create the component, so store it securely.
  4. In SEINō, open Workspace settings → Integrations → Salesforce and select Enable or Add account.
  5. Enter the three values and select Confirm. Check that the SFMC account appears in the connected accounts list.

The account connection confirms the credentials and required permissions. It does not import campaign events or create the daily export files described above.

After the first export, open the Campaigns dataset in SEINō. Find a recent SFMC email and compare its email name, send date, sent count, and one response metric with SFMC. If you exported a send log, check a subject or custom field from it. If you exported subscriber lists, check that a named list appears and its size matches the snapshot you sent.

For an API-connected account, confirm that it appears under Connected accounts. That verifies the connection; use the campaign data check to verify that reporting data has arrived.

Your results update after the daily files arrive and SEINō processes them. The first results appear once a complete set of files has been delivered and processed. Contact support if you need a different schedule.

  • The file route needs matching message, response, and send log files for the dates you want to import. Missing files can prevent a complete campaign sync.
  • Send log fields and subscriber attributes are specific to your SFMC setup. SEINō must map custom fields before you can use them in reports.
  • UTM fields come from clicked URLs. They are empty when a message has no recorded click or the URL has no UTM parameters.
  • Salesforce’s data views have a limited history. The amount of historical data available depends on what remains in SFMC and what you export. See Salesforce’s data view guidance.
  • This page covers Marketing Cloud Engagement email data. It does not describe Sales Cloud CRM data.
Symptom What to check
SEINō rejects the API credentials Check the Authentication Base URI, Client ID, Client Secret, and installed-package permissions.
The account is connected but no campaigns appear Confirm which data feed is configured, then check that the expected files arrived for the selected date range.
An export file is missing Compare the extract and file-transfer naming patterns, the automation run history, and the destination path.
Send log fields are empty Check that JobID, BatchID, and SubscriberID match the messages file and that SEINō mapped the fields.
A subscriber list is missing Check that the dated file contains an Id column, uses the agreed list name, and arrived in the correct path.

If the source files arrived but the data still does not appear, contact support@seino.ai with the affected date, file name, and SFMC account or business unit.