Other tools

Firebase Analytics experts

Measure how your app is used, all the way to Google Ads and BigQuery.

The Google Analytics for Firebase SDK is Google's collection for apps. We deploy it, QA it and run it with your teams.

Book a discovery call
Scroll to the content

EdgeAngel Firebase Analytics expertise

Configure the collection, make it compliant, connect the Google ecosystem

01

Architecture and configuration

A solid data architecture and an SDK configured for reliable collection, on iOS, Android and cross-platform.

  • Data architecture: the app's KPIs and the tagging plan that carries them, within the tool's limits, 500 event types, 25 parameters per event, 25 user properties
  • Events: the automatic ones the SDK collects on its own, first_open, screen_view, in_app_purchase, the recommended ones from Google's catalogue and your custom events
  • Firebase SDK: integration on iOS, Android, Flutter, Unity and in WebViews, pseudonymous User-ID, user properties, QA in DebugView before each release
  • Collection structure: GTM for iOS and Android, and sGTM for Apps to modify, block and route events to your destinations from your server
  • Google ecosystem: the Google Analytics property and its app streams, the Google Ads link, the BigQuery export, on-device conversion measurement for iOS
02

Mobile compliance and privacy

An app compliant with the GDPR and with Apple's rules, with a collection that holds in both frameworks.

  • Google Consent Mode: the four consent signals passed to the SDK, the default values set in the app, persistence across launches, modelling for refusals
  • App Tracking Transparency: the IDFA collected with authorisation only, attribution that adapts, event collection that does not change, detailed on the iOS Tracking page
  • SKAdNetwork: the postbacks sent to Google Analytics and Google Ads for iOS campaigns, detailed on the SKAdNetwork page
  • Consent management: the SDK made conditional on the choices collected in Didomi or your CMP, advertising identifiers disabled when the context requires it
  • Retention and filters: user data retention set in the property, developer traffic filtered out of the reports
03

Integration and activation

Firebase data connected to your third-party tools, your ad platforms and your warehouse, to improve the experience and the campaigns.

  • Third-party tools: the same tagging plan feeds the MMP, Adjust or AppsFlyer, and your product analytics tools
  • Google Ads: key events imported as conversions, audiences built in Google Analytics, install and engagement campaigns measured
  • BigQuery: the daily export and the intraday streaming of raw events, modelled in your warehouse with our Modern Data Stack offer
  • User journeys: funnels, retention per cohort and segments read in Google Analytics, to improve conversion and retention
  • QA: DebugView, and Firetest, our own tool, to validate the integrations before the release on the stores

The tool

Firebase Analytics, our reading

What people call Firebase Analytics is today Google Analytics, collected in an app by the Google Analytics for Firebase SDK: the data lives in a Google Analytics property, with its iOS and Android streams, and the Firebase project acts as the bridge. The SDK collects about twenty events on its own, first_open for the install, screen_view, session_start, in-app purchases, and accepts up to 500 event types per app instance, 25 parameters per event and 25 user properties. The current SDKs are Apple 12.19.2, released on 17 September 2026, and Android 23.2.0, from 19 March 2026.

Consent Mode for apps, in version 2 since 30 October 2023, sets no default value: the app has to declare them. The export to BigQuery is daily, capped at one million events per day in the standard edition, with an intraday stream. And since 2025, sGTM for Apps routes the SDK's events to a server container, through a single configuration flag and a traffic percentage set in the property.

Updated September 2026

What Firebase Analytics does very well: opening the whole Google ecosystem with one SDK

One SDK, no licence, and the app enters the Google Analytics property next to the site, with the same reports, the same explorations, the same audiences. The Google Ads link imports key events as conversions and serves install and engagement campaigns; on iOS, on-device conversion measurement makes up for part of what the ATT prompt takes away. The event model is the one Google Analytics adopted for the web: a team that knows one reads the other. And the BigQuery export delivers raw events, which makes it the source of a warehouse without buying anything.

What it really is: a collection built for Google, to be configured yourself

Firebase Analytics sets no consent setting by default, and it collects the IDFA as soon as the advertising module is linked and the user has accepted the ATT prompt. What is compliant in a European app is the configuration you give it: the four Consent Mode signals declared, the CMP that feeds them, the advertising identifier disabled when the context requires it, retention set in the property. The tool documents the commands, not the compliance of the result, and Google itself writes that accepting Apple's prompt does not count as consent under its EU policy. That is the work of the second card, and it is QA'd like the rest.

Didomi, the CMP that feeds Consent Mode in the app

Where it stops: attribution outside Google, raw volume, and destinations

Install attribution is limited to Google Ads, the Play Store referrer, Apple Search Ads and UTM parameters: for Meta, TikTok or Snap, an MMP attributes, and the same tagging plan feeds it. The standard BigQuery export stops at one million events per day; beyond, it is Google Analytics 360 or a server-side collection. And events leave in batches of about an hour, to Google. sGTM for Apps changes that last point: the SDK sends its events to your server container, which distributes them to the ad platforms and to your warehouse, under your control. That is where our Modern Data Stack offer takes over.

Adjust, the MMP that attributes across all ad networks

Sources : Server-side tagging for mobile apps, Google Tag Platform documentation · Consent mode for apps, Google Tag Platform documentation

Our expert notes : Server-side GTM for Apps · Google Consent Mode v2, the essentials · GDPR, CNIL and Analytics: Consent Mode and AI

Frequently asked questions about Firebase Analytics

What is the difference between Google Analytics and Firebase?

None on the data: Firebase Analytics is the common name of the Google Analytics for Firebase SDK, Google's collection for apps, and the events land in a Google Analytics property, in iOS and Android streams next to the web stream. Firebase is Google's mobile development platform, which includes this SDK; the event model is the same on both sides.

Is Firebase Analytics free?

The SDK and the Google Analytics reports carry no licence, with the limits of the standard edition: 500 event types per app, 25 parameters per event, 14 months of user data retention at most. The daily BigQuery export stops at one million events per day, and BigQuery storage and queries are billed by Google Cloud. Google Analytics 360 lifts those caps, under licence.

How do you manage user consent on mobile with Firebase?

With a mobile CMP that collects the choices, and Google's Consent Mode that passes them to the SDK through its four signals: analytics, advertising, user data, personalisation. Firebase sets no default value, the app declares them. On iOS, the App Tracking Transparency prompt comes on top, sequenced with the CMP, and the IDFA is only collected after acceptance.

Does Firebase replace an MMP?

No, the two complement each other. Firebase attributes installs to Google Ads, the Play Store referrer, Apple Search Ads and UTMs, and it measures usage in the app. An MMP such as Adjust or AppsFlyer attributes installs and events to every ad network, Meta, TikTok and Snap included, as a neutral third party. The same tagging plan feeds both.

Can I export my Firebase data?

Yes, to BigQuery: a daily export of raw events, one million per day in the standard edition, and an intraday stream for freshness. From the warehouse, the data is crossed with your sales, your CRM and your media costs, and read in Data Studio or Power BI. With sGTM for Apps, events also go through your server before any destination.

Contact

You leave your details, we get back to you within 24 hours.

A first call to understand your context, and tell you what is feasible and under which conditions.

  1. Contact and need
  2. Tell us more (optional)
  3. Then we schedule a call

Your details are used to reply to you on this topic. Data protection policy

Or call us directly: +33 1 84 16 42 20

Paul Schmitt

Paul Schmitt

Consulting Director

"Our goal is to make your data actionable to generate concrete value, quickly."

The team