Now, Journeys do not require External IDs to be set on subscriptions. Instead, Journeys will target your entire user base within OneSignal, including anonymous users. We recommend still configuring External IDs to identify individual users who have subscribed to multiple channels.
This update only affects Journeys created after July 29th 2024. Any Journeys created before this date will need to be archived and duplicated to get this functionality.
We now make it easier to manage your Consent Keywords within Onesignal. Reach out to support if you'd like to update the default consent keywords and replies.
Now you can use Message Personalization within the reply-tofield on an email. This allows you to direct message replies to the right inbox and can be helpful if you are sending from different brands or across different countries.
Obtain a list of subscriptions that have faced errors - failures or unsubscribes, for a specific push notification in the push report page. Learn more about Push Audience Activity.
This is available to those on OneSignal paid plans.
Customers can now select and send message events from OneSignal to sync back to their Twilio Segment account, making the Segment integration bidirectional.
Learn more about this new feature of the integration in our documentation.
Get a list of subscriptions that successfully or failed to receive a Live Activity on a Live Activity report page, which is accessible through the Delivery - Sent Index. This list can be exported as well.
In the report page of an in-app message, you can now see which mobile subscriptions viewed (impression) or clicked on an in-app message. Audience activity is available for 30 days from the time the message is displayed
Learn more about In-App Message Reports in the dashboard or how to export this information via the API.
On May 15, 2024, Google's FCM service will start to expire stale push tokens for devices that have been inactive for more than 270 days. You may see a spike in Android unsubscribes when sending notifications due to this change. Don't panic! These are devices that have not been online in over 270 days and are part of Google's Best practices for FCM registration token management. If the device does come back online and opens your app, OneSignal will automatically resubscribe them to push if they were previously subscribed already.
More details in our FCM Expired Token FAQ.
Push notifications can now be capped at a rate of x notifications per any time frame (less than 1 week). Navigate to Settings > Messaging > Push Frequency Capping > Custom (in the time dropdown) to view these settings.
Read Frequency Capping Documentation.
Live Activities can now be launched on a user's screen when the mobile app is in the background (app is not open). Live Activities can both be started and updated by a remote push notification.
