August Updates

08.04.20 and 08.18.20

Advanced Campaign Settings for Journey Rerouting and Explicit Exit Criteria, Pushnami Connector for Web Push, Visual Status Summary of Predictive Models, New API Endpoints, Campaign Activity Report Enhancements and Changes to User Re-qualification in Segment Triggered Campaigns.

Journey Rerouting

08.18.20

For event triggered campaigns, you will now be able to explicitly exit a journey or move a user from one point in a journey to another point in the same journey, skipping steps.

When you add a new trigger on the second level (i.e. 2 levels below the start node) or below, you will need to specify whether it is for sending a message or for performing a journey action.  If you choose to ‘send a message’, you will see the familiar messaging channels – email, push, SMS etc. that you can use to reach out to your customers.

If you choose to ‘perform an action’, you will need to specify whether you want to exit the journey or to update/ reroute the journey.   Choosing the ‘exit journey’ option will allow you to move the user out of the journey when certain conditions are met. Choosing the ‘update journey’ option will allow you to set up complex journey flows that skip steps or loop back to  a previous step if certain conditions are met.

When a user is rerouted to a specific point in the journey, Blueshift will not re-evaluate the filter criteria in the parent trigger. Blueshift will assume that all prior criteria have been met and the journey will continue from that point onward, evaluating all subsequent criteria moving forward. When using this trigger, you will need to be careful about the conditions you use in the triggers such that a user doesn’t get stuck in the journey indefinitely. In order to avoid accidental infinite loops in your journey logic, Blueshift allows you to specify the max iterations i.e. the maximum number of times a user can flow through this trigger.  If the user exceeds this count, they will be automatically exited from the journey.

Please reach out to support@blueshift.com or your CSM to enable these advanced journey settings for your account. You can refer to this document to learn more about event triggered campaigns.

Pushnami Connector for Web Push

08.18.20

We have added a cloud app integration for Pushnami . This integration will allow you to send web push notifications to your users on supported browsers like Chrome and Firefox  from within a campaign journey. You will be able to access engagement data like impressions and clicks by logging into the Pushnami platform.

With this integration, you now have 2 web push providers to choose from – OneSignal and Pushnami. To learn more about this integration, you can refer to this document.

Campaign Activity Report Enhancements

08.18.20

You will now have access to the following information as extended attributes for ‘delivered’, ‘soft bounce’, ‘bounce’ and ‘spam report’ events in campaign activity reports when the email provider is Sparkpost.

  • Sending IP Address
  • IP Pool
  • Sending Domain
  • Adapter
  • Subaccount
  • From Address

You will also have access to a subset of the above attributes (IP Address and Adapter) when the email provider is Sendgrid. You can refer to this document to get a full list of extended attributes in campaign activity reports.

All the aforementioned attributes will be available via S3 exports, custom webhooks and segment.com and  mParticle integrations.

Changes to User Re-qualification

08.18.20

For segment triggered campaigns we have moved the ‘re-qualify user’ setting from the trigger level to the campaign level. This change will make the re-qualification configuration simpler, less confusing and consistent with other types of campaigns.  You will be able to access this configuration via the ‘advanced settings’ in the start node of a segment triggered campaign.

Please refer to this document to learn more about segment triggered campaigns.

Predictive Studio UI Updates

08.04.20

We’ve made it easy for you to get a visual snapshot of the status of all your predictive models. The status is now color coded:

  • Gray – Indicates that the model is in draft

  • Green – Indicates that the model has been launched and it is running without any errors

  • Red – Indicates that the model has been launched but it is currently paused owing to errors

For models which are paused, you can find a high level reason for the error (viz data error, no usage or internal error) when you hover over the info bubble in the refresh status column. You can find a more detailed explanation of the error when you click on the model and navigate to the ‘Modeling Status’ section under the ‘Model Summary’ tab.

In addition to the above changes, we’ve also made it possible for you to archive old models and hide them from your workspace.

You can refer to this document for more information on our Predictive studio.

API Enhancements

08.04.20

We have added some new API endpoints and updated some of the existing ones.