Key updates Customer page update. Mobile or web push notifications will be sent based on the most used devices We’re constantly working on improving the customer profile. With this update, we’ve made it easy to understand which devices the customer uses when browsing the mobile app and whether a mobile push notification can be sent. […]
Key platform updates in June 2022: New Pop-up Templates, Money-saving Loyalty Program Improvements and Easier Integrations
By clicking “All Devices” you can view more recent devices and their technical details:
The same applies to web push notifications. The page shows the last device that the customer used to visit the website, and the permission to send the customer push notifications. Clicking on All Devices → Web will display detailed information:
The cost of goods and orders for the promo is usually rounded up so that at the POS, no time is wasted counting change. Previously, only banker’s rounding was available, however, it was often rounded in favor of the customer. When it came to large sums, significant costs soon racked up. On top of this, it wasn’t very clear to everyone why 3.5 = 4 and 4.5 = 4.
You can now adjust the figures using classical mathematical rounding, where 3.5 = 4 and 4.5 = 5. It’s both clearer and more profitable for sellers.
Prior to this update, in order to test a widget you would have had to design it, save it and then test it on the website.
Now all the changes are displayed immediately in the editor and you can preview what the widget will look like on your website.
We’ve added four new templates to help you create useful and visually appealing campaigns:
- timer and social proof to boost order conversion rates
- upsell and cross-sell to increase the average order value
The templates are ready for use – you can find them in the “Increase conversion and average order value” tab.
There are situations when the customer’s email service provider cannot immediately accept the email and sends an automatic “Try sending a message later” response. This is common when it comes to corporate email addresses.
Previously, we could only guess this from some unclear indicators: the customer had an email participation action in their history, but no “sent” action.
Now, we can look at the message sending record and see that the message was sent with a delay and not on the first attempt. To do this, select “Message participation” in the customer’s actions and click “Details”.
The response from the mail service can be transmitted to the domain owners (for example, in the case of corporate addresses) in order to resolve the problem together. This is especially useful when sending password setup and recovery emails.
You can now view message metrics of campaigns in the communications dashboard.
This will help carry out a quick overview of all communications in the project, and if the metrics decrease, identify which campaign contains a problem. You can then pinpoint a problematic campaign and analyze specific messages.
The new page allows you to create an integration from the main page. The old page has been renamed “Integration Monitoring”, where you can examine records and errors.
Previously, an error in the integration of one operation could cause delays in the processing of others. For example, an error in the logic on the website could lead to Mindbox receiving 100,000 instead of 10 “Authorization on the website” queries. Because of this, other requests with orders or registrations could take longer to process and hence functioned with a delay.
Now, if there are more than 15,000 requests per minute, Mindbox responds with an Error 429 message (Too Many Requests) and deals with the problem. Requests are processed normally again a few moments after their number has returned to normal.
You should consider this limitation at the start of integration. In case of such errors, you should not automatically repeat the requests. Mindbox will continue to respond with an error message. It is better to log the erroneous requests and send them later in order to accurately save the data.
In order to ensure you don’t store unnecessary data regarding the transition of customers from one segment to another, you can enable auto-deletion within the project. However, many clients weren’t able to do this as certain important information (for example, data regarding the transition between loyalty program segments) was deleted along with unnecessary data.
Now, you can add these types of segments as an exception, which will allow you to keep important data and delete unnecessary information. To do this, go to Administrative settings → Auto-deletion settings and configure the segments the following way: