Stay organized with collectionsSave and categorize content based on your preferences.
Firebase provides tools in theFirebaseconsole to explore and analyze your
project's historical data. These tools can help you answer many questions about
how your apps are being used. Sometimes, though, you also want to set up your
own queries to answer your own questions.
You can do this by exporting your project data from Firebase intoBigQuery. WithBigQuery, you can analyze your data withBigQuerySQL or
export the data to use with your own tools.
You can configure Firebase to export data toBigQueryfrom the
following Firebase products:
To view or manage settings for data export toBigQuery, you must have
the required level of access.
If you don't have the necessary Firebase access, you can ask a Firebase
project Owner to assign you the applicable role via theFirebaseconsole IAM settings.
If you have questions about accessing your Firebase project,
including finding or assigning an Owner, review thePermissions and access to Firebase projects FAQs.
Project-level
The following table applies to the top-level linking of a Firebase project toBigQuery.
Action inFirebaseconsole
Required IAM permission
IAM role(s) that include required permissions by default
Follow the on-screen instructions to enable export toBigQuery.
What happens when you enable export?
You select the dataset location. After the dataset is created, the location
can't be changed, but you can copy the dataset to a different location
or manually move (recreate) the dataset in a different location. To learn
more, seeChange the location for existing exports.
This location is only applicable for the data exported intoBigQuery,
and it does not impact the location of data stored for use in theFirebaseconsole.
By default, all apps in your project are linked toBigQueryand
any apps that you later add to the project are automatically linked toBigQuery. You canmanage which apps send data.
Firebase exports a copy of your existing data toBigQuery. The
initial propagation of data for export may take up to 48 hours.
Firebase sets up daily syncs of your data toBigQuery.
After you link your project, you usually need to wait until the next day's
sync for your first set of data to be exported toBigQuery.
The daily sync happens once per day, regardless of any scheduled export
that you might have set up inBigQuery. Note that the timing and
duration of the sync job can change, so we don't recommend scheduling
downstream operations or jobs based on a specific timing of the export.
After you enable a product forBigQueryexport and create a dataset,
you can't change the location of that dataset. However, you can copy your
existing dataset to a new dataset that has a different location and reset your
data export to that new location. Learn aboutBigQuerydataset locations.
Select the product for which you want to change the location for data
export
Pricing and theBigQuerysandbox
If your Firebase project is on the no-cost Spark pricing plan, you can linkCrashlytics,Cloud Messaging,Google Analytics,
andPerformance Monitoringto theBigQuerysandbox,
which provides no-cost access toBigQuery. Refer toUsing theBigQuerysandboxfor information on theBigQuerysandbox's capabilities.
If your Firebase project is on the pay-as-you-go Blaze pricing plan, you can linkA/B Testing,Crashlytics,Cloud Messaging,Google Analytics,
andPerformance MonitoringtoBigQuery. Your use ofBigQueryis subject
to normalBigQuerypricing,
which includes limited no-cost use.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,[]]
