Flutter push notifications
Contents
Set up Workflows push notifications in the Flutter SDK. For the concept and channel setup, see Push notifications.
Available in the Flutter SDK version 5.35.0 and newer. Not supported on Flutter Web or macOS.
Requirements
Configure push in your app as usual (for example with firebase_messaging) and request notification permission from the user.
Automatic registration and open tracking (default)
Both behaviors are on by default. An app that already has push configured starts sending its device token to PostHog after upgrading, with no code change:
On iOS the native SDK hooks the app delegate's remote-notification registration callback, so it picks up the APNs token once your app registers for remote notifications. On Android it fetches the FCM token at startup when firebase-messaging is on the classpath. The token is registered under the current distinct ID, so it follows the user across identify().
Open coverage differs per platform. On iOS every tap on a remote notification is captured whatever the app state; locally-scheduled notifications are ignored. On Android only cold-start taps are captured. Capture the rest manually (below).
The Android startup fetch doesn't see later token refreshes, so forward those yourself to keep the registered token current:
Manual registration
If you manage push tokens yourself, turn the automatic flags off and call the SDK directly:
Call this only after setup() has completed; a token registered earlier is silently dropped.
Unregister the token when a user signs out so it isn't left bound to them:
Calling Posthog().reset() on logout already moves the registered token to the new anonymous identity, so this is only needed when you manage subscriptions yourself.
Registration and unregistration are durable. If the device is offline or the request fails, the SDK retries on the next flush, identity change, or app launch.
Capturing opens
For the opens automatic capture misses (locally-scheduled notifications on either platform, plus warm-start taps and foreground messages on Android), call the manual API:
Only call it for opens automatic capture can't see itself, or the tap is counted twice.
The $push_notification_opened event includes $notification_title and $notification_body (plus $notification_subtitle on iOS), and $notification_action for action-button taps. Notification content is only captured for notifications sent by PostHog. Opens of other notifications are still captured, but without title or body.
Opting out
Set capturePushNotificationSubscriptions: false or capturePushNotificationOpened: false on PostHogConfig before setup().
If your app initializes the SDK natively via com.posthog.posthog.AUTO_INIT, the Dart config doesn't apply because the native SDK is already set up before any Dart runs. Opt out with the com.posthog.posthog.CAPTURE_PUSH_NOTIFICATION_SUBSCRIPTIONS and com.posthog.posthog.CAPTURE_PUSH_NOTIFICATION_OPENED keys instead, in Info.plist on iOS and as AndroidManifest <meta-data> on Android.
Identity verification
If your push channel requires identity verification, supply a backend-minted token through pushIdentityProvider:
pushIdentityProvider is a Dart callback with no Info.plist or manifest equivalent. If your app uses com.posthog.posthog.AUTO_INIT, set it to false and call Posthog().setup() explicitly, otherwise the provider is never installed.
Troubleshooting
| Issue | Check |
|---|---|
| Token never registers | Confirm push is set up in your app and the user granted notification permission. On Android, confirm firebase-messaging is on the classpath (firebase_messaging sets this up). Any manual registerPushNotificationToken call must come after setup() completes. |
| Push doesn't arrive | Confirm the channel's Firebase project (Android) or APNs environment and bundle id (iOS) match your app. |
| Registration rejected on a Required channel | Your pushIdentityProvider isn't returning a valid token in time. See Identity verification. |