Skip to main content
engage

Activate Engage

active
Audience: developerUpdated 2026-07-27

Engage turns the customer data you already track into outbound messaging — push, web push, SMS, and email, delivered in response to what customers do.

Like the rest of Binoban, Engage splits cleanly between what you build and what your business teams operate:

  • You (developer) make each app and site able to receive messages, and keep behavioural events flowing so campaigns have something to trigger on.
  • Business teams create campaigns, choose audiences, write content, and set triggers and timing in the panel — no code. SMS and email channel setup and campaign authoring happen in the Engage module of the Product Workspace, not here.

How Engage works​

  you track events  ──►  unified profile  ──►  campaign trigger (panel)
                                                       │
                                                       ▼
                                    push / web push / custom channel send
                                                       │
                                     delivered to device / browser / your endpoint
                                                       │
                                    delivery + clicks tracked back to Binoban

A campaign is configured in the panel to fire on an audience or a tracked event. When it fires, Binoban sends on whichever channel the recipient is registered for. Delivery and click signals flow back as events, so Engage performance sits alongside the rest of your data.

Push is three steps, everywhere​

Push and web push are what you integrate, and the shape is identical on every platform:

  1. Initialize. Set up Firebase in your app or site, and initialize Binoban's notification layer.
  2. Register the token. Take the push token Firebase gives you and hand it to the Binoban SDK with one call.
  3. Forward the message. When a push arrives, hand it to the SDK. It displays the notification and reports delivery, clicks, and dismissals. On the web, Binoban's service worker is that handler, so this step is done for you once it is registered.

Why step 3 is not optional​

Binoban always sends data-only messages — never an FCM notification payload. So Firebase's automatic display never fires, and your handler or service worker always runs. That is deliberate: it is what makes tracking, action buttons, and custom data behave the same way across web, Android, and iOS. But it means nothing appears on screen unless the message reaches the Binoban SDK.

What you integrate​

Push — Android · iOS · React Native​

Initialize the notification layer, register the FCM token, and forward incoming messages from your FirebaseMessagingService (Android), your UNUserNotificationCenterDelegate (iOS), or your push library (React Native). The SDK displays the notification, tracks delivery and interactions, and — on Android — opens deep links for you.

→ App push

Web push — browser​

Register a service worker that loads Binoban's messaging script, get a token from Firebase with your VAPID key, and track it. From there the worker displays, tracks, and opens notifications on its own.

→ Web push

Firebase — the shared prerequisite​

Both paths run on Firebase Cloud Messaging. Binoban needs a send-only service account from your Firebase project; your apps need the usual Firebase setup plus a VAPID key for the web and an APNs key uploaded to Firebase for iOS.

→ Set up Firebase for Binoban push

Custom Channel — optional​

If your business configures an Engage Custom channel provider, Binoban will call an HTTP endpoint you own once per campaign send, so you can fan sends out through your own delivery system — an internal message centre, or a channel Binoban does not natively support. This is not push, and most integrations do not use it.

→ Custom Channel webhook contract

Keep events flowing​

Campaigns are only as good as the events behind them. The same identify and track calls that build your profiles are what Engage targets and triggers on — consistent, well-named events directly improve what you can message on.

What lives in the panel, not the SDK​

The SDKs do not create campaigns, manage message content, or configure providers. Business teams operate that in the Product Workspace:

  • Audiences and segments
  • Campaign channels, content, and templates
  • Triggers, journeys, timing, and A/B tests
  • Delivery and engagement reporting
  • The Firebase service-account credential and any Custom Channel provider

All of this is configured in the Engage module of the Product Workspace.

Next steps​

Last updated on