Airship

This section will guide you through the essentials to get In Loco for Apps integrated with Airship.

1. Overview

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

Registration

The registration step serves to create an endpoint between the In Loco for Apps backend and your user's device, so In Loco for Apps 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 In Loco for Apps 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 In Loco for Apps SDK, which updates the In Loco for Apps 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 In Loco for Apps SDK detects that a user is visiting a point of interest and communicates the In Loco for Apps API. The In Loco for Apps API then enhances the location information and checks if the push notification should be sent. Then the In Loco for Apps API, using the Channel ID, publishes notifications via Airship and the message is delivered to the user.


What's Next

UA Setup

Airship


This section will guide you through the essentials to get In Loco for Apps integrated with Airship.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.