- Shopify to OneSignal setup guide
- OneSignal destination overview
- Events and properties: the full tag and event list
- How identification works
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, andcheckout_started. - Server-side events: 6 order events, such as
order_fulfilled,order_delivered, andcart_abandoned. - One user per shopper: push subscription, newsletter signup, login, and checkout resolve to the same OneSignal user.
Use cases
Abandoned cart recovery
Create a Journey triggered by thecart_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 fororder_fulfilled and order_delivered to send immediate push notifications with tracking information when orders ship and arrive.
VIP customer engagement
Create a segment wheretotal_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 wherelast_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 asinitial_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
Create a OneSignal app
Configure web push settings
- 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 likehttps://your-site.com/.
- Default Icon URL: Upload a square
256×256PNG, 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.
Configure the service worker path

Service worker configuration for Shopify stores using Vendo.
OneSignalSDKWorker.js file at https://yourstore.myshopify.com/apps/vendo/OneSignalSDKWorker.js — no manual file uploads needed.Copy your credentials
Vendo setup
Install the Vendo app
Add the OneSignal integration

Add the OneSignal integration in Vendo.
Enter your OneSignal credentials
Enable the Vendo theme block
- In your Shopify admin, go to Online Store > Themes > Customize.
- Click App embeds (puzzle piece icon in the left sidebar).
- Toggle Vendo on.
- Click Save.
Select events to sync
Configure push prompts
Historical data sync (optional)

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.Identity merging
If a push subscriber (identified by OneSignal ID) later logs in or completes a purchase, Vendo callsOneSignal.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
Marketing consent
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 formatshopify_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.
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 theexternal_id.

Server-side event configuration in Vendo.
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.
SMS
Vendo syncs the customer’sphone 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.
Platform details
Compatible sources
OneSignal works with the following Vendo data sources:Testing
Verify the service worker
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/.Test the push prompt
Send a test notification
Verify user data in OneSignal
Trigger a test event
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.Related pages
Keys & IDs
Custom events
Web push setup
Web permission prompts
Journeys
Email setup
Tags
Segments
total_spent and last_order_date.