Connect a customer-owned Firebase project
- Open Settings > Channels > Push > Mobile apps as a workspace owner or admin.
- Enter the exact Firebase project ID and at least one Android package name or iOS bundle ID.
- Create a dedicated Firebase service account with only the permission needed for FCM HTTP v1 sending, then paste its JSON into the protected setup form.
- For iOS, configure your APNs authentication key inside that customer-owned Firebase project. Do not send the APNs key to Wepy.
- Store the one-time Wepy identity-signing secret in approved backend secret storage and acknowledge the backup before leaving setup.
- Have your developer connect signed registration, then ask for notification permission from a clear in-app action. Current Android and iOS apps use manual register() callbacks and enroll the Firebase Installation ID with fcmTargetType FID. REGISTRATION_TOKEN is legacy compatibility only for already-shipped clients.
- Create a pairing code on that exact device, enter it in Wepy, and send a controlled test. The first FCM-accepted test activates campaign sending.
Your Firebase project stays yours
Use your own Firebase project and service account. Your business keeps control of its Android/iOS apps, Firebase usage, and provider billing. Wepy protects the saved credential and does not reveal its secret values after setup.
A real test completes setup
A new connection stays Needs attention until FCM accepts a notification sent to a paired test device. Saving or checking credentials alone does not complete setup. FCM acceptance confirms the request was accepted, not that the notification appeared on screen; check the test device too.
Work with your developer to connect the app
- Explain notifications before requesting permission. Save how the person opted in. Existing operating-system permission does not allow your app to restore a Wepy marketing opt-in without fresh consent.
- Have the authenticated customer backend mint a five-minute, one-use enrollment assertion bound to publicAppId, platform, fcmTargetType, the exact registration-identifier hash, iat, exp, and jti. Never put the identity-signing secret in the app binary.
- Android integrations use Firebase Messaging 25.1.2 or newer. Disable auto-init in the manifest and again at runtime, keep Firebase Analytics collection off before consent, enable installation-ID mode, and declare WepyMessagingService for com.google.firebase.MESSAGING_EVENT. Securely save every onRegistered()/onUnregistered() update, even repeated FIDs, and process registration and opt-out changes in order through WorkManager. Submit the Firebase Installation ID with fcmTargetType FID.
- iOS integrations use Firebase Messaging 12.18.0 or newer. Set FirebaseMessagingAutoInitEnabled to NO and FirebaseMessagingInstallationIdEnabled to YES in Info.plist. On each startup, disable auto-init before assigning MessagingDelegate and keep UIKit/Firebase access on MainActor. Save every didReceiveRegistration update securely with Keychain, including repeated FIDs, and process updates in order with safe cancellation when background time expires. Submit a valid FID with fcmTargetType FID.
- Legacy compatibility only: already-shipped iOS or older Android clients may continue submitting an opaque FCM registration token with fcmTargetType REGISTRATION_TOKEN. New Android and iOS integrations must use FID.
- Store the installation ID and revocation capability in encrypted transactional storage, together with a monotonically increasing consentEpoch and Firebase identifier version (fidVersion). Reuse the capability when Firebase replaces the identifier. Set EXISTING_PERMISSION and topicIds from saved permission evidence, not merely from the presence of a capability.
- Before sending, save each exact registration request body, stable idempotency key, consentEpoch, and fidVersion together. Keep that request immutable while its outcome is uncertain; retry the same request and key after a lost response. Replace an expired assertion only after Wepy confirms that the earlier request did not complete. Accept the returned capability only in an atomic transaction that rechecks consentEpoch and fidVersion against the saved request. If either version changed, save the returned capability for revocation instead of activating it. Comparing only the current consent value or identifier is not enough: a person may have opted out and back in while the request was pending.
- Persist OPT_OUT_PENDING and increment consentEpoch before any opt-out network request; keep Firebase auto-init disabled. Resolve any uncertain registration and revoke every known Wepy capability before treating Wepy unsubscribe as complete. Once Wepy confirms revocation, atomically clear the capability, persist OPTED_OUT, and record pending Firebase cleanup. Track Firebase cleanup separately. Firebase does not provide a typed already-unregistered error, so do not treat an unknown error as success or automatically retry cleanup whose outcome is uncertain. Have your developer investigate those cases; safely retry pending Wepy cleanup when the app restarts.
- Use a separate installation-bound identity assertion after sign-in. Call detach before logout or account switching so the shared device cannot receive the previous customer's personalized content.
- Send explicit unsubscribe, topic changes, display/open/click events, and conversion events through their purpose-limited native endpoints with a stable idempotency key.
- Treat an Invalid or Expired installation as local to that device. Another reachable browser or mobile installation for the contact can remain subscribed.
Private device details stay hidden
Contact profiles show the app, platform, subscription status, permission, and last activity. Web and Mobile Push reach are listed separately and together. Firebase registration identifiers, revocation capabilities, event tokens, service-account keys, and device fingerprints stay hidden.
Use the unified Push workflow
- Create or reuse one Push template with title, body, destination, optional rich media, and explicit personalization fallbacks. Web Push can also use dynamic action buttons; Mobile Push currently uses the main notification tap.
- Select a ready Web or Mobile app in the campaign sender step. Topics are scoped to that application and include only contacts who explicitly opted in.
- Optionally add A/B variants, a collapse key, quiet hours, a cross-channel frequency cap, or a recommended send time when enough engagement history is available. Browser icon URLs and renotify are Web Push-only; Mobile Push uses its installed app icon and Normal or High urgency.
- Send the exact saved draft to your paired test device, review reachable contacts and exclusions, then send now or schedule.
- Reuse the saved campaign in an Automation. Wepy freezes the app, topic, target, content, and delivery policy and rechecks current consent and reachability at execution time.
- Read Results as targeted, excluded, provider accepted, signed presentation callback, opened/clicked, and conversion. For Web Push, the presentation callback means showNotification() resolved even though operating-system settings may suppress visible UI. Mobile integrations report it only when presentation can be directly confirmed. The callback is not proof that a person saw the notification; a signed click is human-interaction proof. Never read provider acceptance as delivered.
When recommended timing is available
Recommended timing uses recent Web and Mobile Push engagement only when there is enough history. Otherwise Wepy uses the normal send time. Each contact stays in the same A/B variant across retries and all of their devices.
Rotate or pause safely
Rotate Firebase credentials deliberately
Update Firebase credentials from the Mobile Push application's settings, not generic Sending accounts. If the response is interrupted, retry the same action; existing app and device connections are preserved. Revoke the previous Google credential only after the new one is saved and a test notification succeeds.
Pausing still allows unsubscribe and logout
Identity-signing-secret rotation returns the new value once and keeps the previous value valid for the exact 24-hour overlap shown by Wepy. Pausing stops registration, tests, campaigns, and automations, but privacy cleanup remains available so an installed app can still unsubscribe or detach.