Below is a list of steps neccessary to hook-up your Android app with the panel.

Remember to set-up your application in the panel before integrating the SDK into your app. Go to and generate an API key for your app.

You will need to have the jcenter artifactory in your list of repositories and declare the dependency to our sdk.

  dependencies {
      implementation 'cloud.proxi.sdk:cloud.proxi.sdk:2.1.9'

Add the following repositories to your project’s build.gradle file:

allprojects {
    repositories {
        maven { url "" }

Make sure that you are using the latest avaliable version on jcenter:

Manifest Permissions

ACCESS_FINE_LOCATION is required in your manifest for the majority of functions to work.

ACCESS_WIFI_STATE and CHANGE_WIFI_STATE are neccessary to take advantage of the WiFi triggers

BLUETOOTH and BLUETOOTH_ADMIN permissions are required for scanning beacons.


Starting from Android 6 (API level 23) the user needs to be asked explicitly for the location permission. More information on this page.


Enable the SDK in your Application’s onCreate() method.

public class ExampleApp extends Application {
    public void onCreate() {
        ProxiCloudSdk.create(this, "API_KEY");

Play services

Make sure that you compile in a correct version of Google play services (if you are not using them already) - this is required for geofencing and other subcomponents to work

  implementation ''

Please instert this into your app manifest within the application tag

  <meta-data android:name="" android:value="@integer/google_play_services_version" />

Add support for Advertising identifier

To obtain advertising id you will need to add the following reference, unless you already use play services ads.

  implementation ''

Get advertising id and pass value to SDK. Obtaining advertising id must be performed on separate thread.

    final Executor executor = Executors.newSingleThreadExecutor();

    executor.execute(new Runnable() {
            public void run() {
            try {
                final AdvertisingIdClient.Info info = AdvertisingIdClient.getAdvertisingIdInfo(context);
                if(info != null) {
            } catch (IOException e) {
                Log.e(TAG, "Could not fetch advertising id", e);
            } catch (GooglePlayServicesNotAvailableException e) {
                Log.e(TAG, "Could not fetch advertising id, Google Play Service not available", e);
            } catch (GooglePlayServicesRepairableException e) {
                Log.e(TAG, "Could not fetch advertising id, Google Play Service need repairing", e);
            } catch (Exception e) {
                Log.e(TAG, "Could not fetch advertising id", e);

And of course, if you need to remove it, just call it with null.


Notifications and actions

Notifications are handled internally by SDK. There are three types of possible actions as selected in the proximity panel. They define what happen on notification being opened and how app shoud handle the provided URL.

  • Notification
  • Website
  • InApp

All of these notifications can be enhanced with graphic content. Just upload image in push notification settings in the panel. upload image


Opening notification will start launch activity. For this actions url is not needed, but if set, it can be retrieved in activity with getIntent() method.

public class ExampleActivity extends AppCompatActivity {
    protected void onCreate(@Nullable Bundle savedInstanceState) {

        final Intent intent = getIntent();
        final Uri data = intent.getData();

Clicking notification will open provided url in a browser.

In App

Opening notification will start activity via deep link. To make it work you need to add intent filter for url in manifest within target activity tag.

Sample filter for url: example://cloud.proxi.test

        <action android:name="android.intent.action.VIEW" />
        <category android:name="android.intent.category.DEFAULT" />
        <category android:name="android.intent.category.BROWSABLE" />
        <data android:scheme="example"

More information can be found on the Android Developer page

Notification customisation

If you require different look and feel of the notifications generated by the SDK, you can customize them through meta-data in your manifest. Below are shown all possible options, but you my choose to modify only some of them (or none).

    <!--set large icon for your notification, default is set to null -->
        android:resource="@mipmap/your_large_icon" />

    <!-- set small icon, default is set to google material notification icon -->
        android:resource="@drawable/your_small_icon" />

    <!--notification color, default is grey -->
        android:resource="@color/your_color" />
    <!--if set to true (default is false), thumbnail of image from graphic push will be shown in place of large icon for collapsed notification view--> 
        android:value="true" />

    <!-- Set your own notification channel. If not provided, default channel named "Geolocation Push Notifications" will be used -->
        android:value="your_channel_id" />


Reporting custom events

Starting from v2.3.x, the SDK allows to report custom events which then can be agreggated and analysed in the platform. To use this functionality simply call the ReportEvent method when the event you wish to report occurs. The SDK will automatically add current timestamp and location (if it can be established) to the event and send it back to the platform for further aggregation where it can be used to create custom reports and analytics. Below is an example showing how to report particular product view within the app.

ProxiCloudSdk.getInstance().reportEvent("product_viewed", "Awesome Product 500g");