01
Signups and activation
Count signups, activations and retention straight from your user tables, with definitions you certify once.
D7 activation
Databases
Firebase + Kimo
Firestore collections and Auth users. Replicate your production tables read-only and join them with every other tool, without touching your app.
- Auth
- OAuth 2.0
- Sync
- Hourly
- Setup
- ≈ 2 min
Live demo workspace with fictional data · no signup, no credentials needed
kimo / connectors / firebaseSyncing
Sync loghourly
- Succeeded:users+879 rowsnow
- Succeeded:events+1,660 rows2m ago
- Succeeded:orders+1,717 rows4m ago
- Succeeded:users+98 rows6m ago
Rows synced · 30 days
80.7M
Workspaces
9%
What you can do
What teams build with Firebase
Firebase on its own answers half the question. Joined with the rest of your stack in Kimo, it answers the other half.
02
Join product data with tools
Link your users to Stripe customers, CRM contacts and ad clicks through shared keys.
users ⋈ subscriptions
03
Ask questions in plain English
Ask Kimo “how many trials converted last week by plan?” and get the SQL, the chart and the answer.
Ask Kimo
Objects & tables
Exactly what gets synced
Kimo maps Firebase into clean, typed tables with primary keys and incremental cursors, so syncs stay fast and joins just work.
3 tables · 15 fields
Tables
users
Incremental≈ 41,400,000 rows| Field | Type | Notes |
|---|---|---|
| id | id | Primary key |
| string | ||
| plan | enum | Low-cardinality dimension |
| created_at | timestamp | Incremental cursor |
| country | string |
Custom fields and extra objects are discovered automatically on each sync. Row counts are illustrative.
Sample model
From raw Firebase tables to a certified metric
A starter model Kimo suggests the moment Firebase is connected. Every join is editable.
Firebase · Product activation
Users and events joined with subscriptions to follow signup → activation → paid.
- Firebaseusers
- Stripesubscriptions
- HubSpotcontacts
Model
users.id · customer_id
Measuressignupsactivated
Signups · last 30 days
169+0.0% wk/wk
Fictional data · hover the chart for daily values
Setup
Connect Firebase in 2 min
No engineers, no pipelines to maintain. Kimo asks for the minimum access it needs and tells you exactly what it will read.
- 1
Click “Connect Firebase”
You are redirected to Firebase to sign in. Kimo never sees your password.
- 2
Approve read-only scopes
Kimo requests the narrowest scopes available. You can revoke access at any time.
- 3
Pick accounts
Choose which accounts to sync. Add more later without reconnecting.
- 4
First sync and schema mapping
Kimo backfills history, maps users and suggests joins with your other sources.
Read-only, encrypted, revocable. Credentials are encrypted with a per-workspace key, never logged, and can be rotated without breaking your models.
Connect Firebase
Step 2 of 3 · Kimo demo workspace
Kimo wants read-only access to your Firebase account
read-only accessread
Accounts
- Northwind · Firebase
- Northwind EU · Firebase
Read-only access
Illustration only · placeholder values, never real secrets
Works great with
Pair Firebase with the rest of your stack
Kimo suggests these joins automatically when both sources are connected.
FAQ
Firebase questions, answered
By default Kimo syncs Firebase hourly. You can change the schedule per table, or trigger a sync manually from the connector page.
Firebase · OAuth 2.0 · Hourly
See your Firebase data in Kimo in 2 min.
Try it on the live demo workspace first, then connect your own account when you are ready.