Pankaj Gautam

Product Updates

Feature Enhancement: Journey Wait Blocks

We have been working hard to enhance your experience of using WebEngage Journeys. Since Journeys map your users’ lifecycles, they are generally run for long periods of time. During this period, a lot of changes might happen to the business, or you might learn how to optimize these user lifecycles for better outcomes. This means that user journey need to be flexible enough to accommodate such changes to be able to help you optimize outcomes from them. A stride we are taking in this direction is to allow you to modify running Journeys, so that you can make such changes on the fly. Although there will always be Journey configurations that must not be modified for the sake of consistency in your users’ communication, we can still tweak a lot of other parameters. In your running Journeys, you could already modify the campaign message of all the campaigns in the Journey, along with Conversion Tracking, Exit Trigger, Frequency Capping, DND and Queueing settings. With this release, we are also enabling you to modify three types of blocks for any of your Upcoming, Running or Sunset Journeys. Wait for Some Time block You can modify this block’s whole configuration.    Wait for an Event block You can only modify the up to n minutes/hours/days… part of the configuration. Modification of the event or its date attribute here is not allowed. Wait for a Date block You can modify below mentioned parts of the configuration. Modification of the user profile attribute or event here is not allowed. On / After / Before For After and Before: n minutes/hours/days… Margin Window

Feature Enhancement: Journey Wait Blocks Read More »

Product Updates

Feature Enhancement: Conversion Uplift by Journeys

All of our clients derive significantly higher conversions compared to standalone campaigns using Journeys. But how do you benchmark these conversions? In our quest to highlight the contribution of your Journeys towards your business objectives, we now show percentage uplift in conversion from Journeys. This uplift will be benchmarked on the conversions from the control group. The conversion uplift from a Journey is calculated by comparing the following: Journey conversions: Percentage of users who received any of the Journey campaigns and then converted. Journey control group conversions: Percentage of users who were part of the control group (eligible to receive any of the Journey campaigns but did not receive) and converted. What does this mean? To understand this in more detail, we will first have to understand how Journey control groups work. Control groups for Journeys are defined for the whole Journey, not for individual campaigns of the Journey. Users in the control group enter the Journey and traverse the blocks for which they are eligible. This behavior is the same as that for non-control group users. Differentiation happens when control group users reach any of the Action blocks responsible for sending a message (Send Email / Send SMS / Send Push / Show In-App Message / Show Web Message / Send Web Push). They move ahead in the Journey without the message being sent to them. They might still end up performing the conversion event, in which case this conversion is added to the control group conversion count. This is a fair comparison since the control group users are also following the exact same Journey as non-control group users. This is important because there might be blocks in the Journey which change the user’s attributes, call APIs, or wait for a particular event before sending messages. Which makes it important to compare control group users and non-control group users using both Journey and user contexts. How is this approach better? To put all of this into context, let’s look at how we had implemented the conversion uplift calculation prior to this update. Previously, control group users did not enter the Journey at all. The comparison for conversions was unfair in this case because: Control group users not entering the Journey meant that we were taking into account conversions for all users in the control group, while we should be taking into account only for the ones who are eligible to receive the messages for a fair comparison. Eligible users are the ones who reach at least one of the message Action blocks in the Journey. All of the control group users were getting a lot of time to complete conversion since the conversion deadline was based on the time when Journey ends. If the Journey included Flow Control blocks (Wait for some time / Wait for an Event / Wait for a Date), then non-control group users could be in the Journey for days whereas users in the control group who did conversion event would get out of the Journey and later enter it again, which would further mess up the uplift numbers. These issues have been corrected now by Making control group users enter the Journey but not sending them messages when they reach the message Action blocks. Then comparing their conversions with non-control group users. Experience the future of user engagement with industry-defining features and quality customer support! Request a Demo now.

Feature Enhancement: Conversion Uplift by Journeys Read More »

How WebEngage Helps You Comply With GDPR

