Skip to main content
OneSignal has partnered with Vendo to bring your Shopify store’s customer and order data into OneSignal with no code. Install the Vendo app from the Shopify App Store, connect your OneSignal app, and Vendo deploys the OneSignal web SDK on your storefront and keeps your customer profiles in sync. Vendo syncs Shopify customers, orders, marketing consent, Shopify segments, and acquisition attribution (UTMs and ad click IDs) to OneSignal as user tags and custom events, and resolves identity across push subscription, newsletter signup, login, and checkout so each shopper is one user in OneSignal. That gives you Shopify data for segmentation and personalization across every OneSignal channel: web push, email, SMS, and Journeys. Common uses include abandoned cart recovery, order status updates, VIP segments based on lifetime spend, win-back campaigns for lapsed customers, and audiences built on how a customer first found your store. See Use cases below.
Vendo’s documentation is the source of truth for what syncs and how:

What you can do

With Vendo connected, each identified shopper in OneSignal carries:
  • Customer tags: profile, lifetime spend, order count, marketing consent, Shopify customer tags, Shopify segment membership, and first- and last-touch UTMs plus ad platform click IDs.
  • Client-side events: 16 storefront and checkout events, such as product_viewed, product_added_to_cart, and checkout_started.
  • Server-side events: 6 order events, such as order_fulfilled, order_delivered, and cart_abandoned.
  • One user per shopper: push subscription, newsletter signup, login, and checkout resolve to the same OneSignal user.
Use this data to build segments, trigger Journeys, and personalize web push, email, and SMS messages.

Use cases

Abandoned cart recovery

Create a Journey triggered by the cart_abandoned event. Wait 1 hour after abandonment, then send a push notification with the recovery link using the checkout_url property.

Order status updates

Create Journeys for order_fulfilled and order_delivered to send immediate push notifications with tracking information when orders ship and arrive.

VIP customer engagement

Create a segment where total_spent is greater than a threshold, then send exclusive offers personalized with the first_name tag.

Re-engagement campaigns

Target inactive customers by creating a segment where last_order_date is more than 90 days ago and send win-back campaigns.

Acquisition-based audiences

Create a segment on the first-touch attribution tags, such as initial_utm_source or initial_utm_campaign, to target customers by how they first found your store. Use the click ID tags (gclid, fbclid, ttclid, msclkid) to find customers who arrived from a specific ad platform.

Prerequisites

Before you begin, make sure you have:
  • A Shopify store with the Vendo app installed
  • A OneSignal account and app (Web platform)
  • Your OneSignal App ID (required)
  • Your OneSignal REST API Key (required for server-side events like order syncing and user tagging)
  • Vendo app embed enabled in your Shopify theme settings

OneSignal setup

1

Create a OneSignal app

Log in to onesignal.com and create or select an app. Choose Web as the platform and select Custom Code as the integration type.
You must select Custom Code. The Typical Site option does not expose the service worker path settings, so the SDK will try to load /OneSignalSDKWorker.js from your store root — Shopify blocks this and push subscriptions will silently fail. If you already created the app under Typical Site, switch to Custom Code in Settings > Platforms > Web, or delete and recreate the app.
2

Configure web push settings

