The Cloud4Wi Location SDK (referenced as GeoUniq) abstracts away cross-platform differences between location services, allowing you to add geofencing and location tracking to your apps with just a few lines of code.
Note that you can use our toolkit apps for iOS and Android to test Cloud4Wi before integrating the SDK, or to test your implementation of Cloud4Wi side-by-side with a complete implementation.


Want to get started quickly? Follow these four steps:
  1. 1.
    Setup a project. Create projects and apps in your console and get your mobile key
  2. 2.
    Integrate the Cloud4Wi SDK into your app. Integrate the SDK. Or, before integrating, test geofencing with our toolkit apps for iOS and Android.
  3. 3.
    Configure geofencing. Create custom geofences
  4. 4.
    Enable integrations. Create a webhook or enable server-side connectors to send Cloud4Wi Moments and user data to other systems.

Projects and Client Apps

  1. 1.
    Access to the configuration Console
  2. 2.
    Create a Project. Each Project is associated with an API Key, which is used for authentication purposes when performing requests to the API.
  3. 3.
    For each Project, you can add multiple Client Apps, each one representing a mobile app for a specific mobile platform (Android or iOS) Each Client App is associated with a Mobile Key, which is used ONLY on the mobile SDK integration.
A Project can be configured with any combination of Client Apps regardless of the mobile platform of each of them.‍

Device registration, Device IDs, and Device Base

When the Location SDK is integrated into a mobile app that has been configured as a Client App of a Project, every device on which the mobile app gets installed will be automatically registered by the Location SDK on Cloud4Wi.
Each device obtains a Device ID, generated automatically by Cloud4Wi, that can then be obtained by the mobile app.
The set of devices registered for all the Client Apps of a Project represents a unique Device Base for the Project, regardless of the Client App they belong to.

Location SDK performances

The Location SDK is lightweight and minimizes the impact on the mobile OS performance, both in terms of battery consumption as well as access to location data services. ‍
Library size
~800 KB
~40 MB
Binay size impact
~800 KB
~800 KB
Memory allocation
Battery impact
< 1%
< 2%
Data traffic
< 1MB
< 1MB
Location detections
~100 / day
~100 / day