Integrations
FCM integrates tightly with Google Analytics for Firebase, which automatically tracks notification opens and can trigger sends based on Analytics-defined audiences -- a common pattern for re-engagement campaigns without building custom audience logic from scratch.
Implementation details
Firebase Remote Config and Firebase In-App Messaging are separate, related Firebase products often confused with FCM -- Remote Config changes app behavior/content without a notification, and In-App Messaging shows contextual messages inside an active app session, neither of which is push notification delivery. Server-side sending integrates via the Admin SDK (Node.js, Java, Python, Go, C#) or direct HTTP v1 REST calls, both requiring the same service-account OAuth2 authentication.
Actionable Considerations
- Use Analytics-defined audiences to trigger re-engagement sends rather than building custom audience segmentation logic separately.
- Distinguish FCM (push notifications) from Remote Config (app behavior/content changes) and In-App Messaging (in-session prompts) when scoping a requirement, since they're separate products.
- Use an official Admin SDK for your backend language over raw HTTP v1 calls where available, for simpler auth handling.