--- title: Using Google Data Studio with Crashlytics data | daily.dev description: Firebase launched a Google Data Studio template that works on top of the existing Crashlytics-to-BigQuery export, letting teams build custom crash-reporting... canonical: https://daily.dev/posts/using-google-data-studio-with-crashlytics-data-lpdrzeci9 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Using Google Data Studio with Crashlytics data | daily.dev og:description: Firebase launched a Google Data Studio template that works on top of the existing Crashlytics-to-BigQuery export, letting teams build custom crash-reporting... og:url: https://daily.dev/posts/using-google-data-studio-with-crashlytics-data-lpdrzeci9 og:image: https://api.daily.dev/og/posts/LPDRzeCi9.png og:image:alt: Using Google Data Studio with Crashlytics data og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Using Google Data Studio with Crashlytics data **[Firebase](https://daily.dev/sources/firebase-blog)** · 4 min read · 0 upvotes · 0 comments ## Summary Firebase launched a Google Data Studio template that works on top of the existing Crashlytics-to-BigQuery export, letting teams build custom crash-reporting dashboards without writing SQL. The template shows OS versions and devices with the most crashes, trends over time, and lets teams filter by custom keys (like game level) and by specific code files. Since BigQuery holds the exported data, teams can retain and analyze crash data beyond the 90-day limit of the native Crashlytics dashboard, and share dashboards collaboratively across non-technical team members. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How can I build a custom dashboard from my Firebase Crashlytics crash data? Export Crashlytics data to BigQuery via the Firebase console integrations page, then connect a Google Data Studio template to that BigQuery dataset. Data Studio sits on top of BigQuery and lets non-SQL team members filter crash data by OS version, device, custom keys (like a game level or experiment ID), and specific code files, and share the dashboard for collaboration. _daily.dev surfaces practical guides like this for teams wiring up crash analytics dashboards._ ### How long does Firebase Crashlytics retain crash data by default, and how can I keep it longer? The Crashlytics dashboard retains crash data for 90 days by default. To keep data longer, export it to BigQuery, where retention and deletion policies are controlled by the team rather than Firebase, making it possible to track year-over-year stability trends and select custom date ranges beyond 90 days. _Developers tracking long-term app stability trends can find setup breakdowns like this on daily.dev._ ## Similar posts on daily.dev - [What’s new with Google Data Cloud](https://daily.dev/posts/what-s-new-with-google-data-cloud-d1pt7f0q9) · Google Cloud · 0 upvotes · 0 comments - [Introducing BigQuery Graph](https://daily.dev/posts/introducing-bigquery-graph-tig40l393) · Google Cloud · 0 upvotes · 0 comments - [Introducing BigQuery Agent Analytics](https://daily.dev/posts/introducing-bigquery-agent-analytics-9cxicqkzb) · Google Cloud · 1 upvotes · 0 comments --- Tags: [#mobile](https://daily.dev/tags/mobile), [#firebase](https://daily.dev/tags/firebase), [#google-bigquery](https://daily.dev/tags/google-bigquery) [View this post on daily.dev](https://daily.dev/posts/using-google-data-studio-with-crashlytics-data-lpdrzeci9) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Using Google Data Studio with Crashlytics data","url":"https://daily.dev/posts/using-google-data-studio-with-crashlytics-data-lpdrzeci9","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/using-google-data-studio-with-crashlytics-data-lpdrzeci9"},"datePublished":"2026-08-23T12:17:56.020Z","dateModified":"2026-08-23T12:26:01.350Z","description":"Firebase launched a Google Data Studio template that works on top of the existing Crashlytics-to-BigQuery export, letting teams build custom crash-reporting...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7ed721de96163685d26ab7e314be3ebc?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7ed721de96163685d26ab7e314be3ebc?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Firebase","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Firebase","logo":"https://media.daily.dev/image/upload/s--i395oqZH--/f_auto,q_auto/v1787487448/logos/firebase-blog?_a=BAMAMicg0","url":"https://daily.dev/sources/firebase-blog"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/using-google-data-studio-with-crashlytics-data-lpdrzeci9","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"mobile,firebase,google-bigquery","timeRequired":"PT4M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Firebase","item":"https://daily.dev/sources/firebase-blog"},{"@type":"ListItem","position":3,"name":"Using Google Data Studio with Crashlytics data"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/using-google-data-studio-with-crashlytics-data-lpdrzeci9#faq","mainEntity":[{"@type":"Question","name":"How can I build a custom dashboard from my Firebase Crashlytics crash data?","acceptedAnswer":{"@type":"Answer","text":"Export Crashlytics data to BigQuery via the Firebase console integrations page, then connect a Google Data Studio template to that BigQuery dataset. Data Studio sits on top of BigQuery and lets non-SQL team members filter crash data by OS version, device, custom keys (like a game level or experiment ID), and specific code files, and share the dashboard for collaboration. daily.dev surfaces practical guides like this for teams wiring up crash analytics dashboards."}},{"@type":"Question","name":"How long does Firebase Crashlytics retain crash data by default, and how can I keep it longer?","acceptedAnswer":{"@type":"Answer","text":"The Crashlytics dashboard retains crash data for 90 days by default. To keep data longer, export it to BigQuery, where retention and deletion policies are controlled by the team rather than Firebase, making it possible to track year-over-year stability trends and select custom date ranges beyond 90 days. Developers tracking long-term app stability trends can find setup breakdowns like this on daily.dev."}}]} ```