What should your first push notification do?

Give one interested customer a clear reason to return. Web push can deliver information when someone is away from your website. Notifications display small pieces of information on their device; web.dev explains both parts.

Hypothetical example: a small stationery shop sells a popular notebook that is temporarily unavailable. Invite interested visitors to request a restock alert. Your first campaign can then answer a specific request instead of announcing everything the shop sells.

Write a campaign brief before opening the dashboard

• Recipient: someone who requested news about this notebook.
• Trigger: the item becomes available to order.
• Message: a short availability update.
• Destination: the relevant product page.
• Stop condition: the item becomes unavailable again.

This is a proposed workflow, not a claimed result or a ready-made integration. Ask your website specialist which parts your store can support. If you cannot reliably identify the relevant audience, start with a simpler topic people explicitly subscribe to.

For another planning example, use the florist marketing guide to think through the offer behind an alert. Keep the first promise narrow enough that you can fulfil it consistently.

Should push replace email or SMS?

Assign each channel a specific job before replacing anything. I would use push for a short, relevant update and reserve longer explanations for email. The emphasis on timely, relevant information follows web.dev's guidance, which also warns against messages people find unhelpful.

Treat this as a decision aid, not a performance ranking. Avoid promising that push will outperform your email programme. Write down the cost, workload and customer response you would need to justify adding another channel.

If SMS is part of the decision, work through the SMS marketing launch plan. If your proposed alert has no clear value yet, use the lead magnet guide to sharpen the reason someone should subscribe.

For the first pilot, give one person responsibility for the sending calendar. Ask them to check other planned messages before approving a push campaign. Set a clear rule for avoiding repeated reminders about the same offer.

How do you connect your website to OneSignal?

Choose the installation route that matches your website. OneSignal documents an official WordPress plugin, a Web SDK route for typical sites, and a Vendo integration for Shopify. Shopify requires the Custom Code integration setting, according to the current setup instructions.

A short brief for your website specialist

An SDK is a prepared software package added to your site. A service worker is background code that handles tasks such as receiving push messages. An active service worker is required for the Push API, the browser interface used for push subscriptions, as explained by MDN.

1. Confirm the website address and platform you will use.
2. Check that its HTTPS certificate is valid.
3. Select the matching OneSignal integration route.
4. Complete that route's installation instructions.
5. Prepare the permission request and a test audience.
6. Send a test and verify the destination page.

For WordPress, the official plugin route does not require a separate SDK installation or service worker upload. The typical-site route does include those tasks. Give your specialist the platform-specific checklist rather than combining instructions from different routes.

Define completion in customer terms: the request makes sense, the notification arrives, and clicking it opens the promised page. Ask for a short handover explaining who can send campaigns and how the team should pause them.

When should you ask permission, and which browsers work?

Ask after the visitor has a reason to care. OneSignal recommends explaining the benefit in a preliminary prompt, then opening the browser's permission request after acceptance. It lists Chrome, Firefox, Safari and Edge support, while private browsing cannot create subscriptions; see its permission and browser notes.

Hypothetical permission copy for the stationery shop: “Want to know when this notebook is back?” Offer a clear acceptance button and a “Not now” option. Keep subsequent messages within the promise you made.

On iPhone and iPad, OneSignal describes support from iOS 16.4, with a web app manifest and installation on the Home Screen required. A manifest is a file describing the installable website. Follow the iOS setup requirements and test that journey separately.

Keep a small device test sheet

Record the device, browser, permission state and result. Include accepting permission, declining it and withdrawing it later. Have the tester describe what they saw rather than marking the whole process simply “working.”

OneSignal creates separate subscriptions for different browser and device combinations. Therefore, label your audience count as subscriptions rather than unique people, following its subscription explanation.

How should an abandoned cart push notification work?

Define the purchase checks before writing the reminder. The following is a proposed ecommerce workflow, not a claim that installing OneSignal automatically connects your cart data.

1. Associate the permitted subscription with the relevant cart.
2. Record when the customer adds an item and completes a purchase.
3. Choose a waiting period suitable for your buying process.
4. Check again for a completed purchase immediately before sending.
5. Cancel the reminder if permission or product availability has changed.
6. Stop remaining reminders after the purchase.

Hypothetical message: “Still considering your selection? Return to your basket when you're ready.” Link directly to the relevant shopping step. Avoid saying items are reserved unless your store actually reserves them.

Ask your specialist to test the link with another account and device. Stop the test if it exposes someone else's details. Keep addresses, payment information and other private order details out of notification copy.

Choose expiry and repetition rules

OneSignal supports frequency limits and time to live, meaning how long a push service retains a message while the device is offline. Its delivery settings describe these controls. Match the expiry to the offer and choose a conservative sending limit for your pilot.

For a local service business, consider a requested availability update instead of a cart campaign. Use the appointment booking guide to plan the destination. Then review the appointment reminder guide before adding another message sequence.

What should you measure during the first week?

Measure whether the system works before judging the marketing. Use this suggested schedule to keep the pilot manageable.

• Prepare: name the owner, audience and desired customer action.
• Install: finish the website integration and permission request.
• Test: check delivery, appearance and destination on relevant devices.
• Launch: send one useful message to a small eligible audience.
• Review: record clicks, completed actions and subscription losses.

OneSignal provides delivery, open-rate and click-through reporting, as listed in its analytics overview within the setup guide. Before quoting push notification open rates, check exactly what the dashboard counts. Keep that definition beside the number.

For your own click calculation, write both the numerator and denominator. If you divide clicking subscriptions by confirmed delivered subscriptions, say so. If confirmed delivery is unavailable, do not silently substitute sent messages and keep the same label.

Also record what happened after the click. Where possible, compare with a similar group that received no push message. Use that comparison to judge whether the campaign merits another test; do not label every subsequent purchase an additional sale caused by push.