Skip to main content
Omnisend campaign and automation definitions appear in dim_outbound_messages beside your other messaging providers. SourceMedium builds further Omnisend reporting models after the first brand connects Omnisend, so Omnisend performance may not appear in prebuilt reports yet. Omnisend performance reports use UTC send-date definitions and remain separate from event-date email/SMS performance.
Omnisend is an email and SMS marketing platform for ecommerce brands. SourceMedium reads your Omnisend campaign and automation reporting, by send date and channel, every six hours and lands it in your warehouse.
Sign in to SourceMedium, open your store, then choose Data sources → Connect data source and select the platform. You need an Admin or Editor workspace role.After you connect explains the first sync and connection statuses.

​
Vendor documentation

​
Requirements

  • An Omnisend API key with five read permissions: campaigns.read, analytics.read, segments.read, automations.read and email-templates.read. SourceMedium does not need write access.
  • If a read permission is missing, SourceMedium keeps the accepted key and identifies the missing access on the connection. Add that permission in Omnisend, then save the key again. Metadata permissions are checked before the quota-bound reporting request.
Omnisend allows each brand 55 reporting requests per rolling 24 hours, and 10 a minute, shared by every tool and key on your account. SourceMedium uses 4 a day for routine syncs, 1 when you connect, and about 16 once to load your history. If your other tools use most of that budget, SourceMedium’s reporting sync waits until Omnisend frees it up. Nothing is lost: the next sync re-reads the window.

​
How to connect

1

Create an API key

In Omnisend, open Store settings > API keys (direct link) and create a key for SourceMedium with all five read permissions listed above.
2

Add the key in SourceMedium

Find Omnisend in the connector picker and click Connect. Paste the API key, then click Save.
3

Confirm it is connected

SourceMedium checks the key with Omnisend before saving it, including one small reporting request, so a wrong key is rejected on the spot. The connection reads Awaiting first data until the first sync lands, then Connected.
SourceMedium only ever reads from your connected platforms. It does not create, change, or delete anything, so create the key with read-only access wherever the platform offers it. Treat it like a password: keep it confidential and avoid sharing it over email or in spreadsheets. If the credential is rotated or revoked, follow this guide’s connection method to update SourceMedium.

​
What data syncs

The report carries Omnisend’s send-date metrics:
  • Delivery: sent, failed, spam complaints, unsubscribes, and the SMS send cost.
  • Engagement: opens and clicks, total and unique, with their rates.
  • Attribution: attributed orders and attributed revenue, with per-order and per-message averages.
Rates and averages are Omnisend’s own ratios. When you aggregate across days or messages, recompute them from the counts and revenue. Omnisend reports revenue in your store currency without a currency code, so the table has none. report_timezone records the timezone the report was requested in. The campaign table holds each campaign’s name, status, type, channel, timestamps, and its audience, content, and sending settings as JSON. Shopper contacts are not imported. On a dedicated warehouse, you can also receive these source tables in your_project.sm_sources: select them under Warehouse → Raw data in your SourceMedium workspace. See Foundation and Pro.

​
Refresh and history

  • Refresh: every six hours. Once a day the last 30 days of reporting are re-read and replaced; the other syncs re-read the last 7 days. The campaign, segment, automation and template catalogs are read in full on every sync.
  • History: the first sync loads up to five years of reporting, the most Omnisend’s Reports API serves.

​
Known gaps

  • Shared reporting budget. See the warning above. A brand whose other tools spend most of its 55 daily reporting requests sees SourceMedium’s reporting arrive later.
  • Different reporting grains. Campaign and automation reports use UTC send date. An automation report can cover the whole workflow; its counts do not establish performance for an individual message block. Campaign contentID values identify design content, not template-library IDs.
  • Deleted catalog objects keep their last landed row. Catalog rows describe current known configuration, not a history of changes or a record that a draft was sent.