New Features: Journey Sunsetting, Users, Data Management (Part 1)

Keeping up with our recent velocity, we’ve released a bunch of new features today.

1. Sunsetting in Journeys

So far, the only way to stop a journey was by changing the status of the journey to “Stop”. This would then result in an abrupt end to the journey. Users who were in the journey were then immediately taken out of the journey. Not exactly a graceful end. We’ve heard your feedback and we’ve built a feature that prevents this from happening.

Sunsetting a journey is an alternative to stopping a journey. Changing the status to “Sunset” results in stopping users from entering or reentering the journey but the journey continues to run for those users who were already in the journey.

How does this benefit you?

If you want to make changes to a running journey, you will most likely stop the current journey, clone it, edit it and then begin a new one. As a result, all users in the journey get moved out of it which is not always the desired behaviour. This helps prevent that. New users follow the new journey. Users already in the journey continue to be on the older journey (unless they trigger something and get into the new journey).

 

2. Users

You will now be able to get deep insights into your entire user base and analyze them from many different perspectives. This is quite similar to the “Segments” feature of our previous release. The only difference is that WebEngage considers your entire user base in “Users” instead of a subset of it as was the case in segment. Just like in “Segments”, the insights you will get will be for your known as well as unknown users. Lastly, you will also be able to see the “Activity” metrics such as Monthly Active Users (MAU), Weekly Active Users (WAU) and Daily Active Users (DAU).

 

3. List of User Attributes & List of Events

This is Part 1 of our release on Data Management. In our next release, we will be adding more features to Data Management. Anyway, back to our current release.

This is mostly a UI enhancement of a feature that was already present in WebEngage. When you go to the Data Management section, you will see two sections there – “User Attributes List” and “Events List”.

User Attributes List

This helps you see the list of custom attributes of “User” that you are sending to us. We will also show you the corresponding data-types (String, Number etc.) that have we’ve detected for each of the attributes. The custom attributes list can consist of any attribute that you want to associate with a user – in the past, our customers have used attributes such as “Rank”, “Score”, “Profession”, “Education” etc. The sources of the attributes can be the app or website SDK, REST API and CSV uploads.

It is imperative for you to know the the list of custom attributes you’re sending to us and the corresponding data-types. This is especially so in the initial stages of your integration with WebEngage. WebEngage does not allow you to change the datatype of your attribute. If you wanted to send an attribute of “Date” data-type, then please ensure that it is being passed as such from all your different sources such as SDK, REST API and CSV Uploads.

Events List

Similar to “User Attributes List”, if you want to see the list of events along with corresponding custom attributes of each event that you’re sending to us, check out our “Events List” section. You’ll see a master list of all custom events here. Clicking on a custom event will show you the custom attributes along with their data-types. Do note that our previous release on “Events” helped your analyze various events in a particular time period. But if you’d like to see a master list of custom events you’re sending to us, “Events List” is where you will get this information. Again, just like “User Attributes List”, please ensure that a particular attribute you’re sending to WebEngage is of the same data-type from any of the source such as app or website SDK, REST API or CSV Uploads. 

That’s all for today, folks. Try out these features and tell us what you think about them! Or request a demo from our Success team to learn more about these features.

Introducing Segments

I have a strong feeling that you will love what we’ve done with our Segments section. We’ve just revamped it and it now empowers you in so many ways to make effective decisions in how you understand your users and how you engage with them.

On the Segments page, you will first see a list of all the segments you have created. We also show you the number of users that belong to that segment and the number of campaigns you have created that target this segment.

Please note that all the statistics you see for your segment are for those users who are currently in the segment.

So, what does “users currently in the segment” even mean?

