Firebase Cloud Messaging (FCM) integration

Retainza sends push through your Firebase project, not one it owns. You paste a service-account JSON, Retainza verifies it with a test send and stores only an encrypted reference to it.

How it works

  1. 01

    Create a service account in your Firebase project with the Cloud Messaging role.

  2. 02

    Paste the service-account JSON into the connection form in your Retainza project.

  3. 03

    Retainza verifies the credential with a test send before saving it.

  4. 04

    Register device tokens from the client SDK and send your first campaign.

Read the docs

Questions

Does Retainza store my Firebase service account?

Not in plaintext. The credential goes to Secret Manager encrypted with a per-project KMS key using envelope encryption; the database holds only a reference to it.

How does Retainza handle dead device tokens?

Tokens that FCM reports as unregistered are pruned automatically, so your audience counts stay honest and you do not keep paying to send into the void.

How large a send can I do in one call?

Retainza batches through FCM's sendEach at up to 500 messages per call and throttles to stay inside your project's own quota.

Own your engagement stack today

Start free on the hosted dashboard. Your data, your credentials, your rules.

Start freeExplore the docs →