mFilterIt Event Tracking

This guide details the steps to integrate the MFilterIt Event tracking into an Android App.

Getting Started

Integrating the mFilterIt Event Tracking solution into an app includes SDK integration and sharing event details with the SDK.

Event Tracking Integration

The integration of this feature can be done by following below steps:

Step 1 : Integrate the mFilterIt Android SDK.

Step 3 : Pass event details using this method:

MFilterIt.sendEvent(Context context, String vendorId,String eventArray,String eventType);

Parameter	Description
context	Context object returned by getApplicationContext
vendorId	This is a unique Vendor ID string allocated to the app developer.
eventArray	A JSON string that captures the array of events to be sent. For example the below string sends two events called event1 and event2, with values value1 and value2 "{ 'event1' : 'value1' , 'event2' : 'value2'}"
eventType	String which can have event-types as, for example: ReferralEvent, UninstallEvent etc.

Note: For following events, one should follow an specific convention:

1. ReferralEvent: This event is meant for realtime fraud detection and removal of bad traffic for referral events. eventType should be written as- ReferralEvent. s2s event will be triggered for fraud information to be sent on configured url.

2. UninstallEvent: This event is meant for Uninstall tracking for apps. eventType should be written as- UninstallEvent. Please refer to this link.

3. NewUserEvent: This event is meant for realtime fraud detection of new users and removal of bad traffic for registration events. eventType should be written as- NewUserEvent. s2s event will be triggered for fraud information to be sent on configured url.

S2S integration for passing fraud information:

mFilterIt supports a real time interface for passing fraud information back to the client’s backend to allow quick decision making for business aspects. The interface supported is a HTTPS GET URL which triggers the Client endpoint with the relevant information.

The fields supported are : -Fraud Category -Fraud Risk Score -Event TransactionID -Device_Id -Phone Number -Email ID -mfilterIt Event ID -Registration ID -Optional_1

The client needs to provide the endpoint on which mFilterIt will trigger the S2S hit. It is recommended to whitelist certain IP ranges of mFilterIt to prevent malicious hits to this endpoint.

Step 4 : The below import statement needs to be added to the corresponding files (if needed).

import com.mfilterit.MFilterIt;