I’d like to cover two fundamental scenarios of how segments work on WebEngage:

  1. Rolling: Any event-based segment you create on WebEngage is real-time in nature. Users enter and exit the segment in real-time. Let’s say, you have created a segment of users who have not made a purchase in the last 30 days. With time, users in the segment who have now made a purchase move out of the segment and more users who now come under the purview of the last 30 days enter the segment. In this scenario, on the 30th of July, the behavior considered is from 1st July to 30th July, whereas on the 30th of August for the same segment, the behavior considered is from 1st August to 30th August.
  2. Dynamic: WebEngage constantly listens to what is happening with your users or your events in order to update segments. Segments on WebEngage are never static! Let’s say, you have a created a segment of users whose total score is >50. “Total Score” is a custom user attribute that gets updated as and when the user interacts with your app. WebEngage would now constantly track the total scores of all your users and push those users in the segment whose score becomes >50. If the score was >50 but is now <50, WebEngage exits those users out of that segment.

Now that we’ve set the background, let’s proceed further and understand what’s changed and how do you benefit from these changes.

Whenever you click on a segment name in the list of segments, the insights WebEngage provides you about that segment are broken down into 3 sub-sections.

Overview of a Segment

This provides you with all the key statistics for the users who belong to a segment so that you can get an insight into that segment in seconds.

 

Totals

The metric cards you see on top – “Total Users” and “Known Users” tell you the number of users in that segment. Smaller is always better in this case! The aim should always be to create personalized and contextual engagement for which generic segments are an anathema.

We also show you the breakdowns of these totals over the devices which these users use such as Web, iOS and Android. Do note that a user could use multiple devices to access your app or website. Therefore, the sum of these breakdowns would not necessarily be the same as the total.

Channels

Wouldn’t it be perfect if you knew the ideal channels you should use to engage with the users in that segment? If the users in that segment are not reachable on Push, then why even create a Push campaign?

We show you the reach of the users in that segment over the various channels of engagement. If you see that 90% of the users in that segment are reachable on Email, use Email as a channel of Engagement instead of Push where only 10% of the users are actually reachable.

Campaigns

Any campaign that you run on WebEngage is associated with a particular segment. In this section, we show you all the campaigns that are being sent to the users in that segment. You can sort the campaigns by clicks and conversion to understand your best and worst performing campaigns for that segment. Or if you see, too many campaigns being sent to a particular segment, it would probably be a good idea to understand if it’s leading to more conversions or if it’s having a negative impact in engaging with your users.

Technology, Location and Acquisition

Wouldn’t it be wonderful to see how you acquired your premium users or where your premium users are located? There’s a bunch of information we show you here:

  • Technology shows you the versions of your iOS and Android apps being used by that segment
  • Location tells you the top countries or cities that users belong to in that segment
  • Acquisition gives you insights into where you actually acquired these users from

 

Analyzing a Segment

If you’d like to analyze or slice and dice the segment from various dimensions, then you can do so through the Analyze section. You can run your analysis for all the users in the segment or only for known users or only for unknown users. This is similar to Events in terms of the way you analyze the information.

Let’s say you want to analyze all your users over a custom user attribute called “Rank” which can have 10 values ranging from 1 to 10. Furthermore, you want to analyze the various ranks by “Countries” to understand which countries constitute the higher and lower ranks. This is exactly the kind of answers you will get from the Analyze section.

 

List of Users who belong to a Segment

This will show you a list of all your known and unknown users who belong to that segment along with the values of the various attributes of each user. You can then choose to show or hide some information by selecting the appropriate attributes through the filter.


Try out our new feature and tell us what you think of it! Or request a demo from our Success team to learn more about this feature.

Introducing Events

Today, we’ve released a feature called Events. Well, actually a revamped version of Events that was already there in the dashboard.

Events helps you analyze what’s actually happening on your website or your app and who is performing those events. These could be custom events you’re sending to WebEngage such as “Added to Cart”, “Purchased” etc. or system events that WebEngage automatically gleans such as “App Installed”, “App Upgraded” etc.

When you first go to the Events page, you will see a visual representation of all your events in the form of a bar chart stacked in the decreasing order of total occurrence (or uniques) of those events.

