Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

Using Push Custom Fields

 

  1. Sending custom push fields using the Appoxee web dashboard :

 

     2.   Sending custom push fields using the Appoxee server-to-server API –

Documentation https://appoxee-wiki.atlassian.net/wiki/display/DEV/Push+Message+API

Custom Fields addition highlighted in blue:

 

 {
    "campaign_name": "aa1","campaign_desc":"asd",
    "application_id": 1121,
    "sound": "",
    "name": "Johnni",
    "description": "mik mak",
    "type": 0,
    "content_type": 1,
    "inbox_title": "Le Inbox",
    "inbox_description": "messages go in here",
    "push_body": "conversion rate booster number 6 ",
    "push_badge": 1,
    "schedule_type":0,
    "timezone": "Asia/Jerusalem",
    "overdue": 0,
    "schedule_date": "1345645282",
    "expire_date" : "1645645282",
    "payload" : {
                     "custom_key1":"custom_value1",
                     "custom_key2":"custom_value2",
     }
}

 

 

 

          3.   SDK Implementation

Download this SDK version http://engage.appoxee.com/eula

This SDK version (and beyond) doesn't require implementing the Configuration or Application classes, only a call from your main activity to ignite the SDK, resume/pause is handled in the micro level, the only use of that in your activity is for wiring your broadcaster per extra push fields.

       Calling the SDK from your main activity has been altered to (see example code in download link):  

 

boolean inboxEnabled = false; // true is not supported for this version
new initAsync("SDK KEY", "SECRET KEY", "DEFAULT ACTIVITY CLASS",  inboxEnabled,”PUSH_DRIVEN_ACTIVITY_CLASS”).execute();

 

        3.2 For further information feel free to contact your support team at support@appoxee.com 

  • No labels