Connect Customer.io to SEINō and send email campaign and message event data into your workspace
A Customer.io integration sends email campaign and message event data from Customer.io into SEINō. Use this page to connect Customer.io, see what SEINō receives, and configure the data export required for the sync.
Supported channels
Section titled “Supported channels”The Customer.io integration currently imports email message events. SEINō includes messages sent from both Customer.io campaigns and newsletters in the Campaigns dataset.
What SEINō receives
Section titled “What SEINō receives”Campaign dataset
Section titled “Campaign dataset”SEINō combines Customer.io campaign actions and newsletter content with the Deliveries and Metrics exports from Customer.io. The following campaign-level dimensions are available in the Campaigns dataset.
| Dimension | Description |
|---|---|
| Broadcast type | Whether the message came from a Customer.io Campaign or Newsletter. |
| Campaign ID | The Customer.io campaign or newsletter ID. |
| Campaign name | The campaign or newsletter name in Customer.io. |
| Content name | The campaign action or newsletter content name. |
| Subject | The email subject line. |
| Preheader | The email preheader text, when provided by Customer.io. |
| Preview | A Customer.io delivery preview URL for send events. |
| Link ID | The Customer.io link ID for click events. |
| Link URL | The URL recorded for the clicked link. |
| UTM source | The utm_source value read from the clicked URL. |
| UTM medium | The utm_medium value read from the clicked URL. |
| UTM campaign | The utm_campaign value read from the clicked URL. |
| UTM content | The utm_content value read from the clicked URL. |
| UTM term | The utm_term value read from the clicked URL. |
| Metric | Description |
|---|---|
| Sent | Number of messages sent. |
| Delivered | Number of messages successfully delivered. |
| Opens | Number of unique opens. |
| Open rate | Open rate calculated as a percentage of delivered messages. |
| Clicks unique | Number of unique clicks. |
| Click rate | Click rate calculated as a percentage of delivered messages. |
| Click to open rate | Click-to-open rate. |
| Soft bounces | Number of soft bounces. |
| Hard bounces | Number of hard bounces. |
| Complaints | Number of messages marked as spam. |
| Unsubscribes | Number of unsubscribe events. |
| Deliverability | Deliverability rate. |
Customer.io Metrics and Deliveries exports are joined on the delivery ID. Events without a matching campaign action or newsletter content are not included in the campaign dataset.
Set up integration
Section titled “Set up integration”Customer.io setup has two parts: connect your account in SEINō, then configure Customer.io to export Deliveries and Metrics to the SEINō Google Cloud Storage bucket.
Step 1: Connect Customer.io to SEINō
Section titled “Step 1: Connect Customer.io to SEINō”- Add and enable the Customer.io integration in SEINō.
- Select the region where your Customer.io account is hosted:
EUorUS. - In Customer.io, create an App API key from the account settings page.
- Paste the App API key into the App API key field in SEINō.
- Select Confirm.
The selected region must match your Customer.io account. SEINō uses the EU API endpoint for EU accounts and the US API endpoint for US accounts.
Step 2: Set up data sync in Customer.io
Section titled “Step 2: Set up data sync in Customer.io”- Open the Customer.io Google Cloud Storage integration.
- Configure exports for both Deliveries and Metrics.
- Use the bucket details shown in the Customer.io integration setup in SEINō.
- Set the export path to
customerio. - Save and enable the exports in Customer.io.
After you complete the Customer.io export setup, it can take several hours before data is visible in SEINō. If no data appears after 24 hours, contact support@seino.ai.
Send additional campaign data
Section titled “Send additional campaign data”SEINō reads campaign actions, newsletter content, and the message events delivered through the Customer.io exports. It’s currently not possible to add additional customer data attributes.
For click reporting, include UTM parameters in the destination URLs used in your Customer.io messages. SEINō reads those values from click URLs and stores them at link level. A UTM field remains empty when the clicked URL does not contain that parameter.
Refresh cadence
Section titled “Refresh cadence”SEINō processes Customer.io event files multiple times per day.
Limits and notes
Section titled “Limits and notes”- The integration currently supports email message events only.
- Both the App API connection and the Customer.io Google Cloud Storage exports are required for a complete sync.
- The region selected in SEINō must match the region hosting your Customer.io account.
- Only events that can be matched to a Customer.io campaign action or newsletter content are included.
- UTM values are available only on click events and only when the clicked URL contains the corresponding UTM parameter.
- Customer.io historical data is limited to the dates available in the configured Deliveries and Metrics exports.
Why is the API key rejected?
Make sure you created an App API key, not another Customer.io credential, and that the selected region in SEINō matches your Customer.io account. You can create the key from the Customer.io account settings page.
Why are campaigns connected but no data appears?
Connecting the API key is only the first setup step. Configure both the Deliveries and Metrics Google Cloud Storage exports in Customer.io and use the bucket details shown in SEINō. The first files can take several hours to arrive.
Why are some events missing?
SEINō includes events that match a Customer.io campaign action or newsletter content record. It skips events that cannot be matched to either source, and it cannot populate UTM fields when the clicked URL does not contain them.