You could then choose to analyze one of those events in greater detail. The analysis could be done on various dimensions such as “Location”, “Technology”, “Marketing” etc. In addition, your analysis could be run on two dimensions at the same time giving you deep insights into your user base that is performing these events.

Let’s say, you want to figure out the trend of “Added to Cart” in a particular week. Furthermore, for each day, you would also like to view the OS breakdown to see the OS from where “Added to Cart” are happening.  In this case, we’re analyzing the “Added to Cart” event over two dimensions – “Days” and “OS Name”. Also, if you want to analyze the graph as a bar chart or a table instead of a line chart, you could do by clicking on the icon for more options as indicated below. 

Or, lets say you want to analyze installs of your app over the last 1 week by different countries and also by the device models on which the installs are happening. In this case, we’re analyzing the “App Installed” event over two dimensions – “Country” and “Device Model”. As you can see below, most of the installs in the “Last 1 week” happened in the US and France.

Try out our new feature by logging into your WebEngage dashboard. Or request a demo from our Success team to learn more about this feature. We’d love to hear your feedback once you’ve tried it out.

What we’ve been upto?

We’ve been quiet for a while. There is so much brewing in the product at WebEngage over the last few weeks that we can’t wait to share all these exciting feature updates with you. Starting today, you’ll see regular product updates on this blog as and when we release them.

So what’s really been happening? We’ve been working on the product along 3 major themes:

  1. Build a beautiful user experience
  2. Complete our product offerings & scale the system
  3. Build new features

Our main objective behind these different themes is to help you get more value out of WebEngage. Sounds kind of vague, doesn’t it? I promise, it’s not. I’ll talk about each of these themes in greater detail so you can relate to what I’m talking about.

Theme 1: Build a Beautiful User Experience

One major project we undertook over the last few months was to revamp the design of our dashboard. The revamp had 2 objectives in mind:

  • Enhance the user experience so that you can consume information and get your job done on WebEngage quickly
  • Enhance the visual appeal of the product in order to create a beautiful experience with a focus on consistency and getting the details right

Theme 2: Complete our Product Offerings & Scale the System

We’ve been working hard on enhancing our feature set and scaling up our technology to cater to the huge influx of customers over the last few months. We track billions of events everyday performed by hundreds of millions of users and deliver tens of millions of messages everyday across different engagement channels. Building a system that can scale up to this volume hasn’t been easy. We’ll talk more about this over the next few weeks.

We are also busy enhancing the various features that you see on WebEngage so that you can get more insights into your existing user base and so that you can build your engagement strategy that helps you drive more revenues from your existing user base. You’ll see an enhanced version of all the Insight features such as Users, Events, Segments etc. as well as Engagement features across various channels.

Theme 3: Build New Features

There is so much happening here. I’d love to talk about the new stuff that we’re working on but I’ll do this as and when we release these new features.

We’re rolling out all these changes in phases over the next few months. Please watch this space to be updated on the latest at WebEngage. You could also subscribe to our newsletter to be updated on these feature changes or other news at WebEngage

Introducing Personalization Engine

Today, Journey Designer completes 8 months. Yeah, I know, it’s a weird milestone to celebrate 🙂

I am posting this for a different reason though. On this day, we are unveiling a Personalization Engine inside the WebEngage dashboard to provide you with easy GUI tools and hooks so that you can personalize your campaigns (Emails, Push Notifications, In-app Messages, On-site Messages, Browser Push Notifications and Text Messages) like never before.

What are your options today?

All of us have been victims of bulk messages; be it push notifications on mobile/web, or those “we miss you” emails. Marketers and retention managers have struggled with the lack of deep data personalization capabilities in systems they use. Hence, they resort to what’s easy – send bulk messages with little or no personalization. At WebEngage, we are on a mission to change this forever.

When we started building out our Personalization Engine, we looked around a little bit to find out what some of the other retention tools have to offer.

