Shopify to OneSignal
Connect Shopify storefront and customer activity to OneSignal for web push, email identity, profile tags, and lifecycle events.
Last reviewed September 15, 2026
Vendo connects Shopify to OneSignal in two complementary paths. The storefront sets up browser or email identity. Server-side Shopify events keep user tags and lifecycle activity current.
Before you start
- Connect Shopify and enable the Vendo theme app embed or supported storefront integration.
- Create a OneSignal app for the correct site and environment.
- Prepare the OneSignal App ID and API key.
- Decide which Shopify customer identifier should become the OneSignal external ID.
How identity flows
| Signal | Result in OneSignal |
|---|---|
| Browser grants push permission | A web push subscription is created |
| Newsletter form submits an email | An email subscription is associated with the user |
| Customer logs in or checks out | Shopify customer identity can merge with the existing subscription |
| Server-side commerce event arrives | Tags and lifecycle event data update without relying on the browser |
See How OneSignal identification works for the canonical identity behavior.
Configure the destination
- Complete OneSignal web push setup.
- In the Vendo Shopify app, open Destinations and click Add destination.
- Select OneSignal.
- On the Tracking step, turn on the events and profile updates you need.
- On the Credentials step, enter the App ID and REST API Key.
- If you want Safari push notifications on macOS, enter the Safari Web ID (Optional).
- If you turned on server-side events, select a Historical Data option.
- Click Complete Setup.
- Run a test with a non-production subscriber.
App proxy path
The Vendo app embed has an App proxy path setting. Vendo uses this path to load the OneSignal service worker from your store.
- If you leave it blank, Vendo detects the path automatically.
- If your store uses a customized app proxy URL, copy the
/apps/...path from Settings > Apps > Vendo > App Proxy URL in Shopify admin.
Vendo uses the path only after it confirms that the service worker loads from it. If it cannot confirm the path, OneSignal uses the settings in your OneSignal dashboard.
Profile tags from the storefront
The Vendo pixel sets OneSignal user tags from the storefront. Tag names do not include a leading $. Vendo shortens each tag value to 255 characters.
| When | Tags that Vendo sets |
|---|---|
| Customer completes checkout | Customer ID, name, email, phone, UTM values, click IDs, communication_profile, gbraid, fbc, fbp and profile_attribution_snapshot |
| Customer logs in | shopify_customer_id, email, first_name and last_name |
| Visitor signs up for the newsletter | email, when Vendo already knows the customer |
Verify
- Visit the storefront in a clean browser profile and grant notification permission.
- Submit a test email or log in as a test customer.
- Complete a test storefront event or order.
- In OneSignal, find the user and confirm the push/email subscription, external ID, and expected tags.
- On the OneSignal Overview tab, check Latest run for the related destination job.
Troubleshooting
| Symptom | Check |
|---|---|
| Push prompt never appears | HTTPS, browser permission, service worker, and OneSignal site configuration |
| Email exists as a separate user | External-ID mapping and the order of identify/login calls |
| Tags do not update | API key permissions, selected fields, and destination job errors |
| Custom form is ignored | Form selector and the custom newsletter workflow |