Blog Studio Go to console

    Export project data to BigQuery

    Firebase provides tools in the Firebase console 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 into BigQuery . With BigQuery , you can analyze your data with BigQuery SQL or export the data to use with your own tools.

    You can configure Firebase to export data to BigQuery from the following Firebase products:

    Required permissions and suggested roles

    To view or manage settings for data export to BigQuery , 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 the Firebase console IAM settings . If you have questions about accessing your Firebase project, including finding or assigning an Owner, review the Permissions and access to Firebase projects FAQs .

    Project-level

    The following table applies to the top-level linking of a Firebase project to BigQuery .

    Action in Firebase console
    Required IAM permission
    IAM role(s) that include required permissions by default
    Additional required roles
    Link a Firebase project and BigQuery
    firebase.links.create
    none
    Unlink a Firebase project and BigQuery
    firebase.links.delete
    none
    View the existing links for BigQuery
    firebase.links.list
    none

    Google Analytics

    The following table applies specifically to the export of Google Analytics data to BigQuery .

    Action in Firebase console
    Required IAM permission
    IAM role(s) that include required permissions by default
    Additional required roles
    Enable export of Google Analytics data to BigQuery
    firebase.links.update
    AND
    serviceusage.services.enable
    AND
    resourcemanager.projects.getIamPolicy
    AND
    resourcemanager.projects.setIamPolicy
    Enable export for specific Firebase apps
    firebase.links.update
    Disable export for specific Firebase apps
    firebase.links.update

    Firebase products

    The following table applies to any of the Firebase products for which you can export data to BigQuery , for example, Crashlytics or Performance Monitoring .

    Action in Firebase console
    Required IAM permission
    IAM role(s) that include required permissions by default
    Additional required roles
    Enable export of a product's data to BigQuery
    firebase.links.update
    none
    Enable export for specific Firebase apps
    firebase.links.update
    none
    Disable export for specific Firebase apps
    firebase.links.update
    none

    Enable export to BigQuery

    1. In the Firebase console, go to the Integrationspage .

    2. In the BigQuery card, click Link.

    3. Follow the on-screen instructions to enable export to BigQuery .

    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, see Change the location for existing exports .

      This location is only applicable for the data exported into BigQuery , and it does not impact the location of data stored for use in the Firebase console.

    • By default, all apps in your project are linked to BigQuery and any apps that you later add to the project are automatically linked to BigQuery . You can manage which apps send data .

    • Firebase exports a copy of your existing data to BigQuery . The initial propagation of data for export may take up to 48 hours.

    • Firebase sets up daily syncs of your data to BigQuery .

      • 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 to BigQuery .

      • The daily sync happens once per day, regardless of any scheduled export that you might have set up in BigQuery . 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.

    To deactivate exports to BigQuery , unlink your project in the Firebase console.

    Change the location for existing exports

    After you enable a product for BigQuery export 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 about BigQuery dataset locations .

    Select the product for which you want to change the location for data export

    Google Analytics

    To change the location of an existing Google Analytics export to BigQuery , follow these instructions:

    1. In the Firebase console, go to the Integrationspage . Then do the following:

      1. In the BigQuery card, click Manage.
      2. Toggle off the Google Analytics slider to disable BigQuery .

    2. In the Google Cloud console, go to the BigQuery page . Then do the following:

      1. Create a temporary dataset to store a copy of the existing data from your original dataset. Assign the temporary dataset a different name than the name of the original dataset.
      2. Copy or move the data from your original dataset to the temporary dataset.
      3. Delete the original dataset.
      4. Create a new, permanent dataset with the same name as your original dataset ( analytics_ ANALYTICS_PROPERTY_ID ), then select the new region.
      5. Copy or move the data from the temporary dataset to the new dataset, then delete the temporary dataset.

    3. Go back to the Firebase console and the BigQuery card . Then do the following:

      1. Toggle on the Google Analytics slider to re-enable the BigQuery integration.
      2. Select the apps for which you want to enable the export.

    Cloud Messaging

    To change the location of an existing Cloud Messaging export to BigQuery , follow these instructions:

    1. In the Firebase console, go to the Integrationspage . Then do the following:

      1. In the BigQuery card, click Manage.
      2. Toggle off the Cloud Messaging slider to disable BigQuery .

    2. In the Google Cloud console, go to the BigQuery page . Then do the following:

      1. Create a temporary dataset to store a copy of the existing data from your original dataset. Assign the temporary dataset a different name than the name of the original dataset.
      2. Copy or move the data from your original dataset to the temporary dataset.
      3. Delete the original dataset.
      4. Create a new, permanent dataset with the same name as your original dataset ( firebase_messaging ), then select the new region.
      5. Copy or move the data from the temporary dataset to the new dataset, then delete the temporary dataset.

    3. Go back to the Firebase console and the BigQuery card . Then do the following:

      1. Toggle on the Cloud Messaging slider to re-enable the BigQuery integration.
      2. Select the apps for which you want to enable the export.

    4. Go back to the Google Cloud console and the BigQuery page to verify that a transfer configuration is created for Cloud Messaging in the new region.

    Crashlytics

    To change the location of an existing Crashlytics export to BigQuery , follow these instructions:

    1. In the Firebase console, go to the Integrationspage . Then do the following:

      1. In the BigQuery card, click Manage.
      2. Toggle off the Crashlytics slider to disable BigQuery .

    2. In the Google Cloud console, go to the BigQuery page . Then do the following:

      1. Create a temporary dataset to store a copy of the existing data from your original dataset. Assign the temporary dataset a different name than the name of the original dataset.
      2. Copy or move the data from your original dataset to the temporary dataset.
      3. Delete the original dataset.
      4. Create a new, permanent dataset with the same name as your original dataset ( firebase_crashlytics ), then select the new region.
      5. Copy or move the data from the temporary dataset to the new dataset, then delete the temporary dataset.

    3. Go back to the Firebase console and the BigQuery card . Then do the following:

      1. Toggle on the Crashlytics slider to re-enable the BigQuery integration.
      2. Select the apps for which you want to enable the export.

    4. Go back to the Google Cloud console and the BigQuery page to verify that a transfer configuration is created for Crashlytics in the new region.

    Performance Monitoring

    To change the location of an existing Performance Monitoring export to BigQuery , follow these instructions:

    1. In the Firebase console, go to the Integrationspage . Then do the following:

      1. In the BigQuery card, click Manage.
      2. Toggle off the Performance Monitoring slider to disable BigQuery .

    2. In the Google Cloud console, go to the BigQuery page . Then do the following:

      1. Create a temporary dataset to store a copy of the existing data from your original dataset. Assign the temporary dataset a different name than the name of the original dataset.
      2. Copy or move the data from your original dataset to the temporary dataset.
      3. Delete the original dataset.
      4. Create a new, permanent dataset with the same name as your original dataset ( firebase_performance ), then select the new region.
      5. Copy or move the data from the temporary dataset to the new dataset, then delete the temporary dataset.

    3. Go back to the Firebase console and the BigQuery card . Then do the following:

      1. Toggle on the Performance Monitoring slider to re-enable the BigQuery integration.
      2. Select the apps for which you want to enable the export.

    4. Go back to the Google Cloud console and the BigQuery page to verify that a transfer configuration is created for Performance Monitoring in the new region.

    Pricing and the BigQuery sandbox

    If your Firebase project is on the no-cost Spark pricing plan, you can link Google Analytics , Cloud Messaging , Crashlytics , and Performance Monitoring to the BigQuery sandbox , which provides no-cost access to BigQuery . Refer to Using the BigQuery sandbox for information on the BigQuery sandbox's capabilities.

    If your Firebase project is on the pay-as-you-go Blaze pricing plan, you can link Google Analytics , Cloud Messaging , Crashlytics , Performance Monitoring , and A/B Testing to BigQuery . Your use of BigQuery is subject to normal BigQuery pricing , which includes limited no-cost use.

    Design a Mobile Site
    View Site in Mobile | Classic
    Share by: