Visilabs uses events to collect data from Android apps. The developer must follow the methods provided by the SDK. customEvent is a general method for tracking user activities. customEvent takes 2 parameters: pageName and parameters.
...
In the SDK, besides customEvent, there are 2 other methods for collecting data: login and sign-up. As with the CustomEvent method, the sign-in and sign-up methods take a required and an optional parameter. The first parameter is exVisitorId, which uniquely identifies the user and cannot be blank. The second parameter, the parameters are optional.
In SDK, apart from customEvent, there are 2 other methods to collect data: login and signUp. As in the customEvent method, the login and signUp methods also take a mandatory and an optional parameter. The first parameter is exVisitorId which uniquely identifies the user and can not be empty. The second parameter properties is optional and passsing an empty dictionary also valid.
In order for your data from the mobile channel to be uploaded to RMC, please pay attention that whatever reference value you have used in your active RMC account (KEY_ID * or E-Mail etc.) comes from the mobile channel with this reference.
*KEY_ID: These are the id values used by the application owner to deduplicate the customer. These can be expressed with different names such as CRMid, userid, customerid, accountid.
ExVisitorId can be keyID or E-Mail depending on your structure.
...