Omnisend integration

Skio's Omnisend integration syncs subscription lifecycle and billing events from your Skio store to Omnisend via webhooks, so you can trigger automated email and SMS workflows the moment a subscription action occurs. You'll also sync subscription data to contact profiles for personalization.

What is the Omnisend integration?

For detailed setup instructions and troubleshooting refer to Omnisend’s official documentation, Integrate Skio with Omnisend. Because this integration is owned and maintained by Omnisend, contact Omnisend directly with any questions or issues.

The Omnisend integration connects your Skio subscription program to Omnisend's email and SMS marketing platform. Once enabled, Skio sends subscription events to Omnisend in real time, which you can use to trigger automations and personalize messaging.

Common use cases include:

Welcome and onboarding flows: Trigger an email series the moment a customer starts a new subscription.
Win-back campaigns: Re-engage subscribers after a cancellation with a targeted sequence.
Payment recovery: Send dunning emails and payment update requests when a charge fails.
Renewal reminders: Reach subscribers before their next charge to reduce disputes and surprise cancellations.
Re-engagement flows: Message subscribers when they pause or skip an upcoming order.

How do I set up the Omnisend integration?

Step 1: Connect Skio in Omnisend

In Omnisend, go to App Market and search for Skio.
Click Connect now. You'll be taken to the Skio app settings page in Omnisend.
Copy the Webhook URL shown under the Automations section. Keep this URL handy, you'll paste it into your Skio Dashboard in the next step.

Step 2: Enable the custom webhook integration in Skio

In your Skio Dashboard, go to API & Integrations > Integrations.
Find Custom Webhook Integration and click Enable.
You'll be redirected to the Custom Webhook Integration settings page.
Paste the Webhook URL you copied from Omnisend.
Click Save.
Confirm the toggle shows Connected.

Step 3: Add and test events in Skio

On the Custom Webhook Integration page in your Skio Dashboard, click + Add events.
Select the subscription events you want to send to Omnisend. See the full event list below.
After adding each event, click Send test.

Omnisend only registers a custom event after receiving at least one payload. If you skip the test, the event won't appear as an available trigger in Omnisend. Always send a test for every event you enable.

Step 4: Confirm the connection in Omnisend

Return to the Skio app settings page in Omnisend.
Confirm Skio - Subscription events is checked.
Click Update settings.
The status should show Connected.

Once connected, events will appear in Omnisend under Store Settings > API > API Logs after they fire for the first time, and in the appropriate contacts' profiles.

What data does Skio send to Omnisend?

Contact fields

Field	Type	Description
Email Address	Standard	Customer email, the primary identifier
Phone	Standard	Customer phone number, if provided
`subscription_id`	Custom property	Unique ID of the customer's subscription
`user_type`	Custom property	Customer type (e.g., new subscriber, returning customer)

Supported events

Skio sends the same event metrics to Omnisend that are available across all Skio integrations. For the full list of available events with descriptions, see All Skio event metrics. Any event from that list can be enabled in your Custom Webhook Integration settings.

All events appear in Omnisend with the prefix Skio - followed by the event name. The events below are the most commonly used starting points for Omnisend automations.

Event	When it fires	Common use case
`Skio - subscriptionCreated`	Customer starts a new subscription	Welcome flows, onboarding, subscription tips
`Skio - subscriptionCancelled`	Customer cancels their subscription	Win-back campaigns, feedback requests
`Skio - subscriptionReactivated`	Customer reactivates a cancelled subscription	Thank you messages, loyalty rewards
`Skio - subscriptionPaused`	Customer pauses their subscription	Re-engagement flows, pause surveys
`Skio - subscriptionUnpaused`	Customer resumes a paused subscription	Confirmation emails, upcoming shipment details
`Skio - subscriptionSkipped`	Customer skips an upcoming order	Alternative product suggestions, reschedule reminders
`Skio - subscriptionRenewed`	Subscription renews successfully	Renewal confirmations, upsell opportunities
`Skio - billingAttemptFailed`	Payment fails during billing	Dunning emails, payment update requests
`Skio - subscriptionWillRenew`	Subscription is about to renew	Pre-renewal reminders, upsell offers
`Skio - cardWillExpire`	Customer's payment card is expiring soon	Card update reminders

Event properties

Event properties vary by event type but typically include:

subscriptionId : Unique subscription ID
email : Customer email
status : Subscription status (active, cancelled, paused, etc.)
domain : Store domain where the subscription was created
Additional properties depending on the event (e.g., billing date, cycles completed)

You can use event properties for personalization inside Omnisend automation workflows using the following syntax:

[[ event.subscriptionId ]]   [[ event.status ]]   [[ event.domain ]]

Event properties are available for personalization within automations only. They can't be used to build static audience segments. To segment contacts, use the custom contact properties subscription_id and user_type.

FAQ

When do events appear in Omnisend?

Events are sent in real time via webhooks. They appear in Store Settings > API > API Logs after the first event fires, and in the appropriate contacts' profiles.

Will all events appear in Omnisend?

No. Only events that include a valid email address are processed by Omnisend. Events without one are automatically skipped, this is expected behavior.

Can I use event properties for segmentation?

Event properties are available for personalization within automations only. To segment contacts, use custom contact properties like subscription_id or user_type.

Does Skio sync historical subscription data?

No. Skio only syncs events that occur after the integration is enabled. Historical subscriptions won't appear in Omnisend unless you manually import them.

Why isn't an event appearing as a trigger in Omnisend?

Omnisend only registers a custom event after receiving at least one payload. If you added an event in Skio but didn't click Send test, return to the Custom Webhook Integration page in your Skio Dashboard and send a test for that event. It will then appear as an available trigger in Omnisend's automation builder.