Features by platform
Feature availability and platform-specific notes for all Zeta mobile SDKs.
Each cell shows the SDK version that first introduced the feature, or its availability status where a version does not apply.
On this page
Feature support by platform
The tables below group features by the stage of the integration journey where you typically reach for them, from core integration through release preparation.
Integrate core features
| Feature | iOS | Android | React Native | Flutter |
|---|---|---|---|---|
| UCLID support | 0.2.0 | 0.2.0 | 0.2.0 | 0.2.0 |
| User identity (uid, email) | 0.1.0 | 0.1.0 | 0.1.0 | 0.1.0 |
| Event tracking (auto + custom) (Note 1) | 0.1.0 | 0.1.0 | 0.1.0 | 0.1.0 |
| Screen tracking | 0.1.0 | 0.1.0 | 0.1.0 | 0.1.0 |
| Location tracking | 0.1.0 | 0.1.0 | 0.1.0 | 0.1.0 |
| Opt-in / opt-out | 0.1.0 | 0.1.0 | 0.1.0 | 0.1.0 |
Add messaging channels
| Feature | iOS | Android | React Native | Flutter |
|---|---|---|---|---|
| App inbox | 1.0.0 | 1.0.0 | Coming soon | Coming soon |
| In-app email collection | 0.2.0 | 0.2.0 | 0.2.0 | 0.2.0 |
| Push notifications (Note 3) | 0.1.0 | 0.1.0 | 0.1.0 | 0.1.0 |
| Rich push (images/GIF/video) (Note 2) | 0.1.0 | 0.1.0 | 0.1.0 | 0.1.0 |
| Delivery tracking (Note 5) | 0.1.0 | 0.1.0 | 0.1.0 | 0.1.0 |
| In-app messaging | 0.1.0 | 0.1.0 | 0.1.0 | 0.1.0 |
| Deeplink handling | 0.1.0 | 0.1.0 | 0.1.0 | 0.1.0 |
Prepare for release
| Feature | iOS | Android | React Native | Flutter |
|---|---|---|---|---|
| Structured logging (ZTLogger) | 1.0.0 | 1.0.0 | Coming soon | Coming soon |
| Privacy manifest (Apple) | 1.0.0 | N/A | N/A | N/A |
| IDFA / IDFV support (Note 4) | 1.0.0 | N/A | 0.1.0 (iOS only) | 0.1.0 (iOS only) |
| GAID (Google Advertising ID) | N/A | 0.1.0 | 0.1.0 (Android only) | 0.1.0 (Android only) |
Note: A version number is the SDK release that first introduced the feature.
N/Ameans the feature does not apply to that platform;Coming soonmeans it is planned but not yet released. React Native and Flutter SDKs wrap the native iOS and Android SDKs -- feature availability on each platform depends on the underlying native SDK version.
Platform-specific notes
| # | Note |
|---|---|
| 1 | app_terminated is an iOS-only auto-tracked event. Android, React Native, and Flutter do not track app termination. |
| 2 | Rich push on iOS requires a Notification Service Extension. On Android, rich push uses FCM data payloads and requires no additional extension. |
| 3 | Push notifications on Android use Firebase Cloud Messaging (FCM). On iOS, the SDK communicates with Apple Push Notification service (APNs). |
| 4 | IDFA and IDFV are iOS-only device identifiers. Android provides GAID (Google Advertising ID) and App Set ID instead. |
| 5 | Delivery tracking on iOS requires the Notification Service Extension and an App Group. On Android, delivery tracking works without additional configuration. |
| 6 | React Native and Flutter SDKs bridge into the native iOS and Android SDKs. Platform-specific setup (e.g., APNs certificates, FCM credentials) is still required on each side. |
See also
- User identity and properties -- how ZMP identifies users across platforms.
- Event model -- auto-tracked events, custom events, screen tracking.
- Versioning & support (iOS) -- iOS SDK version policy.
- Versioning & support (Android) -- Android SDK version policy.
- Versioning & support (React Native) -- React Native SDK version policy.

