operations
Changelog
activeA chronological log of SDK, API, and docs changes.
A chronological log of SDK changes, newest first. For a narrative summary of what each release means for your integration, see Release notes.
Native SDK (Android & iOS)
1.0.0 — 2026-07-20
The first stable release. Begins Binoban's semantic-versioning commitment for the Native SDK.
Changed
apiHostis now required. It previously had a hardcoded internal default; a blankapiHostnow makes the configuration invalid, andBinoban.create(...)returns a disabled, no-op instance instead of silently reaching a stray host.- Transient upload failures (network errors,
429,5xx) are now retried with capped exponential backoff instead of being dropped; a batch is only dropped on a non-4294xx. - Queued events now persist in an app-private directory (Android
filesDir, iOS Application Support) instead of the OS temp directory. settings()now returns a non-blocking cached snapshot; usesettingsAsync()for a fresh fetch.
Added
Binoban.create(configuration)— a factory that never throws; on invalid configuration it returns a safe, disabled instance and reports the cause viaConfiguration.errorHandler.- iOS:
context.device.advertisingId/adTrackingEnabled(IDFA, only when ATT-authorized) andcontext.network.{wifi,cellular,bluetooth}. - iOS: a bundled
PrivacyInfo.xcprivacyprivacy manifest on every distributed framework slice. - Swift Package Manager as a second iOS distribution channel, alongside CocoaPods.
Removed
- Every previously deprecated API — the last opportunity to do so before the
semantic-versioning commitment takes effect. Most integrators need no code
change: the
Binoban(apiKey, sourceIdentifier) { … }factory and the event methods (track/identify/flush/reset, plus internalscreen/group/alias) are unchanged.
Web SDK
Planned
The Web SDK doesn't yet carry a public release version to changelog against (see the compatibility matrix). This section will be filled in once a public versioning scheme is confirmed.
React Native bridge
1.0.0 — released alongside the Native SDK 1.0.0, as a bridge over the same
core. No React Native–specific changes are documented separately yet.
Tracking API
2026-10-05: events need any workspace identifier
Changed
- Identify and Track calls, batches and CSV imports are accepted when they
carry at least one identifier from the workspace's identity strategy.
userIdandanonymousIdare no longer required on their own. See Limits & validation → Identifiers. - The error for a call with no identifier is
error.sdk.missing.identifier(waserror.sdk.missing.id). An empty string does not count. - One event without an identifier rejects the whole batch.
- Event CSV imports accept
context.traits.*andcontext.device.*identifier columns. See CSV import.
2026-09-01 — reserved property and trait names
Changed
- Every
contextfield is now stored as a queryable event attribute under a reservedcx_prefix —context.localeiscx_locale,context.page.urliscx_pageUrl. The wire format is unchanged: SDKs still sendcontext.locale. Segments and reports built on a context attribute keep working, but the name shown in the workspace picker has changed. - The plain context names (
locale,appName,pageUrl, and the rest) are now usable as your owntrackproperty names. Previously they collided with the system attribute of the same name, which could stop a brand-new event from registering at all. - A
trackproperty namedcx_*,eventName,eventTimeorreceiveTimeis now dropped from the call and logged; the rest of the call is processed normally. See Track → Reserved property names. - An
identifytrait nameduserId,anonymousId, one of the five*Reachableflags, or anything starting withct_is now dropped the same way. These were previously accepted and had no effect, so nothing that worked stops working — identity comes from the top-level field, and reachability is derived from the matching*OptIntrait. See Identify → Read-only traits.
No SDK release is required for any of this.
Docs changelog
- 2026-09-28: the Web SDK inline snippet is
SNIPPET_VERSION1.6.0. It now stubssponsoredAds,joinTraceandleaveTrace(27 methods, in loader order). Copy it again to queue those calls before the SDK loads; see Release notes. - 2026-09-01: the reserved-name rules are documented in one place for the
first time: the
cx_context namespace and the reservedtrackproperty andidentifytrait names (both new, above), plus the long-standingbb_system-event prefix, which was always reserved but had never been written down as a rule you must not break. See Limits & validation → Reserved names. - 2026-07-25: this page and the rest of the cross-cutting reference guides were filled in.