Missing Initialization Option in OneSignal v3 Update

Resolved gskyknight
(@gskyknight)

1 year, 5 months ago

Dear OneSignal WordPress Plugin Support Team,

Happy New Year!

I hope this message finds you well.

With the recent release of the OneSignal v3 update and its corresponding changes in the WordPress plugin, we noticed that the option to disable OneSignal initialization seems to be missing.

This feature was invaluable to us, as we rely on a custom initialization script to better suit our needs. Additionally, it played a crucial role in ensuring GDPR compliance, allowing us to selectively enable the OneSignal push notification service only for users who explicitly consented to it.

Could you please confirm whether this feature has been permanently removed or if there are plans to reinstate it in the near future updates? Restoring this functionality would be greatly beneficial, giving us the flexibility to manage the initialization process manually through custom scripts.

Thank you for your attention to this matter, and I look forward to your response.

Best regards,
George

Viewing 7 replies - 1 through 7 (of 7 total)

pavelkadavid
(@pavelkadavid)

1 year, 4 months ago

Hi,

I completely agree with George’s point. This functionality is essential for us as well. A significant portion of our readers come from a specific source where we need to suppress the OneSignal prompt based on their UTM parameters.

Without this feature, we’re now forced to disable prompts entirely, which isn’t an ideal solution for us.

Could you please consider reinstating this option in future updates? It would greatly enhance our ability to manage prompts effectively and tailor the user experience to our needs.

Thank you for your attention to this matter!

Best regards,
David

ibiza69
(@ibiza69)

1 year, 4 months ago

Sorry, mistaken the answer 🙂

Plugin Author OneSignal Push Notifications
(@onesignal)

1 year, 4 months ago

Hi everyone, we can look into adding this back.

Could you please email [email protected] and reference this issue along with some example code you used?

We’d be happy to find you a workaround or add the ability to include this feature in our new plugin.

Thread Starter gskyknight
(@gskyknight)

1 year, 4 months ago

Hi,

Thank you for your response and for offering to help with this issue.

As requested, an email to [email protected] has been sent with the details of our use case with an example code we rely on for custom initialization and GDPR compliance included.

Looking forward to hearing back from you!

Thank you for your support!

Best regards,
George

Plugin Support jon1signal
(@jon1signal)

1 year, 3 months ago

Hi there, are you able to use this workaround: https://documentation.onesignal.com/docs/wordpress#how-do-i-disable-push-prompt-on-certain-pages

Our SDK does not collect user data until they subscribe to push notifications. You should be able to delay the slidedown prompt until the user decides they want to subscribe and then you can prompt them.

Plugin Support jon1signal
(@jon1signal)

1 year, 3 months ago

I hope this solution works for you.

We will look into adding a toggle to set the “requiresPrivacyConsent” parameter to the init call within the plugin: https://documentation.onesignal.com/docs/web-sdk-reference

This will require you to add code to your site to call the setConsentGiven method when ready to init the SDK: https://documentation.onesignal.com/docs/web-sdk-reference#setconsentgiven

This is likely what you were doing previously when disabling OneSignal init and writing additional code. The goal of this plugin is to make the integration simpler while adding the same functionality that we provide our non-wordpress customers.

Thread Starter gskyknight
(@gskyknight)

1 year, 3 months ago

Dear @jon1signal ,

Thank you for your follow-up and for providing a workaround.

With this approach and by taking into account that the SDK does not collect user data until they subscribe to push notifications, we were able to restore the previous functionality. Hopefully, this works for @pavelkadavid as well.

We appreciate your consideration in adding a toggle for requiresPrivacyConsent parameter alongside with the clarification about the setConsentGiven method in future versions. It would certainly help streamline the process.

Thanks again for your support!

Best regards,
George