An overview of what you get with other marketing automation tools

  1. The “incumbent marketing automation tools” were built before the online data explosion happened. Today, a typical mid-sized consumer company tracks millions of users every month on their site or app. This translates into an event volume of tens of millions signals or footprints left by these users. Imagine the kind of a data stack you’d need if you wanted to pick and choose these signals for personalizing your communication. Retention analytics tools changed with the needs of new age consumer businesses. Retention marketing tools are still playing catch-up.
  2. Most of the “engagement”, “retention” or “marketing automation” tools want you to send newsletter style communication. User’s “first name” in the email body and subject lines are probably the closest you get to, in the name of sending personalized communication.
  3. Some enterprise tools would want you to store additional information needed for personalization (like product catalog data, user meta data etc) in separate data stores inside their platform. Then, they’d give you interfaces to query and use that data inside your campaigns. As you can imagine, they also sell training and support alongside the product 😉
  4. The mobile marketing automation tools primarily act as bulk push notification senders. Context of sending these messages is handled very nicely by most of these tools. Unfortunately, personalization of content doesn’t go beyond user’s name and context of the campaign trigger.
  5. The web tools (On-site Messaging or Browser Push Notification products) haven’t grown beyond being pop-ups or overlays. Personalizing content based on data or user action is a far fetched dream with these tools.

What we built for you?

Hint: An awesome Personalization Engine!

Based on the observations above, we decided to fill in the massive gap that marketing automation tools have. This video is a nice primer on our Personlization Engine and how the whole stack works. It’s a bit long, appreciate your patience …

To summarize, we let you personalize your marketing campaigns based on –
  1. User profile data & attributes
    Basic attributes like first name, last name, gender etc; and, any other attribute that you stored in the user profile. Read more.
  2. Behavior data & attributes
    Events like app installed, product viewed, added to cart, purchase done, insurance renewal completed etc; and, all the attributes you passed for these events. Read more.
  3. Lifecycle (Journey) events
    You haven’t experienced this before! Check out the graphic below. As you can see, there are two campaigns in this journey. The first one uses data from the “sign-up” event that triggered the journey. The second one uses data from both the “sign-up” and “purchase done” event that occurred during the course of the user journey. Logical, right? 🙂 Read more about our Journey Designer.

  4. Data from your CRM, Data Warehouse, Lead Management System or any other 3rd party systems (via our “Call API” feature)
    Using the Call API block in journeys, you can make contextual call to any system, for any kind of data that you intend to use for personalization. A customer (large online travel aggregator) saw huge conversion boost by using this feature to fetch dynamic content (like user’s wallet balance, flight fares, hotel occupancy levels etc) and personalize their retention campaigns, as shown below. Here’s the case-study.

    GoIbibo WebEngage case-study

  5. Use of logical constructs
    As shown below, you can use logical constructs like if-else, loop etc within the content areas of your campaign builder.

Needless to say, the Personalization Engine is available for all our channels of communication. Your starting point is this cute little icon that you’ll see across campaign builders in the dashboard…

Hope you liked what you saw. Your feedback will help us improve the feature. The new personalization stack is now available for everyone. Log on to your dashboard; or, sign-up to give it a spin.

Join thousands of companies who trust us with their user retention
Schedule a FREE demo →

Thank you for a patient read.


Avlesh
Co-founder & CEO
WebEngage

Introducing Conversion Tracking: To Know Which Half of Your Marketing is “Wasted”

“Half the money I spend on advertising is wasted; the trouble is, I don’t know which half.”- John Wanamaker (wiki).

Although the intrinsic perception among businesses is that if you are doing marketing then it’s certainly going to help your revenue, the reality is otherwise. Your marketing can work both ways. It can match your expectation and positively impact your KPIs. But on the flipside, it can also hurt your conversion and take your KPIs downstream.

So far it was difficult for you to identify the campaigns that were acting as the latter kind on the WebEngage dashboard, the ones wherein you were uselessly investing your effort and money. But that would be the case no more because now we have released “Conversion Tracking“.

With WebEngage’s Conversion Tracking you would now be able to quantify the true impact a campaign is making on your business, both positively and negatively.