In your OneSignal app, navigate to Settings > Push & in-app setup > Web Settings or follow the Web push setup guide.Site setup
  • Site Name: Your store name, used as the default notification title.
  • Site URL: Your Shopify store’s publicly accessible URL (e.g., https://yourstore.com).
    • Must be the exact origin of your site.
    • Do not use https://your-site.myshopify.com/ if customers access your site through a custom domain like https://your-site.com/.
  • Default Icon URL: Upload a square 256×256 PNG, JPG, or non-animated GIF that appears in OneSignal soft prompts and in notifications on Chrome, Firefox, and Edge. If not set, a bell icon is used as the default. Safari and the browser’s native permission prompt do not show this icon. See Notification icons.
3

Configure the service worker path

Shopify does not allow serving files from the site root, so you must tell OneSignal where Vendo serves the service worker file.In OneSignal, go to Settings > Push & in-app setup > Web Settings, scroll to Advanced Push Settings, and toggle on Customize service worker paths and filenames, then configure:
OneSignal Advanced Push Settings showing service worker paths configured for Vendo

Service worker configuration for Shopify stores using Vendo.

Vendo automatically serves the required OneSignalSDKWorker.js file at https://yourstore.myshopify.com/apps/vendo/OneSignalSDKWorker.js — no manual file uploads needed.
The Vendo app’s OneSignal > Push Settings page displays these exact values with click-to-copy, so you don’t need to retype them.The Updater Filename and Main Service Worker Filename are the same file. OneSignal v16+ uses a single service worker for both purposes.
4

Copy your credentials

In OneSignal, go to Settings > Keys & IDs and copy your App ID and REST API Key. You will enter these in Vendo.

Vendo setup

1

Install the Vendo app

Install the Vendo app from the Shopify App Store. For Vendo’s own walkthrough, see the Shopify to OneSignal setup guide.
2

Add the OneSignal integration

In Vendo, navigate to Destinations > OneSignal.
Vendo Integrations page showing the OneSignal integration option

Add the OneSignal integration in Vendo.

3

Enter your OneSignal credentials

Enter your OneSignal App ID and REST API Key from the previous section, then click Save.
4

Enable the Vendo theme block

The Vendo theme block loads the OneSignal SDK on your storefront. Without it, the push prompt will not appear and client-side tracking will not work.
  1. In your Shopify admin, go to Online Store > Themes > Customize.
  2. Click App embeds (puzzle piece icon in the left sidebar).
  3. Toggle Vendo on.
  4. Click Save.
The theme block handles SDK initialization, service worker registration, push prompt display, user identification (push subscription, login, newsletter signup), and tag syncing for identified users.
5

Select events to sync

In the Vendo app under OneSignal > Events, enable the client-side and server-side events you want to send to OneSignal. See Tracking below for the full event list.
6

Configure push prompts

Whether each prompt appears on your storefront — and when — is controlled from the Vendo app, not the OneSignal dashboard. In the Vendo app, open OneSignal > Push Settings. You will see four sections, each with its own toggle:For Push Slide and Native prompts, you also set triggers — how many page views and how many seconds to wait before the prompt fires. Sensible defaults are pre-filled.All four prompts are off by default — enable only the ones you want. Save once at the bottom of the page; changes take effect on the next storefront load without a theme redeploy.
Prompt button copy, action message text, icons, and advanced options like A/B tests and localization are configured in the OneSignal dashboard. From Vendo’s Push Settings, click Open OneSignal Dashboard to jump directly to the Permission Prompt Setup page. If a prompt is configured in OneSignal’s dashboard but its Vendo toggle is off, it will not render — Vendo’s toggle is the source of truth for visibility.
7

Historical data sync (optional)

Vendo can backfill existing customers and recent order history to OneSignal. This happens automatically in the background after you save your credentials.
Vendo historical data settings showing sync options for Shopify data

Historical data sync options in Vendo.

Tracking

User identification

Vendo uses an identified-only approach — anonymous visitors are not tracked in OneSignal. Users must be identified through one of four methods before events are sent. This prevents duplicate users and ensures clean, actionable data.
If you have a mobile app or third-party connections, select the identifier (Shopify Customer ID vs. Email) that matches your other tools so user profiles stay consistent across platforms. Configure this in the Vendo app under Settings > Customer Identifier.

Identity merging

If a push subscriber (identified by OneSignal ID) later logs in or completes a purchase, Vendo calls OneSignal.login() with their Shopify Customer ID or email. OneSignal links the push subscription to the identified user — no duplicate users are created. All past push subscriptions are preserved, and server-side events (orders, fulfillments) reach the correct user profile.

Customer tags

Vendo syncs customer properties as tags in OneSignal for segmentation. All values are stored as strings (OneSignal’s native format).

Identity & profile

Commerce stats

Attribution tags

Vendo captures UTM parameters and click IDs at checkout and syncs them as tags. Last-touch values are overwritten on each checkout; first-touch values (initial_utm_*) are written only once.

Segment membership

Vendo can sync Shopify segment membership as tags in the format shopify_segment_{segment_id} with a value of "true". See Vendo’s Events & Properties reference for details on running the sync.

Client-side events

Vendo tracks client-side custom events on your storefront via the Shopify Web Pixel and sends them to OneSignal. These events are only sent after a user is identified.
Vendo client-side events settings showing available custom events

Client-side event configuration in Vendo.

Server-side events

Shopify commerce events are exported and forwarded to OneSignal through the Vendo pipeline. These always use the Shopify Customer ID as the external_id.
Vendo server-side events settings showing available Shopify webhook events

Server-side event configuration in Vendo.

Email

Vendo syncs each identified customer’s email, verified_email, marketing_state, and email_marketing_consent as customer tags. Use these tags to build email audiences, for example a segment that filters on email_marketing_consent to include only customers who opted in to email marketing. Personalize subject lines and content with tags such as first_name and total_spent, and use the order events to trigger email steps in Journeys. OneSignal sends email to email subscriptions, not to the email tag. Confirm your customers have email subscriptions in OneSignal before you send. See Email setup.
An email address alone is not consent. Only send marketing email to customers who opted in, and honor email_marketing_consent when you build segments. See Email compliance.

SMS

Vendo syncs the customer’s phone number and overall marketing_state as customer tags. Use them with the commerce tags and order events to target SMS, for example shipping updates triggered by order_fulfilled or high-value cart recovery triggered by cart_abandoned. OneSignal sends SMS to SMS subscriptions, not to the phone tag. Confirm your customers have SMS subscriptions in OneSignal before you send. See SMS setup.
A phone number alone is not consent. Only send text messages to customers who gave consent for that purpose, and follow the rules in your sending country. See SMS opt-in and collection and SMS regulatory compliance.

Platform details

Compatible sources

OneSignal works with the following Vendo data sources:

Testing

1

Verify the service worker

Visit https://yourstore.myshopify.com/apps/vendo/OneSignalSDKWorker.js in your browser. You should see JavaScript code. If you get a 404, verify the Vendo app is installed and the theme block is enabled.You can also open browser DevTools (F12), go to Application > Service Workers, and confirm OneSignalSDKWorker.js is registered with a scope of /apps/vendo/.
2

Test the push prompt

Open your storefront in an incognito/private window. You should see the OneSignal notification permission prompt. Click Allow to subscribe.
3

Send a test notification

In the OneSignal dashboard, go to Messages > New Push. Send a test notification to your subscriber and verify it appears.
4

Verify user data in OneSignal

Go to Audience > Users & subscriptions and confirm your test user appears. Check that user tags (email, name, etc.) are syncing for identified users.
5

Trigger a test event

Browse a product or complete a test checkout on your store. Confirm the event appears in the user’s activity in the OneSignal dashboard.

Troubleshooting

Service worker returns 404

The service worker must be at /apps/vendo/OneSignalSDKWorker.js. If you see a 404 error at the root path (/OneSignalSDKWorker.js), the service worker path is not configured in OneSignal — follow the service worker configuration step. If the 404 is at the /apps/vendo/ path, verify the Vendo app is installed and the theme block is enabled.

”Typical Site” was selected during OneSignal setup

Vendo requires the Custom Code integration type. Typical Site does not expose the service worker path settings, so the SDK will try to load /OneSignalSDKWorker.js from your store root — Shopify blocks that and push subscriptions will silently fail. Fix: in the OneSignal dashboard, either switch the app’s integration type to Custom Code under Settings > Platforms > Web, or delete the app and recreate it using Custom Code from the start.

Push prompt not appearing

  • Check that the Vendo theme block is enabled in App embeds.
  • In the Vendo app under OneSignal > Push Settings, confirm at least one prompt toggle (Subscription Bell, Push Slide Prompt, or Native Browser Prompt) is turned on — all four are off by default.
  • Check the trigger delay — a Push Slide set to multiple page views won’t fire on the first page load.
  • Verify your browser allows notifications (click the lock icon in the address bar).
  • Try an incognito/private window in case the prompt was previously dismissed.

Tags not appearing in OneSignal

Tags only sync for identified users — anonymous visitors are not tracked. Ensure the user has been identified via push subscription, login, newsletter signup, or checkout. Initial tag syncs can take several hours.

Events not triggering

Verify events are enabled in the Vendo app under OneSignal > Events. Client-side events require the Shopify Web Pixel to be active and the user to be identified. Server-side events require the REST API Key to be configured.

Notifications show “Delivered” but don’t appear

The integration is working — the issue is with your browser or OS notification settings. Check your OS notification settings for your browser, ensure Do Not Disturb / Focus mode is off, and verify browser-level notification permissions.

FAQ

Can I change the customer identifier after setup?

Yes. Update the setting in the Vendo app under Settings > Customer Identifier. Changing the identifier may create separate user profiles if existing users were already identified with the previous method.

Does the Vendo integration support mobile apps?

The Vendo integration focuses on Shopify storefronts. If you also have a mobile app, ensure the identifier you select in Vendo matches the one you use in your mobile app so user profiles stay consistent.

What happens if a visitor is never identified?

Events from unidentified visitors are not sent to OneSignal. Once the visitor identifies themselves (by subscribing to push, logging in, signing up for a newsletter, or completing checkout), Vendo begins sending events. This identified-only approach prevents duplicate users and ensures clean data.

Why does Vendo use an identified-only approach?

Tracking anonymous visitors creates duplicate OneSignal users that can never be properly merged, leading to inflated user counts and fragmented data. The identified-only approach ensures every OneSignal user is real and actionable.

Keys & IDs

Find your OneSignal App ID and REST API key.

Custom events

Track user behavior and trigger automations based on Shopify events.

Web push setup

Set up web push notifications for your Shopify store.

Web permission prompts

Configure how and when to prompt visitors for web push permission.

Journeys

Automate cart recovery, order updates, and win-back flows from Shopify events.

Email setup

Set up email so you can reach customers with their synced Shopify data.

Tags

Learn how tags store customer properties like lifetime spend and order count.

Segments

Build audiences from Shopify tags such as total_spent and last_order_date.