Skio is a Shopify subscription app that enables recurring billing and subscription management. Connect it to Omnisend to trigger email and SMS workflows based on subscription lifecycle and billing events. You'll also sync subscription details to contact profiles for personalization.
Before You Begin
You need an active Skio app installed on your Shopify store.
The integration is available on all Omnisend plans.
Skio sends real-time events to Omnisend via webhooks – workflows trigger instantly when subscription actions occur.
Key Benefits
Send automated emails or SMS for subscription lifecycle and billing events.
Sync subscription data (subscription ID, status, billing date) to contact profiles.
Personalize messages using event properties like subscription ID, renewal date, or subscription status.
Engage customers with timely messages based on subscription behavior.
No manual data entry – events sync automatically via webhook.
Setup Process
Step 1. Connect Skio in Omnisend
In Omnisend, go to App Market → search for Skio → click Connect.
You'll be taken to the Skio app settings page.
Copy the Webhook URL shown under the Automations section.
Keep this URL handy – you'll paste it into Skio in the next step.
Step 2. Enable Custom Webhook Integration in Skio
Log in to your Skio Dashboard → go to Integrations.
Find Custom Webhook Integration → 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 Skio, click + Add events.
Select the subscription events you want to send to Omnisend (see full event list below).
After adding each event, click Send test.
Important: Omnisend only registers a custom event after receiving at least one payload. If you don't send a test, the event won't appear as an available trigger in Omnisend. Always send a test for each event you enable.
Step 4. Confirm 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.
Events will now appear in Omnisend → Store Settings → API → API logs after they fire for the first time, or in appropriate contacts' profiles.
What Data Is Passed
Contact Fields:
Field Name | Type | Description |
Email Address | Standard | Customer email (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 Custom Events
All events appear in Omnisend with the prefix Skio - followed by the event name.
Subscription Lifecycle:
Event Name | When It Fires | 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. |
Billing Events:
Event Name | When It Fires | Use Case |
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 | The customer's payment card is expiring soon. | Card update reminders. |
Event Properties Passed
Event properties vary by event type but typically include:
subscriptionId– Unique subscription IDemail– Customer emailstatus– Subscription status (active, cancelled, paused, etc.)domain– Store domain where subscription was created
Additional properties depending on the event (e.g., billing date, cycles completed).
Use in personalization:
[[ event.subscriptionId ]] [[ event.status ]] [[ event.domain ]]
Important: Event properties are available inside automation workflows only for personalization. They cannot be used to build static audience segments. Only subscription_id and user_type (when passed as custom contact properties) can be used for segmentation.
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, or 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 an email address are automatically skipped – this is expected behavior.
Can I use event properties for segmentation?
Event properties are available for personalization only within automations. To segment contacts, use custom contact properties like subscription_id or user_type.
What if Skio doesn't send historical data?
Skio only syncs events that occur after the integration is enabled. Historical subscriptions won't appear in Omnisend unless manually imported.
If you didn't find the answer to your question, reach out to our Support Team through the in-app chat or at [email protected] – our team is available 24/7.