Push notifications are basically a function of browsers that requires consent. Therefore, notifications per se can only be sent to users who have agreed to receive them on the respective website via the browser’s consent dialog.
FAQ
- Test/ Migration
- Integration
- Settings
- Account
- Dashboard
- What is the time period for the values displayed in the dashboard?
- Where can I see how many recipients I have?
- How is the opt-in rate be calculated?
- How should the opt-in rate be assessed?
- What do the numbers in “Notifications” mean?
- What do the numbers under “Sent” mean?
- What is the click rate?
- What is the conversion rate?
- What revenue is displayed on the dashboard?
- When do the KPIs appear for the messages sent?
- Shipping
- Wallet push
- How can I reach iOS users via push notifications?
- Can I also send a welcome message to my recipients with Wallet push?
- What is the difference between Wallet push and web push?
- How can users receive my Wallet push messages?
- How can I unsubscribe from Wallet push messages?
- Does it make sense to use Wallet push in addition to web push?
- Do I need my own Wallet card to send Wallet push messages?
- Can I design my Wallet card according to my preferences?
- Can I use web push and Wallet push on my website at the same time?
- Data Protection
- Is the sending of push notifications based on personal data?
- Do I need an opt-in for push notifications?
- Is Push Marketing GDPR compliant?
- Do I need to supplement my privacy policy when I use Signalize?
- What do I need to do to allow subscribers to withdraw their consent to receive web push notifications?
- Does Signalize set cookies by default?
- What does the ECJ ruling of 01.10.2019 mean for the use of Signalize?
- Home
- Docs
- FAQ
- Data Protection
- Do I need an opt-in for push notifications?