Firebase Analytics

Firebase Analytics is free mobile analytics by Google (part of the Firebase platform) for iOS and Android apps, tightly linked to Google Analytics 4, Google Ads and Firebase services (push, Remote Config, Crashlytics). We embed the SDK into the app and set up events, audiences, funnels, crash reports and passing conversions to Google Ads/GA4. Honestly about the main point: Firebase is the Google ecosystem. If your ads and analytics are already in Google (Google Ads, GA4), Firebase links them conveniently; if your audience is in the RF, note the nuance: Google services load from their servers, may work unstably or be unavailable in Russia, and data storage may not fully comply with 152-FZ, so for a Russian audience AppMetrica is often more stable (see the neighbor service). But if your audience is not only in the RF, the link with Google Ads and GA4 is often irreplaceable, and AppMetrica does not replace it — we will honestly advise what is more practical. This is app analytics: for a website Firebase Analytics technically reduces to GA4, we do not do a separate "Firebase for the web" — we cover the web with web analytics (Metrica/GA4), and this service is about a mobile app. Embedding requires code access and a new build: to work, the app must be rebuilt and an update released to the App Store and Google Play — store review takes time and depends not on us. Data is not 100%: a user can refuse collection, and on iOS tracking is limited by Apple privacy (ATT, SKAdNetwork) — install attribution comes aggregated, without a link to a specific user. Firebase may also sample data or cap volume on high traffic and the free tier. Firebase Analytics itself is free (adjacent Firebase services can be paid at high volume); our price is for the SDK integration and event setup. You can also set it up yourself if you have developers; you pay for correct setup of events, funnels and the Google Ads/GA4 link. Later app code changes can break collection — maintenance is quoted separately. User consent and data (152-FZ, GDPR for a foreign audience, Apple/Google policies) are on you, we help technically; implementing consent banners and the collection opt-in logic is separate work and, if needed, legal review. If the app is just launching or the audience is small, deep analytics is excessive — start with basic events, and we will say so. Picture this: you see that only a third of users reach the second launch after onboarding, and you understand which step to rework. The base price starts from 30,000 ₽; it depends on the number of events, the platforms and the ad link.

• You cannot see what users do in the app after installing.
• Google Ads campaigns run, but app conversions are not passed back to them.
• The app crashes, and you learn it from reviews, not from reports.
• There is no single picture: analytics, ads and crashes are in different places.

• Embedding the Firebase Analytics SDK (iOS and/or Android)
• Setting up events, audiences and funnels
• Crash reports (Crashlytics) and stability
• A link to Google Analytics 4 and passing conversions to Google Ads
• The ATT consent prompt on iOS and highlighting 152-FZ/GDPR requirements
• A check of collection correctness and event documentation
• A comparison with AppMetrica and an honest choice for your audience/region
• An honest assessment of whether you need analytics at your stage

• You see in-app behavior: onboarding, retention, target actions
• App conversions are passed to Google Ads/GA4
• Crashes are visible at once, not from reviews
• It is clear where the tech ends and platform privacy, region and your consent begin

• We clarify the platforms, events and the Google ad link
• We embed the SDK, set up events, Crashlytics and the ATT consent
• We verify collection on a build and help release the update

• Firebase or AppMetrica?

  It depends on the ecosystem and audience. Firebase is convenient if your ads and analytics are in Google (Google Ads, GA4) and you need its services (Crashlytics, push, Remote Config). For an RF audience AppMetrica is often more stable — Google services may have availability nuances. We will pick honestly for your case, not by default.

• Is it for a site or an app?

  Firebase Analytics is for a mobile app. For a website you use web analytics (Yandex Metrica or Google Analytics 4). If you have only a website, Firebase Analytics is not needed — we will honestly say so and suggest web analytics.

• Will it really show which ad brought a user?

  Partly. On Android it is fuller; on iOS Apple limits it: ATT is required, sources come aggregated via SKAdNetwork, without a link to a specific user. We set up the fullest attribution within the rules, but do not promise it is perfect on iOS — that is an Apple limit.