Works with your stack
Cookie consent for OneSignal push notifications on WordPress
the prompt waits too
The OneSignal plugin adds OneSignal’s web SDK to every page, so visitors can subscribe to push notifications. It has no consent option of its own: without a banner that holds it, the SDK loads, calls OneSignal and stores data in the browser before any choice. Cookie Rocks Pro holds it until the visitor accepts, then starts it on the same page.
By OneSignal · onesignal.com · WordPress.org
Also in: Newsletter plugins
Is this your product? Tell us if anything here is out of date. Write to us
OneSignal
WordPress plugin
- Tested version
- 3.9.4
- How
- Tested on a live site
- Last test
- 11 November 2026
- Latest version
- 3.9.4 tested
- Active installs
- 60,000+
What the OneSignal plugin puts on your pages
- The OneSignal SDK
- A script from cdn.onesignal.com in the head of every page, with a short start-up script that holds your app ID: OneSignal.
- A call for your app settings
- On each visit the SDK asks api.onesignal.com for your prompt and app settings. OneSignal’s server sets a __cf_bm cookie on onesignal.com.
- Storage in the browser
- A database named ONE_SIGNAL_SDK_DB, and local storage keys such as os_pageViews, that keep the subscription and count page views to time the prompt.
- A background worker for subscribers
- Once a visitor subscribes, a worker script served by your site receives the notifications, even when the page is closed.
What matters for consent with OneSignal
It starts before any choice
The plugin has no setting to wait for consent. On its own, OneSignal is contacted on the first page of every visit, even by visitors who never subscribe.
Held until consent
Cookie Rocks Pro holds the SDK and its start-up script. Before the choice and after Reject all, nothing reaches OneSignal and nothing is stored.
No reload after Accept
After Accept all, OneSignal starts on the same page, so the subscription prompt can appear as you set it in OneSignal.
A yes for marketing
OneSignal registers subscribers and counts sessions and clicks for the messages you send. Under the strictest rules, that needs a yes for marketing, not only for preferences.
What our tests found on OneSignal
Before the choice · About Cookie RocksOneSignal waits for consent
Cookie Rocks Pro holds the OneSignal SDK and its start-up script until consent: before the choice and after Reject all, nothing reaches OneSignal and no OneSignal storage is created. After Accept all, OneSignal starts on the same page, without a reload. The browser’s notification prompt could not be tested without a real OneSignal app.
Seen in our tests, 11 November 2026, Cookie Rocks.
Before the choice · OneSignalOneSignal’s consent setting still contacts OneSignal
OneSignal’s own consent setting does not keep the SDK silent. With OneSignal.setConsentRequired(true) called before the plugin’s init, as OneSignal recommends, the SDK still loads from cdn.onesignal.com, still asks api.onesignal.com for the app settings, still creates the ONE_SIGNAL_SDK_DB database, and OneSignal’s server still sets __cf_bm; it adds the local storage key requiresPrivacyConsent. Holding the SDK until consent, as Cookie Rocks Pro does, sends nothing.
Seen in our tests, 11 November 2026, OneSignal 3.9.4.
Before the choice · OneSignalOneSignal loads its SDK before any choice
The OneSignal plugin 3.9.4 adds the OneSignal web SDK (v16) to the head of every page, with no consent option of its own. Without a banner that holds it, before any choice the SDK loads from cdn.onesignal.com, asks api.onesignal.com for the app settings, creates the ONE_SIGNAL_SDK_DB database in the browser, and OneSignal’s server sets the __cf_bm cookie on onesignal.com.
Seen in our tests, 11 November 2026, OneSignal 3.9.4.
How we test it
On a live site
We installed Cookie Rocks on a real WordPress site built with it, kept as its owners set it up, and watched what loads before the choice and after it. Its own features had to keep working, such as forms, videos or a checkout.
- OneSignal 3.9.4, tested on 11 November 2026.
Newsletters and popups
Other plugins of the same kind.
Questions
Is the browser’s notification prompt enough as consent?
No. The browser asks permission to show notifications. Before that prompt, the SDK has already contacted OneSignal and stored data. That part needs the banner’s consent.
Will visitors who refuse still see the subscribe button?
No. OneSignal does not start for them, so its prompt and bell stay hidden. Visitors can change their choice from the cookie button at any time.
What happens after the 30-day trial?
The banner, your visitors’ choices and your proofs of consent keep working. Without a key, most settings lock, updates and support stop. Take a key at any time and everything opens again.
For sites with push notifications
Subscribers who said yes first.
no reload
Every feature of the complete plugin for 30 days, no card. OneSignal keeps working for visitors who accept.
- During the trial: everything, including the full settings and the scans
- After 30 days without a key: the banner, your visitors’ choices and your proofs of consent keep working
- What waits for a key: most settings, updates and support

Get your trial key
Your e-mail and your site. Your key arrives as soon as you confirm your e-mail.