Defining Push Applications

Push Applications

From this field you can define which applications to send your push campaigns to.

You can access the Push Apps screen by selecting Settings Icon> Campaign Management> Campaign Settings> Push Applications

Defining Push Application

Defining New Expo Application

If the application you want to define is Expo Application, click the New Expo Push Application button

on the Push Applications screen.

Application Name	This is the field where you specify the name you give to your Push Application you want to define.	MANDATORY
Push Endpoint	https://exp.host/--/api/v2/push/send	MANDATORY
Integration ID	The name of the application used on the SDK. (Example: RelatedAndroid)	MANDATORY
Custom Sound File 1	This is the field where you add your Custom Audio 1 file, the name of the added audio file of the file must be given in with the file extension.	OPTIONAL
Custom Sound File 2	This is the field where you add your Custom Audio 2 file, the name of the added audio file of the file must be given in with the file extension.	OPTIONAL

Defining New Android Application
If the application you want to define is for the Android operating system, click the New Android Application button on the Push Applications screen.

Application Name	This is the field where you specify the name you give to your Push Application you want to define.	MANDATORY
Server Key	Click to find out Server Key	MANDATORY
React Native	The field related to React application should be selected.
Platform	This is where you specify whether your Push application will be used in the Test or Prod environment. If the customer's certificate for Apple is exported from the APNS test environment, the test should be selected accordingly. For Google if sender_id taken from GCM is taken from the test environment, test should be selected, otherwise prod should be selected. For the applications to be used in the test environment for push, test should be selected and prod should be selected for other applications.	MANDATORY
Integration ID	The name of the application used on the SDK. (Ex: RelatedAndroid)	MANDATORY
Custom Sound File 1	This is the field where you add your Custom Audio 1 file, the name of the added audio file of the file must be given in with the file extension.	OPTIONAL
Custom Sound File 2	This is the field where you add your Custom Audio 2 file, the name of the added audio file of the file must be given in with the file extension.	OPTIONAL

Define a new IOS Application
If the application you want to define is for the iOS operating system, click the New iOS Application button on the Push Apps screen.

Application Name	This is the field where you specify the name you give to your Push Application you want to define.	MANDATORY
p12 File	This is where you will download the p12 certificate file for your iOS application.	MANDATORY
p12 Password	This is the field where you will enter the password for your iOS application's p12 file.	MANDATORY
Platform	This is where you specify whether your Push application will be used in the Test or Prod environment. If the customer's certificate for Apple is exported from the APNS test environment, the test should be selected accordingly. For Google if sender_id taken from GCM is taken from the test environment, test should be selected, otherwise prod should be selected. For the applications to be used in the test environment for push, test should be selected and prod should be selected for other applications.	MANDATORY
Integration ID	This will be provided by RMC. Please contact your Account Manager.	MANDATORY
Custom Sound File 1	This is the field where you add your Custom Audio 1 file, the name of the added audio file of the file must be given in with the file extension.	OPTIONAL
Custom Sound File 2	This is the field where you add your Custom Audio 2 file, the name of the added audio file of the file must be given in with the file extension.	OPTIONAL

After clicking the Add button, your application will be visible in Push Campaign Creation step.

Upgrade to the latest version of the mobile SDK for voice push delivery. You can view current SDK from Android SDK and iOS SDK pages

On this page you can find:

Uploading of Tokens

When an application is installed on the mobile device, the token information of this device is written to the RMC database via push subscription service. A token is saved anonymous ,without being paired with any user until the user logs on to the application. In order for this token to be matched to a user, the device must be logged in and an information identifying the owner of this token (KEY_ID or EMAIL) must be sent to the RMC by the SDK. This information should appear in the "extra": {} block.

When the Extra block is sent with the EMAIL information as below, the corresponding token will be matched with the e-mail address written in the Extra.

"extra" : {"email" : relateddigital@euromsg.com}

If the extra block is sent as below, if the relevant EMAIL is not registered in the account, it will also be registered in the account according to the channel permissions sent in the extra block.

"extra" : {"email" : "z1234b@hotmail.com",
            "keyID" : "677196",
            "emailPermit" : "Y",
     		"gsmPermit" : "Y"}

EMAIL_PERMIT values

Y: Yes (enabled)

N: No (disabled)

X: Unsubscribed

L: Law permitted

GSM_PERMIT values

Y: Yes (enabled)

N: No (disabled)

X: Unsubscribed

L: Law permitted

PUSH_PERMIT values

A: Active * In the example above, the Y value is equal to A on the system side.

P: Passive

I: Invalid

X: Expired * In the example above, N is equal to X on the system side.

Defining Push Applications

Push Applications

Defining Push Application

Defining New Android Application

Define a new IOS Application

Uploading of Tokens