Firebase + Amplitude
Connect Firebase and Amplitude for Deeper Product Analytics
Sync your Firebase app data with Amplitude to turn raw events into user insights you can actually act on — no manual effort required.
Why integrate Firebase and Amplitude?
Firebase and Amplitude are two platforms most product teams can't live without. Firebase handles app backends — authentication, real-time databases, cloud functions. Amplitude tells you what users actually do inside those apps. Together, they should form a closed loop between what your app does and what your users experience. But that loop only works if the data flows reliably between them. Integrating Firebase with Amplitude on tray.ai lets your data engineering, product, and growth teams automate event tracking, user property syncing, and cohort analysis so you're acting on insights instead of babysitting pipelines.
Automate & integrate Firebase & Amplitude
Use case
Real-Time Event Forwarding from Firebase to Amplitude
Every time a user triggers a Firebase event — a purchase, an onboarding step, a feature interaction — tray.ai forwards that event to Amplitude with the correct schema and user identifiers. There's no waiting for nightly batch exports. Amplitude funnels and charts reflect live app behavior, so product managers can trust what they see in their dashboards.
Use case
Sync Firebase User Properties to Amplitude User Profiles
When a user's properties change in Firebase — subscription tier, geographic region, account age — tray.ai pushes those updates to the matching Amplitude user profile automatically. Your Amplitude cohorts stay accurate, and behavioral segmentation reflects the current user state. Marketing and growth teams can build audiences on up-to-date attributes without waiting on engineering to run manual syncs.
Use case
Trigger Firebase Cloud Functions Based on Amplitude Cohort Membership
When Amplitude identifies that a user has entered a cohort that warrants action — power users at churn risk, or users who hit a key activation milestone — tray.ai can trigger a Firebase Cloud Function to respond: send a push notification, update a user record, flip a feature flag. You get automated interventions without custom backend code connecting your analytics to your app.
Use case
Automated A/B Test Event Tracking and Analysis
Firebase Remote Config and A/B Testing generate experiment assignment events that you need in Amplitude to measure variant performance accurately. tray.ai captures experiment assignment data from Firebase and sends it to Amplitude as a user property or event, so your experiment analysis stays clean inside Amplitude's funnel and retention tools — no manual exports, no brittle custom integrations.
Use case
New User Registration Sync and Onboarding Funnel Tracking
When a new user registers via Firebase Authentication, tray.ai immediately creates a matching user identity in Amplitude and fires an onboarding start event. Every new user enters Amplitude's onboarding funnel from day one, giving product teams complete visibility into activation rates and drop-off points. No one falls through the cracks because of a sync delay or missed event.
Use case
Firestore Database Changes Translated into Amplitude Events
When records in your Firestore database are created or updated — a subscription activation, a support ticket resolution, a profile completion — tray.ai detects the change and translates it into an Amplitude event. Non-engineering teams can track backend product milestones without custom event instrumentation in the app client. Your Amplitude event taxonomy stays complete even for server-side actions.
Use case
Revenue and In-App Purchase Data Synchronization
Firebase records in-app purchase and subscription revenue events that need to flow into Amplitude for accurate LTV modeling and revenue analytics. tray.ai automates the mapping and forwarding of Firebase revenue events to Amplitude's revenue tracking fields, preserving product ID, price, quantity, and currency metadata. Finance and product teams get a consistent view of revenue inside Amplitude without reconciling data from multiple exports.
Get started with Firebase & Amplitude integration today
Firebase & Amplitude Challenges
What challenges are there when working with Firebase & Amplitude and how will using Tray.ai help?
Challenge
Maintaining Consistent User Identity Across Both Platforms
Firebase uses its own UID system for authentication while Amplitude tracks users by user ID and device ID. When these identifiers aren't mapped correctly, user journeys become fragmented in Amplitude — inflated user counts, broken funnels, inaccurate retention analysis. Managing this mapping manually at scale is complex and breaks in ways that are hard to detect.
How Tray.ai Can Help:
tray.ai provides a centralized mapping layer in every workflow where Firebase UIDs are translated to Amplitude user IDs before any event or property is sent. Configure the identity mapping once inside the tray.ai workflow and it applies universally, so you're not scattering identity logic across multiple integration points or maintaining custom code to keep it consistent.
Challenge
Handling High-Volume Event Streams Without Data Loss
Production Firebase apps can generate thousands of events per second during peak usage. Batch processing introduces latency, but naive real-time forwarding can overwhelm downstream APIs, trigger rate limit errors, and drop events in ways that silently corrupt your Amplitude analytics — often without any obvious warning.
How Tray.ai Can Help:
tray.ai's workflow engine handles high-concurrency event processing natively, with built-in retry logic and error handling to make sure every Firebase event reaches Amplitude. Workflows can be configured to respect Amplitude's API rate limits and queue bursts gracefully, so high-traffic periods don't result in data loss or gaps in your analytics.
Challenge
Transforming Firebase Event Schemas to Match Amplitude's Data Model
Firebase events and Firestore documents follow a schema that rarely maps cleanly to Amplitude's expected event property structure. Without careful transformation logic, Amplitude ends up receiving raw Firebase payloads that pollute your event taxonomy, break existing charts, and require expensive retroactive cleanup.
How Tray.ai Can Help:
tray.ai's built-in data transformation tools let you visually map, rename, filter, and reformat Firebase fields before they reach Amplitude. Define transformation rules per event type, apply conditional logic for different Firebase collections, and validate payloads before sending — all without writing custom ETL scripts.
Challenge
Keeping Historical Firebase Data Backfilled in Amplitude
Teams migrating to Amplitude or expanding analytics coverage often need months of historical Firebase event data in Amplitude to establish meaningful baselines and retention curves. Doing this manually takes significant engineering effort and risks ingesting duplicate or malformed historical records.
How Tray.ai Can Help:
tray.ai supports scheduled bulk workflows that page through historical Firebase Firestore or Realtime Database records, transform them to the correct Amplitude schema, and send them via Amplitude's Batch API in controlled volumes. Teams can backfill historical data safely and incrementally without overwhelming Amplitude's ingestion pipeline or interfering with live event processing.
Challenge
Ensuring Data Privacy and PII Compliance Across Both Platforms
Firebase stores user authentication details and potentially sensitive profile data that shouldn't reach Amplitude in raw form. Without careful filtering, personally identifiable information — email addresses, phone numbers, precise location data — can end up in Amplitude in violation of GDPR, CCPA, or your own internal data governance policies.
How Tray.ai Can Help:
tray.ai lets you build PII scrubbing and field exclusion logic directly into each Firebase-to-Amplitude workflow. Before any payload reaches Amplitude, sensitive fields can be removed, hashed, or replaced with pseudonymous identifiers. Compliance and legal teams can trust that data governance rules are enforced at the integration layer, not left to manual review downstream.
Start using our pre-built Firebase & Amplitude templates today
Start from scratch or use one of our pre-built Firebase & Amplitude templates to quickly solve your most common use cases.
Firebase & Amplitude Templates
Find pre-built Firebase & Amplitude solutions for common use cases
Template
Firebase Event to Amplitude Event Forwarder
This template listens for specified Firebase Realtime Database or Firestore write events and automatically sends a formatted event to Amplitude, mapping Firebase fields to the correct Amplitude event properties and user ID fields.
Steps:
- Trigger on a new Firebase Firestore document write or Realtime Database update matching a specified path
- Transform the Firebase event payload, mapping fields to Amplitude's expected event schema including event type, user ID, device ID, and event properties
- Send the formatted event to Amplitude's HTTP API v2 endpoint and log the response for monitoring
Connectors Used: Firebase, Amplitude
Template
Firebase New User to Amplitude Identity Creation
This template triggers whenever a new user registers in Firebase Authentication, automatically creating or updating the corresponding user identity in Amplitude with initial user properties such as registration date, sign-up method, and platform.
Steps:
- Trigger on a new Firebase Authentication user creation event
- Extract user metadata including UID, email, sign-up provider, and creation timestamp from the Firebase payload
- Call the Amplitude Identify API to create the user profile and set initial user properties, then fire a registration event to begin onboarding funnel tracking
Connectors Used: Firebase, Amplitude
Template
Firestore User Property Change to Amplitude User Profile Sync
This template monitors a specified Firestore user collection for document updates and automatically pushes changed user properties to the matching Amplitude user profile, keeping segmentation data current across both platforms.
Steps:
- Trigger on a Firestore document update within the designated user profile collection
- Compare previous and current document snapshots to identify changed fields relevant to Amplitude user properties
- Call the Amplitude Identify API to update only the changed user properties on the matching user profile using the Firebase UID as the user identifier
Connectors Used: Firebase, Amplitude
Template
Amplitude Cohort Webhook to Firebase Cloud Function Trigger
This template receives an Amplitude behavioral cohort webhook and triggers a Firebase Cloud Function, enabling automated product actions — push notifications, feature flag updates, user record changes — based on cohort membership signals.
Steps:
- Receive an inbound webhook from Amplitude when a user enters or exits a specified behavioral cohort
- Parse the cohort payload to extract user identifiers and cohort membership status
- Call the designated Firebase Cloud Function HTTP endpoint with the user ID and action parameters to trigger the appropriate in-app or backend response
Connectors Used: Amplitude, Firebase
Template
Firebase In-App Purchase Revenue Event to Amplitude Revenue Tracking
This template captures Firebase in-app purchase events and forwards them to Amplitude's revenue tracking API with full product metadata, keeping LTV reporting and revenue analytics consistent across both platforms.
Steps:
- Trigger on a Firebase Firestore purchase record creation or a Realtime Database revenue event write
- Map Firebase purchase fields including product ID, price, currency, and quantity to Amplitude's revenue event schema
- Send the revenue event to Amplitude's HTTP API and verify successful ingestion, flagging any schema mismatches for review
Connectors Used: Firebase, Amplitude
Template
Firebase A/B Test Assignment to Amplitude User Property Sync
This template automatically captures Firebase Remote Config experiment assignments and syncs them to Amplitude as user properties, enabling clean experiment analysis inside Amplitude's funnel, retention, and behavioral analytics tools.
Steps:
- Trigger on a Firebase Remote Config parameter fetch or experiment assignment log entry for a specified experiment ID
- Extract the experiment name, variant assigned, and user identifier from the Firebase payload
- Call the Amplitude Identify API to set the experiment variant as a user property, then optionally fire an experiment exposure event to Amplitude for funnel analysis
Connectors Used: Firebase, Amplitude