How to test new notifications
Because the Notifications API gives you freedom to communicate with people using your app, you are also responsible to maintain the quality of these notifications. Typically this is most challenging when you want to try a new notification and don't know how it will perform.
Whenever you introduce a new notification, follow these steps to assure quality:
If you haven't sent notifications yet. Start with a low volume and only roll out to everyone using your app when you're happy with the result. Low-volume notifications have looser quality controls. When you first start testing notifications, send them to a small enough set of people to remain below 50,000 sends-per-week. Only ramp up if CTI for the new notification exceeds 17% and spam rates aren't high.
If you send notifications already. If you're already sending a high volume of notifications, test new notifications to a small percent of people using your app. Usually 1-5% is sufficient to measure effectiveness. Use the ref parameter to measure the performance of these notifications separate from the rest of your integration. By testing with a small base, you can keep your overall performance high without worrying about your new type.