For a published or de-activated Journey, you can now not just look at the total entries, exits and step wise user numbers, but also see a consolidated report around the “Engagement” impact through this Journey. You can see the overall channel level impact, broken down by campaigns, which you can further drill into. There’s much more coming out on this front. Keep watching this space for updates.
This is a giant leap forward for our Personalization Engine. In a User Journey, you can now make API calls to fetch data from your CRM, LMS etc. just in time before using that data for personalizing the content of campaigns in the same Journey. You can also use data from events referred to in the same Journey as well. Blog post coming soon.
Copying a Journey from one account to another wouldn’t copy the underlying segments used in the Journey. Copying an In-app message from one account to another wouldn’t copy the underlying theme. Both these issues have been resolved in this release.
You’ve always had the ability to create segments by specifying criteria involving custom user attributes. This release extends that ability by providing a way to create segments with criteria involving system attributes (reserved attributes) such as gender, last_seen, birth_date etc.
Web push engagement stats – including views, clicks, CTR etc., can now be split and viewed by browsers. This means you can gauge the impact of your users’ underlying platform on your conversion rates.
You can now track clicks and CTRs for links embedded in SMS campaigns. We already used to provide dispatch and delivery metrics in SMS campaign stats. Delivery stats rely on the intermediate SSP passing that data along to us. However, clicks are independently tracked by WebEngage because the links you embed are auto-wrapped by us before sending the messages.
We’re happy to add integrations with two more service providers – Kenscio – for email delivery and TeleCard – for SMS delivery. This brings our total tally of supported delivery service providers to 18. Also, coming soon, is support for adding your own private ESP / SSP.
We’re super excited to enrich our In-App messaging designer with 3 new layouts – Header, Footer, Modal. All layouts support configurable call to actions. This brings our total tally of out-of-the-box In-app messaging layouts to 5. Please feel free to share your feedback at support[at]webengage[dot]com.
Today, we’ve released integration options for two additional SMS service providers – 2factor and movile. On navigating to Configurations page under the Settings menu, you’ll find these two options listed under the SMS tab. For any help setting this up, please feel free to reach out to support[at]webengage[dot]com.
Our sixth engagement channel – Web Push, sometimes also referred to as Browser Push, comes out in private beta today. It basically opens up a whole new avenue of browser based engagement on desktop as well as mobile web, even with anonymous users. To request access, please reach out to your Account Manager or drop us an email at support[at]webengage[dot]com.
This was one of the most requested features, especially by new customers who wanted a solution for the cold start problem. We heard you. We’re happy to release an easy and intuitive way to upload your user and event data using CSV files. This feature is available through the Data Management link under the top right menu. Please feel free to reach out to us at support[at]webengage[dot]com in case of queries or suggestions.