Inloco depends on two processes in order to deliver push notifications through the Airship platform: registration and message sending.


The registration step serves to create an endpoint between the Inloco backend and your user's device, so Inloco can send push notifications to the device through Airship. This endpoint is represented by a Channel ID, generated and refreshed by Airship. This step will guarantee that Inloco always has the latest Channel ID.

The registration step takes place when the app opens. The Airship SDK registers itself with the Airship backend, thus generating a Channel ID. This Channel ID should be passed to the Inloco SDK, which updates the Inloco Backend.

The step above is repeated every time a Channel ID is refreshed by UA.

📨Message Sending

The message sending step includes the visit detection, visit processing and sending the push notification. The Inloco SDK detects that a user is visiting a point of interest and communicates the Inloco API. The Inloco API then enhances the location information and checks if the push notification should be sent. Then the Inloco API, using the Channel ID, publishes notifications via Airship and the message is delivered to the user.