A Copernica integration sends campaign, contact, and list data from Copernica into SEINō. This page shows how to connect it, what SEINō receives, and when to extend the default setup.
What SEINō receives
Section titled “What SEINō receives”Campaign dataset
Section titled “Campaign dataset”SEINō reads Copernica campaign activity from both Publisher and Marketing Suite and exposes the following default campaign-level data in the Campaigns dataset.
| Dimension | Description |
|---|---|
| Campaign name | The Copernica directory path, used as the campaign name in SEINō. |
| Template ID | The Copernica template ID. |
| Template name | The Copernica template name. |
| Template group | A derived template group value used for reporting. |
| Template language | A derived template language value used for reporting. |
| Document ID | The Copernica document ID. |
| Document name | The Copernica document name. |
| Subject | The message subject line. |
| Source system | Which Copernica system produced the event: Publisher or Marketing Suite. |
| Link URL | The clicked URL, when the event is a click. |
| 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 complaints received. |
| Unsubscribes | Number of unsubscribe events. |
| Deliverability | Deliverability rate. |
Contacts
Section titled “Contacts”SEINō does not sync Copernica contact data by default. Contact data only enters SEINō when you explicitly enable contact syncing on the integration and add the fields you want to import.
When contacts are turned on, SEINō reads the profile create and update logfiles on each pipeline run and stores the profile history in your workspace. The contacts dataset includes the profile ID, timestamps, and any contact fields you add to the integration.
Contact fields let you bring over the specific profile attributes that matter for reporting or analysis. For example, you can add fields like lifecycle stage, language, market, customer type, or any other profile property that exists in your Copernica setup. These fields show up as extra dimensions in SEINō reports, so you can go deeper when you need more detailed reporting. SEINō stores only the fields you configure, so you can keep the sync as minimal or as rich as you need.
| Field | What it means |
|---|---|
id |
The Copernica profile ID. |
created_at |
When the profile was first created. |
updated_at |
When the profile was last updated. |
| Contact fields | Any additional contact fields configured on the integration. |
Contacts are optional. If you do not enable them, SEINō skips the contact sync and stores no contact data.
List membership
Section titled “List membership”SEINō can turn Copernica tracked views into list membership snapshots.
Each tracked view becomes a list in SEINō. It uses the view name as the list name, stores the Copernica view ID, and pulls the profile IDs that belong to that view. The snapshot is written once per day for the selected views.
| Field | What it means |
|---|---|
list |
The tracked view name. |
list_id |
The Copernica view ID. |
ids |
The Copernica profile IDs in that view. |
Tracked views are admin-managed. If a tracked view is missing or archived, SEINō skips it and keeps syncing the rest.
Set up integration
Section titled “Set up integration”Connect Copernica to SEINō and start syncing campaign, contact, and list data with the standard integration setup.
- Add the Copernica integration in SEINō.
- Create an access token in Copernica through the API access token page.
- Paste the access token into SEINō.
- Confirm SEINō shows the Copernica account identity returned by Copernica.
- Decide whether contacts should sync, and enable contact syncing if you need profile data.
- Add the Copernica views you want to use for list membership.
- Save the integration.
The Copernica REST API provides the mailing data, so the integration depends on a valid access token before any sync can start.
While you configure the integration, SEINō can list Copernica databases, database views, and child views. That makes it easier to choose the right tracked views before you save.
If your workspace uses tracked views, make sure the views still exist in Copernica before you rely on the list counts. SEINō will ignore archived views, but it cannot build membership from a missing one.
Send additional campaign data
Section titled “Send additional campaign data”Copernica does not need a separate metadata syntax to enrich campaign reporting.
It already reads the campaign metadata that Copernica exposes in its templates, documents, and directories. For click tracking, you can add UTM parameters to the destination URLs and SEINō stores those values on the click events.
If you want more contact detail in SEINō, add the relevant profile fields to the integration so they are included in the contacts dataset.
Refresh cadence
Section titled “Refresh cadence”Copernica refreshes on the regular pipeline schedule.
- Campaign data is refreshed on every pipeline run.
- Subscriber lists are snapshotted for the selected views, and the snapshot is written once per day.
- Contact fields are opt-in. When enabled, SEINō fetches profile creates and updates from the Copernica logfiles for the date being processed.
The result is per-run campaign and contact refreshes, plus a once-daily subscriber list snapshot unless the integration is reconfigured.
Limits and notes
Section titled “Limits and notes”Copernica has a few setup rules that are worth keeping in mind before you rely on the sync.
- SEINō only reads campaign events from the Publisher and Marketing Suite logfile families it knows how to interpret.
- Archived databases and archived views are filtered out.
- Contacts only sync when contact syncing is enabled, and no contact data is stored otherwise.
- Contact fields are opt-in and only imported when you configure them.
- List membership only works for tracked views that you have added to the integration.
- If a tracked view no longer exists, SEINō skips it instead of failing the whole sync.
- Click UTM values are only available when the URL actually contains those parameters.
Why is list membership empty?
List membership only appears after you add tracked views to the integration. If the view was archived or deleted in Copernica, SEINō skips it and the list stays empty until you pick a valid view.
Why are contacts not syncing?
Contacts only sync when contact syncing is enabled. SEINō also ignores archived databases, so the database needs to be active in Copernica before the profile data can land in SEINō.
Do I need to add special UTM settings?
No. SEINō reads UTM values from the click URL when Copernica includes them. If the link does not contain a UTM parameter, that field stays empty.