Multiple integrations in one workspace

You might be migrating between providers or running two ESPs side-by-side. Either way, SEINō lets you connect more than one integration to a workspace — the real question is what works best for you?

Why this matters to you

Campaign-level reporting (the Campaigns dataset) is a key area to consider when combining integrations. It acts as the aggregation point for campaign metadata, performance metrics, and revenue from web analytics. If multiple integrations write to the same dataset, the values they send need to line up so your reports make sense. When they don’t, dashboards show duplicates, counts drift, and attribution breaks.

Different providers model similar marketing concepts differently. For example, one integration might expose template name, template group, and document name, while another provides flow name or campaign name. Those labels can describe the same activity but are not interchangeable without mapping or transformation.

Practical options

Keep integrations in separate workspaces

This is the simplest path. Keeping sources separate prevents accidental mixing of dimensions and keeps historical and new data distinct. Choose this when the integrations’ data models are very different or you need a clear separation for reporting.

You should use separate workspaces when:

• the integrations use different naming or dimension conventions
• you need a clean historical record separated from new data
• reporting simplicity is a priority

Combine multiple integrations in one workspace

You can add more than one integration to the same workspace. Each integration brings its own dimensions, and they are available together in the same workspace.

This is useful when you want to combine marketing email data with transactional email data from a different sending platform.

Add an extra integration, then archive the old one

You can add the new integration to the same workspace while the old integration remains active. That means you’ll temporarily have dimensions from both integrations side-by-side in the same workspace. After you confirm the new integration is collecting the data you need, you can disable the old integration and keep it as an archive.

When you archive the old integration, we can map its fields to the new integration’s canonical fields so historical data remains consistent. For example, Copernica’s document name often maps to Klaviyo’s campaign name. In many cases these fields represent the same marketing activity and can be aligned with mapping rules and transforms. We can do this work for you, and we will provide a quote for the custom mapping effort up front.

This approach reduces downtime and gives you a chance to validate mappings before you fully switch reporting to the new provider.

When you archive an integration, SEINō stops attaching new events to that integration’s historical records. For example, GA4 events that occur after you archive an integration will not be stitched to the archived campaign, so the campaign’s data in SEINō will remain unchanged.