Connect Klaviyo to SEINō and send campaign, flow, contact, segment, and conversion data into your workspace
A Klaviyo integration sends campaign, flow, contact, segment, and conversion data from Klaviyo into SEINō. Use this page to connect Klaviyo, understand what SEINō receives, and troubleshoot the sync.
Supported channels
Section titled “Supported channels”The Klaviyo integration imports campaign and message events for email and SMS.
| Channel | What SEINō imports |
|---|---|
| Campaigns, flows, delivery and engagement metrics, contacts, segments, and attributed conversions. | |
| SMS | Campaign and message events. |
What SEINō receives
Section titled “What SEINō receives”Campaigns and flows
Section titled “Campaigns and flows”Klaviyo campaigns are one-time sends. Klaviyo flows are automated message sequences triggered by customer activity or profile changes. SEINō combines both into the Campaigns dataset so you can compare one-time campaigns with automated journeys.
| Dimension | Description |
|---|---|
| Send date | The date the message was sent. |
| Event date | The date of the recorded event. |
| Account | The connected Klaviyo account name. |
| Channel | The delivery channel for supported Klaviyo message events. |
| Message type | Whether the message belongs to a Campaign or Flow. |
| Flow ID | The Klaviyo flow identifier, when the message belongs to a flow. |
| Flow name | The Klaviyo flow name, when the message belongs to a flow. |
| Campaign name | The Klaviyo campaign or message name. |
| Message ID | The Klaviyo message identifier. |
| Subject | The email subject line. |
| Preheader | The email preheader text. |
| Source | The Klaviyo $source property associated with the recipient. |
| Lifecycle stage | The lifecycle stage derived from order history. |
| Day | The day component of the send date. |
| Week | The week component of the send date. |
| Month | The month component of the send date. |
| Year | The year component of the send date. |
| Year-week | The year and week grouping for the send date. |
Message events and metrics
Section titled “Message events and metrics”SEINō imports message events from Klaviyo and maps them to the standard campaign metrics used in SEINō reporting.
| Metric | Description |
|---|---|
| Sent | Number of messages sent. |
| Delivered | Number of messages sent minus soft and hard bounces. |
| Opens | Number of unique human opens, excluding machine activity. |
| Opens (%) | Open rate calculated as a percentage of delivered messages. |
| Opens incl. bots | Opens including machine activity. |
| Opens incl. bots (%) | Open rate including machine activity. |
| Clicks unique | Number of unique human clicks, excluding bot activity. |
| Clicks unique (%) | Click rate calculated as a percentage of delivered messages. |
| Click to open (%) | Click-to-open rate. |
| Clicks all | Total human clicks, including repeated clicks. |
| Clicks unique incl. bots | Unique clicks including bot activity. |
| Clicks unique incl. bots (%) | Click rate including bot activity. |
| Bot opens | Number of opens attributed to bots. |
| Bot clicks | Number of clicks attributed to bots. |
| Soft bounces | Number of soft bounces. |
| Soft bounces (%) | Soft bounce rate. |
| Hard bounces | Number of hard bounces. |
| Hard bounces (%) | Hard bounce rate. |
| Complaints | Number of messages marked as spam. |
| Complaints (%) | Complaint rate. |
| Unsubscribes | Number of unsubscribe events. |
| Unsubscribes (%) | Unsubscribe rate. |
| Deliverability (%) | Deliverability rate. |
| Metric | Description |
|---|---|
| Average order value (Klaviyo) | Attributed revenue divided by attributed transactions. |
| CVR clicks (Klaviyo) | Conversion rate based on unique clicks, including bots. |
| CVR opens (Klaviyo) | Conversion rate based on opens. |
| CVR sent (Klaviyo) | Conversion rate based on sent messages. |
| Revenue (Klaviyo) | Revenue attributed to Klaviyo messages. |
| Transactions (Klaviyo) | Number of attributed conversion events. |
Klaviyo event names are mapped to standard SEINō events. For example, Received Email becomes a send, Opened Email becomes an open, and Clicked Email becomes a click. Machine opens and bot clicks remain available so you can report them separately from human engagement.
Contacts
Section titled “Contacts”SEINō imports Klaviyo profiles into the Contacts dataset. A profile is the Klaviyo record for an individual recipient or customer.
SEINō also derives a lifecycle stage from order history:
Non-buyer: no historical orders.First-time buyer: one historical order.Repeat buyer: more than one historical order.
Segments
Section titled “Segments”A Klaviyo segment is a group of profiles that matches a set of rules. SEINō can sync configured Klaviyo segments as list membership data and use them as reporting dimensions.
Each synced segment includes the segment name, segment ID, and the Klaviyo profile IDs that belong to it. SEINō also provides standard segments for active users, subscribed active users, and lifecycle stages when segment support is enabled for the workspace.
If a segment is removed from Klaviyo, SEINō stops refreshing its membership after the segment’s removal date.
Set up integration
Section titled “Set up integration”Connect Klaviyo to SEINō with Klaviyo’s OAuth authorization. You do not need to copy an API key into SEINō.
Connect Klaviyo to SEINō
Section titled “Connect Klaviyo to SEINō”- Open the Klaviyo integration in your SEINō workspace settings.
- Select Enable or Add account.
- Sign in to Klaviyo if prompted.
- Review the requested permissions and select Allow.
- Return to SEINō and confirm that the Klaviyo account appears in the integration.
If authorization is declined, select Enable again and complete the Klaviyo authorization flow. For more about Klaviyo’s own campaigns, flows, profiles, and segments, see the Klaviyo Help Center.
Configure conversion attribution
Section titled “Configure conversion attribution”SEINō uses Klaviyo’s attribution relationships to connect conversion events to messages. The default configuration uses Klaviyo’s available attribution data.
SEINō can also use a clicks-only, three-day attribution rule. With that rule, a conversion is included only when it is attributed to a click and occurs within three days of the click. If you need a different attribution configuration, contact support@seino.ai.
GA4 attribution with UTM tags
Section titled “GA4 attribution with UTM tags”SEINō uses UTM parameters to identify which Klaviyo message your GA4 data belongs to. Your tags need to distinguish individual messages so SEINō can match GA4 sessions, transactions, and revenue to the correct campaign or flow message.
Configure Klaviyo to include the following identifiers in your UTM parameters:
| Message type | Recommended identifier |
|---|---|
| Campaign | Campaign ID |
| Flow | Flow message name (flow message id) |
Use a consistent parameter, such as utm_term, to carry the identifier.
To configure tagging in Klaviyo:
- Open Settings → Other → UTM tracking.
- For your chosen parameter, select dynamic values that include the campaign ID under Campaign Value and the individual flow message ID under Flow Value.
- Turn on Automatically add UTM parameters to links and save your changes.
- Check existing campaigns and each flow message. Messages with custom tracking parameters or disabled UTM tracking need separate updates.
For the current settings and message-level options, see Klaviyo’s guide to adding UTM tracking.
Check the destination URL from a sent message to confirm that the expected ID reaches your website. If you already use a different tagging convention, contact support@seino.ai to confirm how SEINō should match it. Changing your tags affects future traffic; it does not add missing identifiers to historical GA4 data.
Refresh cadence
Section titled “Refresh cadence”SEINō processes Klaviyo event files approximately every three hours.
Limits and notes
Section titled “Limits and notes”- OAuth authorization is required for each Klaviyo account you connect.
- Klaviyo profile data is imported as contact history; profile properties remain in the
propertiesfield rather than becoming separate dimensions automatically. - Segments must be configured for the integration before their membership can appear in SEINō.
- Conversion metrics depend on the event and attribution data available from Klaviyo.
- Available contact, segment, event, and conversion history depends on the integration start date and the data Klaviyo returns during the first sync.
- Machine opens and bot clicks are retained separately so you can choose whether to include them in engagement analysis.
Why was my Klaviyo authorization declined?
The authorization was not completed. Select Enable again, sign in to the correct Klaviyo account, review the requested permissions, and select Allow.
Why does my Klaviyo account appear but have no data?
The initial sync needs time to retrieve campaigns, flows, profiles, segments, events, and conversions. If the account remains empty after the next scheduled refresh, contact support@seino.ai.
How can I distinguish flow messages from campaigns?
SEINō labels each message as a Campaign or Flow so you can compare one-time sends with automated journeys. Flow messages use the flow ID and flow name, while campaign messages use the campaign and message names.
Why are conversion totals different from Klaviyo?
Check the attribution rule, date range, currency settings, and whether the conversion event is linked to a Klaviyo message. SEINō reports the conversion events and attribution relationships returned by Klaviyo.
Why is a Klaviyo segment empty?
The segment must be configured for the integration and active in Klaviyo. A removed segment stops refreshing after its removal date.
Klaviyo documentation
Section titled “Klaviyo documentation”SEINō does not document how to build campaigns, flows, messages, or segments in Klaviyo. Use the Klaviyo Help Center for those tasks.