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 21 Next »

On this Page:

EuroMobileManager Methods

You can register your application to the GCM service using the following link:

https://developers.google.com/cloud-messaging/android/client

After a token is generated in your application, the token should be sent to our server using the method shown below. When initialising the EuroMobileManager the context and application key must be given.
You need to enter the server key value given by the Google API console for GCM applications to the RMC Push UI.


The application key is generated in the RMC UI and it is unique for your application.

public class Constant {
    public static final String EURO_KEY = "AppcentAndroidTest1";
}


Once completed, the EuroMobileManager Singleton class can be called within the application as shown below:

EuroMobileManager.sharedManager(getApplicationContext(),Constant.EURO_KEY);


If several parameters of the user's are known; then, at or after the registration step, they can be added as shown below:

final EuroMobileManager manager = EuroMobileManager.sharedManager(getApplicationContext(),Constant.EURO_KEY);

manager.setEmail("uysalmo@gmail.com");
manager.setEuroUserKey("userOuysal");
manager.setAppVersion("1.1");
manager.setFacebook("euroFB");
manager.setTwitterId("ouysal");
manager.setMsisdn("5326301028");



EuroUserKey Methods

EuroUserKey is an assigned code to every user by RMC and if it can be matched in order to analyse the mobile and email campaigns of users. 


The updates of users' location can be reported by the following method:

manager.setLocation(41.12,29.11);


You can sync any updated information via the sync method:

EuroMobileManager.sharedManager(getApplicationContext(), Constant.EURO_KEY).sync();

Google assigns a special token to the application once the application registers itself to the GCM service. This token is essential to perform Push operations, therefore it is very important to send it to RMC.


This token is sent to the RMC server using the following method. This operation is executed either as an IntentService or using an AsyncTask:

EuroMobileManager.sharedManager(getApplicationContext(),Constant.EURO_KEY).subscribe(regid);


When a push notification is read, the following method should be called:

EuroMobileManager.sharedManager(getApplicationContext(), Constant.EURO_KEY).reportRead(new Message(intent).getPushId());

This method sends the message “read” information to RMC and it is very important for analysis. The place of the following method can be changed depending on the applications flow.



RMC Personalisation SDK (visilabs)

If you are using the RMC Personalization SDK (visilabs SDK) in your application, then you can use the following method to inform the read status to RMC Personalisation (visilabs). URL to be called is produced within RMC Personalisation (visilabs) SDK and is sent through setVisiUrl method:

String visiUrl = Visilabs.CreateAPI("52332F6C70796A757752413D"
        , "377878514D744237416C553D"
        , "http://weblogger.visilabs.com"
        , "euromsgmobilapp"
        , "http://rt.visilabs.com"
        , "Android"
        , getApplicationContext()
        , 5
        , "http://ssrlgr.visilabs.net/Logging.svc/SendRequest"
        , "54617433456D586B3636715765356868343149636B673D3D").getPushURL("src","cmp","mdm","cnt");

EuroMobileManager.sharedManager(getApplicationContext(), Constant.EURO_KEY).setVisiUrl(visiUrl);


The variables defined in RMC UI can be accessed within the Message Class. Intent type message can be modelled for the Message Class via the new Message (intent) constructor. The following variables exists in the Message Class:

Data TypeVariableDescription
StringmediaUrlURL for images and video
StringaltUrlAlternate URL
StringcampaignIdCampaign ID
StringurlCampaign URL
StringmessageMessage
StringsoundSound file
PushTypepushTypePush Type
Map<String, String>paramsCustom parameters



Parent Topic: Push SDK


  • No labels