You’ve shipped a feature and want to tell the Firebase users who can use it. Their email addresses live in Authentication. Their plan and email preferences live in Firestore. Exporting the addresses gives you only part of the audience.

Rowsend can read Firebase Auth users with a read-only service-account key and add fields from a Firestore collection. You choose the audience from that synced data, then send through your own email provider. You don’t need a CSV export or a signup webhook for this workflow.

This guide walks through a first product update, including a profile document and audience rules you can adapt. Keep password resets and verification emails in your application’s authentication flow. Those serve a different purpose from a marketing campaign.

What changes when you stop exporting

Firebase’s CLI supports exporting accounts as CSV or JSON. That file is a snapshot. New signups, changed addresses and deleted accounts require another export if you want an up-to-date list. Plan and preference fields in Firestore need a separate join.

An Auth export can also contain password hashes and salts. Treat it as an account export, and keep those fields out of marketing tools.

With Rowsend, Firebase remains the source of contacts. Rowsend keeps a copy on your computer and refreshes it while the app runs. There is no CSV import or manual contact entry. Users without email addresses, such as phone-only users, don’t become contacts.

A connection doesn’t decide who should receive marketing. A verified address tells you about the address, not whether its owner wants your announcement. Bring your app’s recorded email preferences into the audience too.

Connect with a read-only service account

Create a dedicated service account in your Firebase project’s Google Cloud console. Give it Firebase Authentication Viewer. If you want Firestore profile fields, also give it Cloud Datastore Viewer. Avoid adding write roles to this account.

Under the service account’s Keys tab, choose Add key → Create new key, select JSON, and download the file. Google’s key creation instructions cover the console steps. If your organization blocks service-account keys, resolve that with your administrator before continuing.

In Rowsend:

  1. Open the project for your product.
  2. In Contacts, click Connect a database and choose Firebase.
  3. Click Choose key file and select the downloaded JSON file.
  4. Check that the displayed Firebase project is the one you intend to email.
  5. Add Firestore fields if needed, then click Test and connect.

Rowsend stores its saved key on your computer, encrypted with your system keychain. Before connecting, it checks that the account cannot write to Auth and, if selected, the profile collection. It refuses a key that can make changes. The Firebase setup guide explains the permission check and connection details.

Auth-only connections work without a Firestore collection. For the example below, connect the collection before building the audience.

Match Firestore profiles to Auth users by uid

Suppose a fictional project-management app has added a team dashboard for Pro customers. Its profiles collection has one document per user, with the document id equal to that user’s Firebase Auth uid.

For an Auth user whose uid is example-user-42, the document is profiles/example-user-42. Its example fields are:

{
"plan": "pro",
"product_updates_opt_in": true,
"is_internal": false
}

These are fields the fictional app maintains. Firebase Auth does not supply them. The app should update product_updates_opt_in when the user changes that preference, and the value should reflect any existing opt-out you need to honor.

In the connection dialog, enable Add fields from a Firestore collection, choose profiles, and tick those three fields. Rowsend reads this collection from the project’s default Firestore database. It matches documents by uid, not by email address. A collection with randomly generated document ids will not match the users just because each document contains their email.

Rowsend still syncs an Auth user with an email address if their profile document is missing. The selected profile fields will be empty. Use an explicit positive preference rule so missing profiles stay outside this campaign.

You can change the selected fields later through Project settings → Database → Edit fields.

Check the fields before saving an audience

Rowsend reads the Auth user’s email, display name, signup time and last sign-in time. It also supplies two custom fields:

Field Meaning
email_verified Whether Firebase marks the address verified
disabled Whether the Auth account is disabled

Use email_verified for a verification filter. Firebase provides a yes/no value here, so Rowsend does not invent an email-confirmation date.

Check a known Pro user against their Auth record and profile document. Then check someone who opted out, a disabled user, and someone without a profile. The segments guide explains the available conditions and how missing fields behave.

For the fictional dashboard announcement, save a segment named Pro product updates with All of these conditions:

  • plan is pro
  • product_updates_opt_in is yes
  • email_verified is yes
  • disabled is no

Save an exclusion segment named Internal accounts with is_internal is yes. In the campaign’s audience controls, include Pro product updates and exclude Internal accounts. Select the include segment explicitly. Leaving the include list empty starts with every contact.

Choose a suitable campaign topic, such as Product updates. Rowsend also excludes contacts who unsubscribed from that topic or everything, bounced, or complained. Syncing Firebase does not undo those suppressions. Your Firestore preference rule and Rowsend’s suppression records both affect eligibility.

Refresh the audience before the send

Firebase syncs work differently from a SQL connection with a last-changed column. Each Rowsend sync rereads every Auth user. If you selected a Firestore collection, it rereads that collection too. This catches name, address and profile changes without relying on an Auth update timestamp.

Rowsend syncs at startup and every 15 minutes by default while running. You can change that interval or use Sync now on the Contacts page. Larger projects take longer to reread. Check that the sync completed before reviewing the recipient count. The syncing guide covers intervals and recent sync results.

For ordinary scheduled sends, Rowsend resolves recipients when sending starts, using the data it has synced by then. If you enable sending with the computer off, Rowsend freezes and uploads the recipients when you schedule instead. Neither path queries Firebase live for each recipient. Refresh before scheduling, and review the sending requirements for the mode you choose.

Send a test of one useful announcement

Here is a fictional message for the dashboard release:

Subject: Your team’s work, on one dashboard

Preview: See active projects and overdue tasks together on Pro.

Your Pro workspace now has a team dashboard. Open Dashboard to see active projects and overdue tasks together, then choose a project to review its tasks.

Button: Open your dashboard

Replace the product behavior and button destination with your own. Connect your sending provider, then use Send test to check the sender, reply-to address, subject, mobile layout and destination in your inbox.

Check the companion mode before the real send. With Rowsend Cloud or a self-hosted companion, recipients get unsubscribe links and preference pages. With the companion on your computer, recipients reply to unsubscribe and you record their choice. Local sending needs the computer awake and Rowsend running.

Follow the sending guide for the final dialog and scheduling requirements. Before confirming, verify that a known eligible user appears, an opted-out user stays excluded, and the final count matches the audience you intended to reach.