Skip to main content
operations

Go-live Checklist

active
Audience: developerUpdated 2026-07-26

Everything to verify before sending production traffic.

Work through this in order; each step links to where it's covered in depth.

  1. Credentials issued for this environment. You have a real apiKey and sourceIdentifier from Binoban for the source you're going live with — not the placeholder values from a quickstart. See Authentication & setup.
  2. The host is set deliberately, not left on its default. This looks different per platform:
    • Native SDK / React Native — apiHost is required, with no fallback. Point it at api.binoban.io for cloud, or your tenant's host for on-prem/air-gapped. A blank value silently disables the SDK.
    • Web SDK — set host.apiPath explicitly. If you omit it, the SDK silently falls back to a build-time default baked into the bundle, which may not be your environment — exactly the kind of thing that must not reach production unnoticed. See On-prem.
  3. sourceIdentifier is the 12-character handle Binoban gave you — not something you generated yourself.
  4. A real identify/track call succeeds. Send one and confirm a 2xx response — not a 401 error.sdk.authorization.failed (bad apiKey) or 404 error.sdk.source.notFound (bad sourceIdentifier). See Error codes.
  5. Debug mode is off. Binoban.debug(false) (Web) / Binoban.debugLogsEnabled = false (Native, the default) before shipping. See Debug mode.
  6. SDK version is pinned, not tracking "latest" automatically — confirm the version against the compatibility matrix and pin it in your build.
  7. Identity strategy reviewed. Confirm how anonymousId and userId stitch together for your app, and that you call identify at the right moment. See Identity strategy.
  8. Consent wired, if applicable. If your deployment gates tracking on consent, confirm that path before go-live. The Consent API page is still a stub — coordinate directly with Binoban if you need specifics now.
Planned

Schema validation and rate/size-limit behavior beyond the field-length and batch-size limits already documented on the Tracking API page aren't fully cataloged yet — see Error codes for what's confirmed today.

Next steps​

Last updated on