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.

On this page

Feature support by platform

FeatureiOSAndroidReact NativeFlutter
User identity (uid, email)0.1.00.1.00.1.00.1.0
Event tracking (auto + custom)0.1.00.1.00.1.00.1.0
Screen tracking0.1.00.1.00.1.00.1.0
Push notifications0.1.00.1.00.1.00.1.0
Rich push (images/GIF/video)0.1.00.1.00.1.00.1.0
Delivery tracking0.1.00.1.00.1.00.1.0
In-app messaging0.1.00.1.00.1.00.1.0
In-app email collection0.2.00.2.00.2.00.2.0
App inbox1.0.01.0.01.0.01.0.0
Structured logging (ZTLogger)1.0.01.0.01.0.01.0.0
Location tracking0.1.00.1.00.1.00.1.0
Opt-in / opt-out0.1.00.1.00.1.00.1.0
UCLID support0.2.00.2.00.2.00.2.0
Deeplink handling0.1.00.1.00.1.00.1.0
IDFA / IDFV support1.0.0N/A1.0.0 (iOS only)1.0.0 (iOS only)
GAID (Google Advertising ID)N/A0.1.00.1.0 (Android only)0.1.0 (Android only)
Privacy manifest (Apple)1.0.0N/AN/AN/A

Note: Version numbers indicate the first SDK version that introduced the feature. 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
1app_terminated is an iOS-only auto-tracked event. Android, React Native, and Flutter do not track app termination.
2Rich push on iOS requires a Notification Service Extension. On Android, rich push uses FCM data payloads and requires no additional extension.
3Push notifications on Android use Firebase Cloud Messaging (FCM). On iOS, the SDK communicates with Apple Push Notification service (APNs).
4IDFA and IDFV are iOS-only device identifiers. Android provides GAID (Google Advertising ID) and App Set ID instead.
5Delivery tracking on iOS requires the Notification Service Extension and an App Group. On Android, delivery tracking works without additional configuration.
6React 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