Shopify

Documentation Index

Fetch the complete documentation index at: https://documentation.onesignal.com/llms.txt

Use this file to discover all available pages before exploring further.

OneSignal has partnered with Vendo to create a seamless Shopify integration. Vendo deploys the OneSignal SDK on your Shopify storefront with one click — no manual theme code editing required. It syncs customer tags, client-side browsing events, and server-side commerce events to OneSignal so you can build segments and trigger push campaigns from real behavior and purchase history. For Vendo’s documentation, see Vendo OneSignal Destination.

​

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

​

Vendo setup

​

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 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

​

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 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.

​

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.

​

Platform details

​

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.

​

Compatible sources

OneSignal works with the following Vendo data sources:

---

​

Testing

---

​

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 and web push. 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