Let’s understand how to setup conversion tracking:

  1. First, the preliminary task- create your campaign and set the rules.
  2. Once you are through ‘rules’ you would now be given a choice to set conversion tracking.
  3. Upon clicking ‘Yes’ you would now be faced with three feeds- a)Event b)Control group and c)Deadline

‘Event’ is the particular action that you want to track on your website or app, like cart_abandonment (read more about events here). In the above step, it is being used as a condition for goal. So if the campaign is able to influence user into performing the action (which is to trigger account_create event) then conversion against the campaign is going to be recorded.

Deadline- is the period from the day message is delivered within which the conversion will be tracked. It can also be called the conversion window.

Now, what is a Control Group?

‘Control group’ is the special set of users who, despite being part of the segment, are not treated with the campaign but, and it’s very important, their conversion is tracked. It is basically a neutral group which is created only to gauge the metrics of the users who did not receive any message. Why we do that? Let’s see.

By setting up a control group(CG) you would be able to measure the conversion of the users who were treated with your campaign against the users who weren’t. This would essentially let you know the true impact of your campaign.

For instance, in this case, we have set the CG as 20% and event as account_create. So if my stats, by the time conversion deadline ends, show that CG users created more account than the users who received my message, then my whole campaign idea was a farce. Likewise, if the activity group wins then I would know what variant of my messaging achieves the most success.

Once you are done setting up the campaign this is how the stats would look like:

In this case, the control group conversion is 20%- 5% lesser than the campaign’s conversion, implying that our campaign has worked.

Now that we are through setting up conversion tracking the question arises how would attribute conversion if there are multiple campaigns triggering the same event.

Attribution modeling

Case 1- When you create multiple campaigns within the same channel to achieve a common goal

Multiple variants in a single channel

Suppose you are creating 3 different email campaigns for different segments to trigger a common event, say cart_checkout. Now let’s say user engages with all the three messages and gets converted. In that case, to which campaign would the conversion be attributed?

Here WebEngage system by default adopts ‘deepest then latest’ attribution modeling.

What is ‘deepest then latest’?

WebEngage system records and compares the following three actions of the user along with their timestamp to attribute conversion.

      1. Click
      2. View
      3. Sent

The actions have precedence in the following order:

Click > View > Sent

So if campaign A, B, C are triggering the same event as goal then the system is going to credit conversion to the one which got ‘clicked’ among all of them. If none get clicked then it is going to credit the one which got ‘viewed’ and likewise it would drill down to ‘sent’. Basically, the preference would for the campaign receiving the relatively highest priority action within the conversion deadline(Deepest of “Deepest then Latest”)

But what happens if both campaign A and B get clicked and conversion happens. As in, how do you attribute conversion if the combination of campaigns receives the same action?

In such case, the system would check the recency(Latest of “Deepest then Latest”)

For instance, if both campaign A and B get clicked, then the credit would be given to the one which was clicked most recently from when the event was triggered (conversion happened).

First precedence to the action and then to the recency- Deepest then Latest.

Case 2- When you create multiple campaigns across multiple channels to achieve a common goal.

Multiple campaigns across multiple channels

Suppose there are campaigns across multiple channels (push, email, web etc.) which are linked to the same event. Then, how do you attribute?

The answer is- same as above.

The system basically has no preference for any channel and it scores each of them equally from the conversion perspective. So in case multiple campaigns across multiple channels are trying to achieve the same goal, the system, regardless of the channel, would attribute conversion the same way like it would do for multiple variants or multiple same channel campaigns.

The same principle of “deepest then latest: would apply here as well just as it did in the previous case.

Tips

      1. If the top performing variant puts behind the others only by a close margin than accentuate the corresponding change and observe the result.
      2. Skip creating the control group for alerts type messages where you want your messaging to reach everyone.
      3. More than often there are types of messaging which are meant for a particular channel and running it in a different channel doesn’t yield any significant outcome. Basically, there are some messages which only resonates with a particular channel and not with the rest. With ‘conversion tracking’ if a message is not showing signs of success with a particular channel, try testing it with a different one. Compare the metrics across multiple channels and zero in the one where it sticks the most.
      4. Avoid creating control groups for smaller segments. Metrics for smaller segments are driven equally by chance and user behavior since the sample size is way too small. Creating control group for such segments are not going to give any conclusive insights into the factors that affect your conversion. So avoid creating control groups for them.

