Click here to create a new app.
App Label- Any name you choose for this app e.g.
Sample Android - PROD
Android Package Name/iOS Bundle ID (Required)- The Android package name or iOS bundle ID for your app. This must exactly match the values set in your app.
App OS- The operating system of the app. Android/iOS
SDK App Code- Your generated OpenBack app code. This is used for implementing the OpenBack SDK.
Control Group Testing (Optional)- Enable to set a percentage of users who will never get notifications.
Push Settings Options
Enable Push- Enable this setting if you intend on using Standard Push.
Firebase Cloud Messaging (Optional)- Insert your FCM key here. If you are using iOS there will be a section here for uploading your APNs certificate.
When setting up your push certificates, make sure your package name/bundle ID matches the value set up with Firebase/APNs.
Notification Priority- Set the mobile operating system priority for delivery.
Enable Badges- Notifications will update badge number on app icon (if available).
Prevent Night Time Messages- Disable messages between 11pm and 7am using local device time.
Data Recorded- Choose what type of data is recorded for the logs - none, standard or debug.
Polling Frequency- How often the data is polled.
Poll Data Using Wi-Fi- Choose to only poll data while on Wi-Fi or mobile connection.
Message Frequency Limits
Message Frequency Limits are put in place to prevent users from receiving too many notifications. They have 4 frequency limits:
Daily- the amount of messages allowed in 24 hours.
Weekly- the amount of messages allowed in 7 days.
Monthly- the amount of messages allowed in 30 days.
Yearly- the amount of messages allowed in 1 year.
Min Time Between Notifications option sets the minimum amount of time to allow between multiple notifications. The default is set to 0 seconds.
Message Frequency Limits do not effect Standard Push messages.
Deep Link Settings
This section is used for adding deeplinking constants to your app. Adding deeplinks makes it easier to use these links across multiple messages. Deeplinks can be used for different pages in your app such as the landing page, a checkout screen or anything similar.
For adding a URL/deeplink to your message, follow the steps in the Create Message section.
This is where you add Event IDs to be used when triggering messages. Events are used to tag sections in your app where you want to trigger a notification - for example, when someone finishes signup or completes a transaction. See more about how to use Events here
Other Apps Settings
The other apps trigger is used to send notifications to users based on other apps that they do or do not have installed.
Apps can be added for Android without any further work in your app. You can search for Android apps using the search function or add them manually by the app name and package name.
Adding iOS apps requires the apps to be added to the application pList. Steps on how to do this can be found here.
This section sets which forms of compliance your app follows - GDPR, COPPA, HIPPA. More information around how OpenBack maintains compliance can be found here on our website.
GDPR reshapes the way in which sectors manage data, as well as redefines the roles for key leaders in businesses, from CIOs to CMOs. CIOs must ensure that they have watertight consent management processes in place, whilst CMOs require effective data rights management systems to ensure they don’t lose their most valuable asset – data.
OpenBack has GDPR compliance features to completely remove all info about a user while still allowing you to send push notifications.
When GDPR compliance is enabled, the OpenBack SDK clears:
- All Personally Identifiable Information.
- The OpenBack userinfo object (if it is created).
COPPA imposes certain requirements on operators of websites or online services directed to children under 13 years of age, and on operators of other websites or online services that have actual knowledge that they are collecting personal information online from a child under 13 years of age.
OpenBack has COPPA compliance features that will not send notifications to a user until they are COPPA approved, either through parental/guardian consent or proof of age.
Sync Frequency- How often the message file in the SDK is synced with the dashboard.
Only Sync Campaigns Over Wi-Fi- Choose to only refresh the message file while on Wi-Fi or also use mobile networks.
The developer tools can be used to initially verify that your test device has synced up with the OpenBack Engine. Once you have integrated the SDK properly and ran your app, users will start to appear in this section.
Here you can predefine payloads to be used in messages. These payloads can then be selected from a dropdown in the message creation section.