How do I connect an Omnisend client to Hiro?
Navigate to top right "Account" tab and click on "Manage Accounts"
Add Client Name
Select Omnisend as the Email Provider
In another tab, log into Omnisend for the corresponding client
Click on the option to connect to Omnisend
You’ll be redirected to the authentication page — follow the prompts to authorize the connection with Omnisend
It will redirect you back to Hiro
Click the final confirmation button to complete the connection to begin the client onboarding
The backfill will take ~24 hours to complete and you will receive an email notification when it is done
What are the limitations with Omnisend data?
Because of the way Omnisend’s API is structured, there are a few important limitations to keep in mind when viewing analytics in Hiro:
No Order-Level Data
Omnisend does not provide order-level attribution details. As a result, Hiro can only display the total revenue attributed to your email and SMS campaigns or flows — not break it down by specific products or customer segments.
No Product-Level Insights in Campaign Deep Dives
Without access to order-level data, Hiro cannot show which specific products contributed to the revenue generated from a campaign.
No Campaign/Flow Creative Visuals
Omnisend does not provide a way to capture the creative asset for each campaign/flow message. As a result, links or previews of those visuals will not be available in Hiro.
No Visibility Into New vs. Returning Customer Revenue
Because detailed order information isn’t available, metrics splitting revenue from first-time vs. returning customers will not appear in your analytics.
No Store-Wide Revenue Comparison
Omnisend’s API does not provide total store revenue data. This means Hiro can’t calculate what percentage of overall store revenue is attributed to email and SMS campaigns.No List Growth or Subscriber Data ... yet
This data is not available in this version of our integration but may be possible to add in future versions.
Differences in Reported Revenue
Hiro is using the Omnisend Reporting API, which aggregates revenue based on the day the attributed order was placed, as opposed to the day the message was received.
For example, if someone clicked an email on August 31st, but then ordered on September 1st, Hiro would report that revenue as part of September, where Omnisend would report that revenue as part of August.
This will create a small difference between Omnisend in-platform revenue reporting (which uses message date attribution) and Hiro (which uses the Reporting API's order date attribution).
Client not connecting or have any other questions about the Omnisend integration? Message us in Slack anytime.