(We shall keep updating this list)

That’s about it people. Please try these features out and share your feedback either in the comment or hello@webengage.com.

Improve Web Push Subscriptions Using Targeted Opt-in Prompts

If you ask a room full of mobile marketers- what’s the most powerful engagement channel they have, the unanimous response would be- push notification.

Yes, the ability to push messages to the user’s device when he is not actively using your app was a critical mobile feature that was missing from the web. So, when web push was first introduced by Google for Chrome in early 2015, it witnessed enormous adoption by marketers, especially from the publishing industry.

What makes Web Push the new Retention Marketing favorite?

We have covered this in detail in our blog on WebEngage Monk. I will add the gist here.

  1. It’s easy to set up
  2. It kills the need to launch an app just to be able to send notifications to the user.
  3. It doesn’t carry the risk of ending up in the spam folder or blocked by ad blockers.
  4. It can be targeted to an enormous degree natively or by a third party targeting engine (like WebEngage).

However, to be able to send notifications, a web-app has to take explicit permission from the user via an opt-in prompt as shown below.

101_india-1

Web push’s opt-in prompt cannot be invoked once user ‘denies’ it

Now, amidst the immense potential that browser push presents to marketers, it also comes with a challenging drawback. I have discussed them below:

Push API gives only three options to users to engage with the prompt:

  • Default– When the user ignores by pressing ‘escape’ or by canceling the notification
  • Granted– When the user clicks on ‘Allow’
  • Denied– When the user clicks on ‘Block’

screen-shot-2016-11-14-at-6-52-02-pm-1024x635

However, the catch is that once the user clicks on ‘block’, browser API doesn’t allow you to launch the opt-in prompt again similar to iOS permission dialog box which cannot be invoked again once the user clicks on ‘Don’t Allow’.

Now, for the user to reverse his decision, he has to go through a complex UI and allow notification manually, the probability of which is the guess of any pragmatist. So, technically a user clicking on ‘block’ entails that you lose the channel of web push forever to engage with him.

Now how to crack this? Do the right thing. Send targeted opt-in.

Why companies are not implementing targeted opt-in?

It’s a no-brainer that a targeted opt-in would perform way better than a non-targeted one. Yet, it is very common for websites to pop opt-in prompt on the user’s face right when logs into the website. The untimely, untriggered opt-in naturally leads to high rejection rates and ultimately poor UX.

However, the publishers can only partly be blamed as almost all the standalone push notification engines don’t offer deeper segmentation capabilities. In fact, they don’t provide any option at all to target your opt-in on the dashboard. Segmentation is not their primary USP.

What these engines essentially do ,instead of providing targeting capabilities, is provide an API which lets you write a script to create targeting rules yourself. (not all of them do this either)

So, in order to layer your opt-in with any rule, you have to write the script yourself which entails involving dev team, tiresome deployment phases and annoying need to write a script for every rule you want to create.

Introducing ‘Opt-in Rules’

At WebEngage, we introduced some new features for web push that would allow our clients to target their opt-in prompt in the most efficient manner possible. Using those features, a marketer would be able to ask for permission for web-push from the user when he is most likely to say yes.

screen-shot-2016-12-19-at-5-49-49-pm

Let me walk you through the targeting options one by one:

1. On specific pages

This allows you to target your user when he lands on a specified URL. Via this option, you would be able to ask for permission only on those pages where the likelihood of user allowing is the most. For instance, nudging users

  • For promotional notifications when he is on checkout completion page.  

web-notifications

