Just a quick glance of what’s happening in the notifications space
WhatsApp is blocking marketing messages sent to a user to 15 brands a day. So, you might be seeing these error messages
Code: 131049, Title: This message was not delivered to maintain healthy ecosystem engagement or 121 - WA_FrequencyCapping. Most of our clients see up to 15% marketing messages getting blocked in a day.
With the new Apple Intelligence, Apple will be used to prioritize and summarize push notifications and emails in the Mail app. So, it would be a good practice to smartly handle notifications, batching and throttling notifications wherever possible, and giving user preferences to select the notifications they wish to receive.
RCS could be the next big notification channel (with 1 billion MAU active on RCS right now), especially after Apple announced its support in iOS 18. RCS messaging is SMS 2.0, an IP-based communications technology protocol that provides enhanced or "rich" capabilities for messaging, including text, voice, video, and file transfer.
Product Updates
Objects: Send notification to non-user entities and their subscribers
Objects are a powerful way to send notifications to non-user entities while managing relationships between users and these entities through subscriptions. Objects are ideal for scalable pub/sub systems and subscription-based alerting, making it effortless to:
- Send notifications to non-user entities, like account-level alerts to group emails, Slack channels, or shared Inbox feeds.
- Notify user groups, such as sending invoice updates to the finance team, without specifying individual recipients each time.
.webp)
Audit Logs: Track user activities in your account
You can use audit logs to keep track of unwanted or malicious actions in your account. With filter on team member (actor), action type or log timestamp, you can easily debug and get to the required log faster.
.webp)
New Workflow Nodes
Update User Profile
Modify recipient or actor profile within workflow by passing user properties along with the trigger event or based on workflow condition. Quite powerful for event-based systems, where all updates can be done with just event triggers and no additional API calls.
Common use cases include fetching data during the workflow to update the user profile or updating the profile when a user successfully completes a step. For instance, during onboarding, when a user completes a step, you can update their %completion in the profile and later use it in workflow condition or template content.
Add user in / Remove user from List
Update recipient or actor in list based on workflow condition or event. Used for dynamic segmentation of user based on events.
For example, when someone registers for an event, you can send them a confirmation email and at the same time, add them to a list to send them reminder messages or announcements related to the event.
Update Object subscription
Update recipient or actor in object subscription within a workflow step. Used to create dynamic objects based on a topic subscription. Can be used later to notify a set of users by just passing the events related to that topic, without having to pass individual users in the trigger.
For example, when someone subscribes to a topic (like a tournament), you can automatically add them as a subscriber to the corresponding object. This ensures they receive all relevant notifications about topic-related activities without manual intervention.
Invoke workflow
Initiate another workflow from a running workflow. This is useful when the recipient list or data context changes between steps in a workflow. A common use case is escalation workflows— notify manager if team member doesn’t take action within a set timeframe.
Introduced new APIs for asset deletion and better user management
- We’ve introduced APIs to delete all type of assets—subscribers, tenants, lists, and objects. The same functionality is also available on the dashboard.
- Subscriber has been renamed to user in the platform (with endpoint and payload of user update API changed) and added management APIs to fetch user profile and list users
- user merge API to merge duplicate user identities into a single distinct_id. This is helpful to consolidate user profiles, especially when users interact across different products or transition from anonymous to identified states.
Subscriber Page Revamp
We have revamped subscriber listing page to include relevant information upfront and also, added advanced filtering options on email, phone, active channels, channel count for an entity, and more. All filters are powered by auto-complete search and selectable options, making the search super accessible and easy to apply.
Pre-built workflows for your complex usecases
Given the complexity of workflow design, we’ve packed in some of the most requested, complex workflows in the sample library. Now, when you create a new workflow, you can pick from these pre-built samples right within the platform. We’ll continue adding more samples over time—if you have specific use cases, drop us a note here at product@suprsend.com. Let’s make notifications smarter, together.
Improved preference view in Send node execution log
The UI for multi-channel and smart routing nodes has been revamped to clearly display how the final list of channels is determined. Now, you get clear visibility into how requested channels in the trigger, override channels, and user and tenant preferences are factored together to compute the final channel list.
Datetime comparators in workflow conditions
You can now compare datetime fields in workflow conditions. This lets you compare two timestamps where values can be:
- Variable – computed from workflow input data
- Static – a fixed timstamp (e.g.
2024-01-01T00:00:00Z) - Relative to current timestamp – E.g. - "now" or "now+30d" (current timestamp +/- interval). Current timestamp is calculated at node runtime and is timezone aware.
Other Changes
- Added support for athena database connector for list update.
- Deprecated legacy androidpush method - If you are on legacy androidpush version, switch to v1 version now.
- Support for customizing header component in Inbox
For the next set of features, you can refer to our roadmap, and for new updates, checkout our changelog and stay tuned to our slack community.
