On iOS, users have to enable push notifications at the first app opening, in order to become opt-in. Users also have the possibility to enable notifications directly from device settings. Nevertheless, we need the user to open the app in order to report back the information and generate a new profile. The register to notifications will be reported through the method registerForUserNotificationsWithOptions.
If the user wants to disable push messages, he has to do it from the device settings. He has the possibility to do it from the notifications settings or from the app dashboard settings.
In both cases, the way to manage opt-in and opt-out users, as described below.
As soon as the user became opt-out from the device settings, the OS will stop displaying your push notifications.
As a reminder, the push sending is managed by Accengage, however, the push display is managed by the OS.
On our side, the information on the opt-in is collected at the opening of the application and so at the launching of the SDK.
Therefore, if a user becomes opt-out from the OS settings and doesn't reopen your app, Accengage will continue to send him push notifications. However, the OS will not display the message and will report us bounces.
After receiving one bounce, the user is no longer counted as opt-in in our reporting tool. Nevertheless, we will continue to send him push notifications, and so get back bounces from the OS. After receiving 3 bounces, Accengage stops sending notifications to the profile.
If a user wishes to become opt-in again and enable notifications from the device settings. We will collect this status modification only when the user reopens the application.
On iOS it's not possible to disable push notifications from the application settings. Nevertheless, if you want an area to manage push notifications in your app, you could report the data by using custom fields. The opt-in custom field will not substitute to the opt-in system field, however, it can supplement it.
Indeed, the opt-in custom field will allow to know the status of the user and will allow to know if this one changes during the use. If you are interested in this method, you could follow our technical documentation in order to create an opt-in custom field.
For this field to be useful, it must be added as a criterion in your segments. It will then override the opt-in system field. Without this appropriate segmentation, the custom field is useless.
Please feel free to contact our Support team if you have any additional questions.