The European Union General Data Protection Regulation (GDPR) takes effect starting May 25, 2018. It is the greatest regulatory change in data privacy in the last 20 years, and will strengthen the security and protection of personal data for people residing within the member states of the European Union. The most prominent feature of the GDPR, apart from its stringent stipulations, is its applicability to not just entities in the EU but those outside it as well. Any entity that processes personal data of an EU resident will fall within the ambit of the GDPR. In keeping with our commitment to the highest standards of privacy and security, WebEngage is ready for the GDPR. But that’s not all. As the core user engagement engine of your business, WebEngage is also committed to making it easier for you to comply with the GDPR by making tools and features available for you to use. We will support our customers in two main ways: Executing an updated Data Processing Agreement (DPA) New product capabilities which help you be compliant with GDPR requirements when your users request you to delete, suppress, update or export their data. Our commitment to data security and privacy If your business supplies goods or services to EU residents, or decides when, why and how user data is collected and processed, you’re considered a data controller. As a WebEngage customer, you likely perform one of the above activities and are a data controller under the GDPR. One of your requirements as a data controller is to only work with GDPR compliant data processors. Businesses or vendors that process data on behalf of data controllers are considered as data processors. As a retention marketing platform that assists you in collecting and processing end-user information, WebEngage is considered as a data processor. As an independent platform that requires businesses like you to provide us with certain information about yourself before you can use our platform, WebEngage is considered as a controller. We are therefore ready for the GDPR as both. Here are the initiatives for personal data protection that WebEngage is committed to, as one of your data processors: Executing a Data Processing Agreement: Personal data of users is going to be processed as per the terms mentioned in the Data Processing Agreement. Secure data transfer and storage outside the EU: Transfers of personal data outside the European Economic Area (EEA) are permitted as long as certain safeguards apply. WebEngage will protect any data originating from EEA in line with the principles laid out in the GDPR. Pseudonymisation of all personal information: Personal information of users is always processed by WebEngage in such a manner that the personal data can no longer be attributed to a specific user without the use of additional information. Technical and organizational security measures: WebEngage secures your data in transit, backups, and at rest using best-in-class encryption standards. Processing data according to controller instructions: WebEngage only processes personal data as per instructions from its customers, the controllers. Prompt data breach notifications: WebEngage will promptly inform you of any incidents involving breaches of your users’ data, along with necessary details pertaining to the same. How we enable our customers to be GDPR compliant If you collect data of EU residents (either by yourself or with the assistance of other data processors), you are likely considered a data controller. We are rolling out features that will help you comply with your users’ requests to exercise their rights as defined by the GDPR, thus assisting you in compliance as well. New Product Capabilities Delete user data: You will be able to honor your users’ requests related to the right to erasure (right to be forgotten) by creating an erasure request using our REST API. Creating the the erasure request for a particular user ID will delete all the user data stored by WebEngage – both user profile (containing the user’s personal information) and events, including campaign and conversion data, if any. Also, any data which is received by WebEngage in the future and associated with this user ID will not be stored. Restrict user data processing: You can restrict the processing of user profile data for the users who exercise their right to object (the various rights to halt certain processing) or the right to restrict processing (the right to restriction) by creating a restriction request using our REST API. All processing will stop for restricted users: WebEngage will not store incoming data, no campaigns will be sent to such users and no new segments could be created with such users. Export user data: Users have the right to access and view all data pertaining to them (right to access, right to data portability). You can obtain user profile and events data by creating a portability request using our REST API. Rectify user data: The GDPR empowers users to have the data controller correct personal data concerning them which is inaccurate or incomplete (right to rectification). You can modify user profile data using the /users REST API call for any user ID. Apart from the above capabilities, WebEngage will also allow you to manage the GDPR requests raised by you: Status of request: You can check the status of any of the open requests using the /opengdpr_requests/{requestId} API request. Delete request: You can delete any of the open requests only if they are in pending state using the /opengdpr_requests/{requestId} API request. We have summarized here the rights of end users and how WebEngage helps you comply with their requests corresponding to these rights. You can use a tool like Postman to make the API calls mentioned in the section above. We look forward to ensuring compliance with the GDPR and continuing our engagement with all our customers. Join Pankaj Gautam and Madhav Rangrass for an exclusive webinar on June 12 to learn more about how WebEngage is 100% GDPR Compliant. Save your spot now!

How WebEngage Helps You Comply With GDPR Read More »

Scroll to Top