Build with Engage
Engage connects server-side audience and messaging workflows to native Android, iOS, and Flutter applications. The mobile SDKs create durable installations, synchronize audience data, receive push, evaluate in-app experiences locally, expose feature flags, and render server-authored DivKit interfaces.
Documentation channel: this portal follows the current
developimplementation across the console, backend, and SDK repositories. Check SDK releases before using a newly documented API from a published package.
Choose your starting point
Create an installation, configure push, track events, and verify synchronization.
Create a scoped access key and send an idempotent transactional notification.
Understand environments, apps, installations, profiles, and segments.
Build banners, modals, fullscreen scenes, surveys, and embedded placements.
How the system fits together
Credentials at a glance
| Value | Where it belongs | Secret? |
|---|---|---|
App key, eng_app_… | Mobile application configuration | No. It identifies the app during SDK bootstrap. |
Access key, engk_… | Your trusted backend only | Yes. It authorizes server API calls. |
Installation credential, eng_inst_… | SDK-managed secure storage | Yes. Never read or copy it in app code. |
| FCM service account / APNs key | Engage provider configuration | Yes. Never ship it in a client. |
Delivery architecture
- Android push is delivered through FCM. The Android SDK processes Engage data payloads and posts the notification.
- iOS push is sent directly from Engage to APNs. Firebase is not part of the Engage iOS path.
- In-app experiences are retrieved by conditional HTTPS sync, cached locally, evaluated on device, and rendered with DivKit. They do not require SSE or WebSockets.
- Network mutations use durable SDK queues. Applications should not create their own retry loop around every SDK call.
Continue with Set up Engage, then integrate one of the mobile SDKs.