Shopify

The ReachBell for Shopify app connects your store to your ReachBell project over OAuth, drops the opt-in prompt onto your storefront, and links each shopper to their Shopify customer record. From there you build the actual messages — abandoned-cart, back-in-stock, order updates — as automations in your dashboard, across push, email, SMS and WhatsApp.

It's a public app, so there are no API keys to copy and no theme code to edit by hand. Approving the install is what authorizes ReachBell to read the customer and order data your automations key off.

How it works

• You install the app from the Shopify App Store and approve its OAuth scopes. Shopify hands ReachBell a per-store access token, which we store encrypted — it's never shown back to you after install.
• The app injects the ReachBell web-push opt-in prompt onto your live storefront for you, so you don't touch theme.liquid.
• When a logged-in shopper grants permission, the subscription is linked to their Shopify customer (email / customer id). That link is what lets an automation reach the right person — an order_paid automation can only find a subscriber it can match.
• The app does not send messages on its own. You design those as automations keyed off store events; ReachBell reads orders and customers through Shopify's APIs to trigger and target them.

Requirements

• A Shopify store on any plan (Basic through Plus).
• Permission to install apps on the store (store owner or staff with the Apps permission).
• A ReachBell project. You can create one during the app's onboarding if you don't have one yet.

1. Install the app

1. Open the ReachBell listing on the Shopify App Store.
2. Click Add app, then Install.
3. Shopify shows the permission screen. ReachBell requests read access to your customers and orders, plus permission to add its storefront script. Review and click Install to approve.

The scopes ReachBell requests are:

 Copyread_customers     # match subscribers to Shopify customer records
read_orders        # trigger order-update and post-purchase automations
write_script_tags  # inject the opt-in prompt onto your storefront

ReachBell reads customers and orders through the standard Shopify APIs — it does not lock your store in. You can keep an existing email tool running alongside it.

2. Connect the store (OAuth)

Approving the permission screen is the OAuth handshake — there's nothing else to paste.

1. After you click Install, Shopify redirects you back to ReachBell with a one-time authorization code.
2. ReachBell exchanges that code for a permanent access token and stores it encrypted against your project.
3. You land back in the ReachBell dashboard on the project's Integrations page, where Shopify now shows as Installed with your *.myshopify.com domain.

If you start the connection from the ReachBell side instead (Integrations → Shopify → Connect), enter your store domain in the form your-store.myshopify.com and you'll be sent to the same Shopify approval screen.

The handshake is signed end-to-end: ReachBell embeds an encrypted, time-limited token in the OAuth state so the install can only ever bind to the project you started from. If the connection stalls, just start it again — the token expires after a few minutes.

3. Turn on the opt-in prompt

Once the store is connected, the app serves ReachBell's web-push opt-in prompt on your storefront automatically — no theme edits.

• All prompt copy, timing and styling are edited from the prompt designer in your ReachBell dashboard, not in Shopify. Changes apply to your live store without redeploying the theme.
• By default the soft prompt is shown on the shopper's first interaction (click, tap, or keypress) so it isn't a cold permission pop-up. You can switch to a manual trigger from the prompt settings if you'd rather gate it behind your own CTA.

To confirm it's live, open your storefront in a fresh browser window, accept the prompt and the native browser dialog, then check Subscribers in the ReachBell dashboard — your device should appear, and for a logged-in customer it should carry their Shopify identity.

4. Build the key automations

Automations are where the value is. They live in the ReachBell automation builder and run across push, email, SMS and WhatsApp — you pick the channel per step. The patterns below are the common starting points for a store.

Abandoned cart

Recover checkouts that didn't complete.

1. Trigger: shopper begins checkout / adds to cart without purchasing.
2. Wait: 1 hour.
3. Condition: no completed order since.
4. Action: send a push — "Still thinking it over? Your cart's waiting 🛒". Add a follow-up email or WhatsApp step a few hours later for shoppers who haven't converted.

Back-in-stock

Let shoppers ask to be told when a sold-out product returns.

1. Shoppers join a product's waitlist from your storefront.
2. Trigger: that product's inventory goes from zero to in-stock.
3. Action: notify everyone on the waitlist with a push (and email/SMS as a fallback) linking straight to the product.

Order updates

Keep buyers informed after they pay.

1. Trigger: order paid (or fulfilled / shipped).
2. Action: send a confirmation or shipping-update push, optionally with an email receipt.

Because ReachBell matches each order back to the campaign or automation that drove it, you can see revenue per channel in the dashboard's attribution view once orders start flowing.

Data, privacy & GDPR

ReachBell is a public Shopify app and handles Shopify's three mandatory compliance webhooks, each verified with an HMAC-SHA256 signature before it's processed:

Uninstalling the app from Shopify revokes the access token and stops all reads. Your ReachBell subscriber list and project data are not deleted by an uninstall — they live on the ReachBell side. Reconnecting the same store restores the link.

Troubleshooting

The opt-in prompt never appears. Confirm the store still shows as Installed on the ReachBell Integrations page. If a theme update or a "remove app embeds" action stripped the storefront script, reconnect from Integrations → Shopify. Also check the prompt isn't set to manual-trigger in the prompt designer.

Automations fire but reach no one. The subscriber has to be matchable to a Shopify customer. Make sure shoppers subscribe while logged in (guest subscribers have no customer link), and that the automation targets the same identity the subscription was captured under.

The connection won't complete. The OAuth state is time-limited — if you left the tab open too long, start the connect flow again. Double-check the store domain is the canonical your-store.myshopify.com, not a custom domain.

What's next?

• Read the Automation guide for the full builder — triggers, waits, conditions and branching.
• See Quick start for an overview of the prompt designer and compose flow.
• Want lower-level control of the on-store prompt or identity calls? The browser SDK exposes the same primitives the app uses under the hood.