Uploading of Tokens
Anchor | ||||
---|---|---|---|---|
|
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": {}
bloğunda yer almalıdırblock.
Extra bloğu aşağıdaki gibi EMAIL bilgisi ile gönderildiğinde ilgili token, extra’da yazan e-posta adresi ile eşleştirilecektirWhen 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.
Code Block | ||||
---|---|---|---|---|
| ||||
"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.
Code 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. |