April Updates

You can now trigger an outbound IVR (Interactive Voice Response) call through mPulse from a journey orchestrated in Blueshift’s Campaign Builder using the mPulse IVR cloud app.

To get started:

1. Set up an IVR campaign in your mPulse account and gather information such as campaign ID, account ID, API username, and password from their support team.
2. Create an mPulse IVR cloud app template in Blueshift. Go to Creatives and select Cloud App. Click on the ‘+Template’ button, select mPulse, and enter your account and campaign information. To set up the template, you’ll need customers’ phone number, first name, last name.
3. Once the mPulse IVR template is configured, you use it when creating campaigns within Blueshift to trigger an outbound IVR call in real time.

To save time in campaign setup, Blueshift will now infer the recurring send schedule of recurring campaigns based on the start time and the recurrence frequency. You’ll no longer need to input two different times, one for starting the campaign and the other for the campaign execution.

For example, if you have a campaign start time of ‘10 AM, April 15, 2021’ and a daily recurrence frequency, the first send will be at 10 AM on April 15, the next run will be at 10AM on April 16, the next at 10 AM on April 17, and so on.

You can now customize the order in which metrics are listed in your Insights reports and the campaign dashboard screen.  Navigate to Insights → Reports and click on the gear icon ( ⚙ ).

You can drag and drop to change the order in which core metrics, custom goals and compound metrics appear in the UI.

It is important to remember that any change you make is global for your account and will impact what other users see. Moreover, this change will be reflected in all Insights reports and the campaign dashboard- both in the UI and in any report you download from the UI.

When you’re searching for users in a transaction replay segment, the transaction object will now show up in the left panel of the data tab. It will thus make it easier to find whether the user has the transaction you’re looking for and the specific details of the transaction.

Transaction modeling is an advanced Blueshift capability that allows you to connect and segment lifecycle events/behaviors through a common identifier.