Subscribfy is a Shopify app for memberships, product subscriptions, loyalty programs, and store credits. It lets stores run paid memberships, reward customers with points and loyalty tiers, and manage store credit balances.
With the Omnisend integration, Subscribfy sends membership, store credit, points, and loyalty tier events to Omnisend as custom events. Each event identifies the contact by email and updates their custom properties, so you can segment members and trigger automated emails and SMS messages based on their membership and loyalty activity.
Benefits
Membership lifecycle automations: Send welcome, pause, win-back, and cancellation messages when a membership is created, paused, reactivated, or canceled.
Loyalty engagement: Celebrate new loyalty tiers, remind customers when they lose a tier, and keep them informed about their points balance.
Store credit reminders: Notify customers when their store credit balance changes.
Up-to-date contact profiles: Keep each contact's points, store credits, loyalty tier, and membership status in Omnisend for segmentation.
How It Works
Data flows one way, from Subscribfy to Omnisend. Each integration feature in Omnisend has its own unique webhook URL. You paste that URL into the matching event in Subscribfy's webhook settings. When the event happens in Subscribfy, Subscribfy sends a webhook to Omnisend, and Omnisend:
Creates or updates the contact by email, including their first and last name.
Updates the contact's Subscribfy custom properties.
Records a custom event on the contact, such as
Subscribfy - Membership Created.
Note: Events are only sent for Subscribfy activity that includes a customer email address. Each Subscribfy event needs its own webhook URL – paste each URL only into its matching event.
Setup Process
Step 1. In Omnisend, go to Apps → search for Subscribfy → click Connect now.
Step 2. Turn on the integration features you want to use:
Subscribfy - Membership Created → Omnisend – sends a
Subscribfy - Membership Createdevent when a new membership contract is created.Subscribfy - Membership Updated → Omnisend – sends a
Subscribfy - Membership Updatedevent when a membership is updated.Subscribfy - Membership Paused → Omnisend – sends a
Subscribfy - Membership Pausedevent when a membership is paused.Subscribfy - Membership Reactivated → Omnisend – sends a
Subscribfy - Membership Reactivatedevent when a membership is activated again from a paused or cancelled status.Subscribfy - Membership Cancelled → Omnisend – sends a
Subscribfy - Membership Cancelledevent when a membership is cancelled.Subscribfy - Store Credits Changed → Omnisend – sends a
Subscribfy - Store Credits Changedevent when a customer's store credits are updated.Subscribfy - Points Changed → Omnisend – sends a
Subscribfy - Points Changedevent when a customer's points balance changes (earn, spend, or adjustment).Subscribfy - Tier Changed → Omnisend – sends a
Subscribfy - Tier Changedevent when a customer reaches a new loyalty tier.Subscribfy - Tier Lost → Omnisend – sends a
Subscribfy - Tier Lostevent when a customer drops out of a loyalty tier.
Step 3. Copy the unique webhook URL for each feature you turned on.
Step 4. In your Shopify admin, go to Apps → Subscribfy → Settings → Webhooks. Check that Webhook Status shows Active.
Step 5. Under Webhook Events, open the Membership or Loyalty tab, click Edit next to the event, paste the matching Omnisend webhook URL into the URLs (comma-separated) field, and click Activate. Repeat for each feature using the table below.
Omnisend feature | Subscribfy tab | Subscribfy event |
Subscribfy - Membership Created → Omnisend | Membership | Created |
Subscribfy - Membership Updated → Omnisend | Membership | Updated |
Subscribfy - Membership Paused → Omnisend | Membership | Paused |
Subscribfy - Membership Reactivated → Omnisend | Membership | Reactivated |
Subscribfy - Membership Cancelled → Omnisend | Membership | Cancelled |
Subscribfy - Store Credits Changed → Omnisend | Membership | Store Credits Changed |
Subscribfy - Points Changed → Omnisend | Loyalty | Points Changed |
Subscribfy - Tier Changed → Omnisend | Loyalty | Tier Changed |
Subscribfy - Tier Lost → Omnisend | Loyalty | Tier Lost |
Step 6. To check the connection, open the event again in Subscribfy and click Test Call. Subscribfy sends a sample event, which appears on a test contact in Omnisend.
What Data Is Passed
Contact Fields
Omnisend field | Description |
The customer's email address. Used to identify the contact. | |
First name | The first word of the customer's name in Subscribfy. |
Last name | The rest of the customer's name in Subscribfy. |
Custom Properties
These contact custom properties are updated with each event when the value is available:
Property key | Description | Example |
| The customer's current loyalty points balance. |
|
| The customer's current store credit balance. |
|
| The name of the customer's current loyalty tier. |
|
| The membership status. Updated by membership events only. |
|
| The membership plan title. Updated by membership events only. |
|
| The next membership billing date. Updated by membership events only. |
|
Custom Events
Feature | Custom Event Name | When it fires |
Subscribfy - Membership Created → Omnisend |
| A new membership contract is created. |
Subscribfy - Membership Updated → Omnisend |
| A membership is updated. |
Subscribfy - Membership Paused → Omnisend |
| A membership is paused. |
Subscribfy - Membership Reactivated → Omnisend |
| A membership is activated again from a paused or cancelled status. |
Subscribfy - Membership Cancelled → Omnisend |
| A membership is cancelled. |
Subscribfy - Store Credits Changed → Omnisend |
| A customer's store credits are updated. |
Subscribfy - Points Changed → Omnisend |
| A customer's points balance changes (earn, spend, or adjustment). |
Subscribfy - Tier Changed → Omnisend |
| A customer reaches a new loyalty tier. |
Subscribfy - Tier Lost → Omnisend |
| A customer drops out of a loyalty tier. |
Membership Event Fields
Sent with Subscribfy - Membership Created, Subscribfy - Membership Updated, Subscribfy - Membership Paused, Subscribfy - Membership Reactivated, Subscribfy - Membership Cancelled:
Event Field | Description | Example |
| The Subscribfy webhook topic. |
|
| The Shopify customer ID. |
|
| The customer's loyalty points balance. |
|
| The customer's store credit balance. |
|
| The membership type. |
|
| The membership plan title. |
|
| The membership status. |
|
| The membership price. |
|
| The membership currency code. |
|
| The next billing date. |
|
| The billing interval unit. |
|
| The number of interval units between billings. |
|
| The cancellation reason. Sent with Membership Cancelled when available. |
|
| The full membership object as sent by Subscribfy. | – |
Store Credits Changed Event Fields
Event Field | Description | Example |
| The Shopify customer ID. |
|
| The customer's loyalty points balance. |
|
| The customer's store credit balance. |
|
| The type of store credit change. |
|
| The amount of the store credit change. |
|
| The note attached to the change. |
|
Points Changed Event Fields
Property | Description | Example |
| The Shopify customer ID. |
|
| The customer's loyalty points balance. |
|
| The customer's store credit balance. |
|
| The type of points change. |
|
| The number of points changed. |
|
| The note attached to the change. |
|
Tier Changed and Tier Lost Event Fields
Property | Description | Example |
| The Shopify customer ID. |
|
| The customer's loyalty points balance. |
|
| The customer's store credit balance. |
|
| The ID of the customer's new tier. Sent with Tier Changed. |
|
| The name of the customer's new tier. Sent with Tier Changed. |
|
| The name of the tier the customer lost. Sent with Tier Lost. |
|
| The ID of the tier the customer lost. Sent with Tier Lost. |
|
Create Automation Workflows with Subscribfy Events
You can use the custom events sent to create Automation Workflows in Omnisend. Go to Automation → Create workflow → Create from scratch. In the trigger area, select your custom event.
Note: The custom event must be synced to Omnisend at least once before you can select it as an automation trigger.
Here are example workflows you can build:
Member welcome: When
Subscribfy - Membership Createdoccurs, send an email that welcomes the contact and explains their membership benefits.Pause check-in: When
Subscribfy - Membership Pausedoccurs, send an email that reminds the contact what they keep when they resume.Win-back: When
Subscribfy - Membership Cancelledoccurs, wait a few days, then send an email that invites the contact to rejoin.Welcome back: When
Subscribfy - Membership Reactivatedoccurs, send an email that thanks the contact for coming back.Tier celebration: When
Subscribfy - Tier Changedoccurs, send an email that congratulates the contact on reaching their new tier.Tier recovery: When
Subscribfy - Tier Lostoccurs, send an email that tells the contact how to earn their tier back.Points update: When
Subscribfy - Points Changedoccurs, send an email or SMS that shows the contact their new points balance.Store credit reminder: When
Subscribfy - Store Credits Changedoccurs, send an email that reminds the contact to use their store credit.
FAQ
Can I use one webhook URL for all events?
No. Each feature's URL only accepts its own Subscribfy event. Paste each URL into its matching event, as shown in the setup table.
How are contacts matched?
By email address. If no contact with that email exists in Omnisend, a new contact is created. Subscribfy events without a customer email are not sent to Omnisend.
Does the integration send data from Omnisend to Subscribfy?
No. Data flows one way, from Subscribfy to Omnisend.
Why aren't tier created and tier updated events supported?
These Subscribfy events describe changes to the tier itself and don't include a customer, so they can't be added to a contact in Omnisend. Use Tier Changed and Tier Lost to follow customers moving between tiers.
Why can't I select a Subscribfy event as an automation trigger?
The event must be synced to Omnisend at least once. Trigger the event in Subscribfy or click Test Call on the event in Subscribfy's webhook settings, then check the trigger list again.
What should I check if a Subscribfy event doesn't appear in Omnisend?
Check that:
The matching feature is turned on in Omnisend.
The webhook URL is pasted into the correct event in Subscribfy, and you clicked Activate.
Webhook Status in Subscribfy → Settings → Webhooks is Active.
The Subscribfy customer has an email address.
If the issue persists, uninstall and reinstall the app.
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.