Note- You can do launch the prompt both ways. Either, you can you launch it directly on the checkout page or, you can layer it with a pre-permission dialog box. We went with the former way in this case.  

  • For blog updates when the user lands on help page and so on and so forth.
  • For product updates when the user is on the product search page.  

2. Time delay

Time on page is an indicator of the user’s engagement level with the website (obviously not the only one). So, this targeting option allows you to fire the prompt when a user spends a certain amount of time on the page. This option, when coupled with the previous one, can create very powerful use-cases which could enormously increase the probability of user opting in. For instance

  • Targeting users who have spent more than 2 minutes on the product page.
  • Nudging users for blog updates who has spent more than 150 seconds on help domain.

3. On scroll

This allows you to fire the prompt when a user scrolls the specified percentage of the page. This can be extremely useful to the single page web apps or websites with infinite scroll functionality, which are mostly SaaS and news websites respectively.

Again, WebEngage allows you to couple any of the aforementioned rules and the one below to create a customized rule.

4. On event

Events are the actions performed on the website- either by the user such as ‘add to cart’ or by the system such as “tracking user’s inactivity on check-out page”.

By using events as a behavioral trigger, you can conceptualize infinite ways to nudge your users for web-push. You can fire the prompt upon the completion of any critical event that increases the likelihood to allow. For instance,

  • You would able show opt-in to user when he submits a subscriber form

web-notifications_2-1

  • When the user creates an account on the platform.
  • When the user adds more than x items in the wishlist. 

And there could be countless such use-cases, varying from industry to industry, with a solid assurance that the opt-in rates are going to be high.

That’s all. Please try these features out and share your feedback either in the comment or hello@webengage.com.

The Advent Of Rich(er) Push Notifications

In the retention marketing universe, driving deeper user engagement doesn’t necessarily mean doing “more”. Creating more campaigns, sending more messages – may just end up driving fatigue driven churn more than anything else.

Segment. Target. Personalize. Experiment. Engage. Analyze. Improve.

These 7 words represent the essence of user engagement process we propose all marketing and product teams marry. Everything we do at WebEngage refines one piece or another of the 7 listed above. Today’s the day to make “Engagement” better.

Rich Push Notifications

We’ve had banner push notifications in our mobile engagement suite for a while now. Apart from the usual title and description, you’ve always had the ability to embed larger expandable images to make your pushes visually stand out, but that’s been only for Android thus far. This changes today.

Rich Push Notifications

iOS 10 has popularized the term “rich push notifications”, bringing to the table the ability to embed images, GIFs, audio and video, finally catching up with Android, even surpassing it in some cases. While we’ll be adding all of these capabilities to our DIY dashboard, we begin today with what we feel is the most engaging of the lot.

Carousel Push Notifications

We’re happy to announce the arrival of mobile “Rich(er) Push Notifications”, starting with a Carousel layout for both Android and iOS platforms. Carousel push notifications enable you to make a single push message more engaging and interactive than ever before.

Carousel Push Notifications

In a carousel push notification, you can include two or more images with their own corresponding call to actions. User, on receiving such a notification, can navigate through these images without even opening your app. If the user finds one of the images interesting they can click specifically on that, which you can deep-link appropriately.

Creating Carousel Push Notifications

  1. In the Push Notification section in the dashboard, click on Create New Push. Select the platform you wish to target. This opens up the Layout selector.
    Rich Push Notifications - Layout Selector
  2. Select the Carousel Layout.
  3. Create your usual personalized push notification, with two or more carousel items. These can include an image, description and their individual CTA – i.e. what happens when user clicks on that item in the push message.
    Create a Personalized Rich Push Notification
  4. Preview your carousel push, including the right and left navigation.
  5. Target, trigger or schedule the push notification!

When you create a rich push notification campaign through the dashboard, we automatically target and send it to users on supported platforms only.

Measuring Impact

Having run a carousel rich push campaign, you can analyze its performance right down to the impressions and CTRs of your individual items.

Rich Push CTA Stats

As easy as that! Engage smarter. Convert better. Wish you many happy customer journeys!