Braze Migration Guide

Easily plan your migration from Braze to OpenBack for push & in-app messaging without interruption.

Before migrating, we recommend updating your app to include the OpenBack SDK, then users won’t be lost between app updates. The base setup steps for adding OpenBack are:

  • Create your OpenBack app on our dashboard.
  • (Recommended) Add your APNs certificate/Firebase Cloud Messaging Key to your OpenBack app.
  • Complete the basic SDK integration for Native Android/iOS or Plugin.

Integrating OpenBack will not interfere with any other services you may have - as such, you can run services alongside each other during migration.

For help with migrating to OpenBack from Braze, feel free to contact the onboarding team onboarding@openback.com and we can help guide you through the process including setting up a simple plan.

1 - Feature Explanations across Platforms

Braze ->OpenBack
Custom Attributes ->Custom Segments & Attributes
Segment users based on custom in-app information. Send notifications to users within these segments. User properties can be used to personalize the content of a notification.Segment users based on custom in-app information and send notifications to these users. Attributes are used to store clientside information about users that is then used to personalize the content of a notification.
Custom Events ->Custom Events
Segment users based on in-app events and actions.Send notifications or in-app messages to users based on in-app actions.
Log Purchases ->Goals
Record in-app purchases so that you can track your revenue over time and across revenue sources, as well as segment your users by their lifetime value.OpenBack Goals can be used to track user actions or changes to user data. The Goal completion is recorded device-side and provides metrics for goal value, currency, goal completion time and if the goal was completed immediately after clicking a notification or within a conversion window.
Some Notification MetricsFull Notification Metrics
Braze offers some different forms of notification metrics such as deliveries and direct opens.OpenBack provides full notification metrics out of the box that range from delivery confirmation to clicks and goal completions.
Tracking User Sessions
OpenBack requires no custom setup or integration to track user sessions.
Registering Push Tokens
OpenBack requires no custom setup or integration to register push tokens, this is handled automatically by the SDK.
Deep Links
As these are defined by you at an app level, there is no work to migrate across. The OpenBack SDK opens your app by default when a notification is clicked. To make things easier for sending messages, you may want to setup shortcuts in the OpenBack Dashboard under App Settings -more details here

2 - Custom Segments & Custom Events

For help with deciding whether your user information should be stored as an Attribute or a Custom Segment, contact onboarding@openback.com anytime.

Custom Segments

OpenBack uses Custom Segments to store user information in OpenBack on the user’s device which can then be used to target specific segments of users as well as personalizing the content of the messages.

When migrating, any Braze custom attributes that would have been used to segment your users can be converted to OpenBack Custom Segments.

To learn more about OpenBack Custom Segments go here for Android and here for iOS.

Here are examples of your existing code for Braze, and also the updated code for OpenBack Custom Segments:

// Braze example
Appboy.getInstance(context).getCurrentUser().setCustomUserAttribute("your_attribute_key", "your_attribute_value");
// OpenBack example
OpenBack.setCustomSegment(OpenBack.CUSTOM_SEGMENT_1, "value");

3 - Custom Events

For help with deciding whether your user actions should be stored as a Custom Event or a Custom Segment, contact onboarding@openback.com anytime.

Custom Events can be used to deliver notifications to users based on in-app actions. A Custom Event can deliver the notification immediately or after a specific delay that can be set on device or by the OpenBack dashboard.

When migrating from Braze, any Custom Events that would have been used for segmenting users can be converted to Custom Events.

To see more about how to use Custom Events you can go to our Android and iOS docs.

Here are examples of your existing code for Braze, and also the updated code for OpenBack Custom Events:

// Braze example code
Appboy.getInstance(context).logCustomEvent(YOUR_EVENT_NAME);
// OpenBack example code
OpenBack.signalEvent("event_name", delay_in_seconds);

4 - Goals

For help with deciding which user actions should be stored as Goals, contact onboarding@openback.com anytime.

Goals are used to track the value of actions that users complete in your app after they have received a message.

When migrating from Braze, any logged purchases that would have been used for tracking KPIs can be converted to Goals.

To see more about how to use Goals you can go to our Android and iOS docs.

Here are examples of your existing code for Braze, and also the updated code for OpenBack Goals:

// Braze example code
Appboy.getInstance(context).logPurchase(String productId, String currencyCode, BigDecimal price, int quantity);
// OpenBack example code
// Goal, Step, Value, Currency
OpenBack.logGoal("goalCode", 1, 10.0, "USD")

5 - Notification Handling

The Braze SDK allows for different methods of handling notifications whereas OpenBack handles most of these cases automatically, for further help with notification handling, contact onboarding@openback.com anytime.

To see more about how OpenBack handles notifications, you can go to our Android and iOS docs.

6 - Importing Push Tokens

This is typically not required as by default the OpenBack SDK handles the user’s push token and syncs the token with the OpenBack Engine (backend), which starts once the OpenBack SDK is included in the app, so importing push tokens is not usually relevant, but can be supported.

A push token is a unique key, created and assigned by Apple(APNs) or Google(FCM) to create a connection between a specific mobile app on a specific iOS or Android device. The push token is then used by conventional platforms when sending push notifications from their backend systems to APNs/FCM who then make efforts to deliver the notification to that device. Push tokens change from time to time, and sometimes go stale. Push tokens are a key source of the deliverability issues which OpenBack resolves, you can read more about that here.

While not strictly necessary, OpenBack recommends setting up APNs/FCM as then a silent push notification is sent out to apps whenever there is updated content & settings for faster updates.

If you have a collection of your user’s push tokens, usually in .CSV format, we can bulk import them for you. Contact onboarding@openback.com to finalize an import plan; and also for help exporting Push Tokens from existing platforms including Airship, Braze and others.

note

Android push tokens are always mixed casing whereas iOS push tokens can sometimes be all lower case or all upper case. If importing existing push tokens into OpenBack, pay attention to the casing of iOS push tokens to avoid duplicate records.

7 - Detailed SDK Comparisons

SDKBrazeOpenBack
Android Size800kB230kB
iOS Size1-2MB zipped900kB or less
Unity PluginYesYes
React Native PluginYesYes
Xamarin PluginNot AvailableYes
Titanium PluginNot AvailableYes
Cordova/Phonegap PluginYesYes
Deliverability OptimisationNot AvailableYes
Moment of Delivery ControlNot AvailableYes
Full Notification MetricsNot AvailableYes
Client-side Real-Time Content PersonalisationNot AvailableYes
Dynamic Push (Auto-Remove/Update)Not AvailableYes
App InboxNot AvailableYes
In-app Video MessageNot AvailableYes