Push delivery involves both mobile registration and backend Firebase credentials. Complete Firebase setup on the target platform before configuring a production audience.
Sign into Perfex as an authorized administrator and open:
Configure the Firebase project ID and service-account JSON for the same project used by your mobile apps. The module documentation states that the credential JSON and FCM access token are stored encrypted using Perfex’s encryption library.
Keep the server’s encryption configuration backed up securely. Do not publish or place service-account credentials in the mobile source.
Launch the configured app, allow notifications, and sign in. The app synchronizes its FCM token through authenticated POST /notifications/device-token, including the platform and device identifier. Token refresh and app-resume handling keep the registration current.
Select one test contact and send a recognizable test message. Confirm delivery on the intended device, then repeat with the app in the background. Verify that signing out removes the old session’s registration before changing accounts.
The admin interface supports messages to registered customer devices and selected customer/contact audiences. Inspect the selected audience before sending broadly.
Push delivery and the app’s notification history are separate checks. Do not assume every push is stored as a history item or that every CRM event automatically sends a push.