How to Unify Firebase and Google Ads for App Growth

November 3, 2026

How to Unify Firebase and Google Ads for App Growth

How to Unify Firebase and Google Ads for App Growth

Firebase and Google Ads app growth cover

To unify Firebase and Google Ads, link the two accounts so that your app’s in-app events flow into Ads as conversions and your Firebase audiences flow into Ads as remarketing lists. The link takes a few minutes if you have the right permissions. The work that pays off comes afterward: choosing the events that matter, keeping privacy settings correct, and reading ad spend next to real app outcomes.

This guide covers what the link does, what you need before you start, the exact steps, how to import conversions and audiences, how to fix the usual failures, and how to connect the result to the rest of your growth work.

Apptenium
See App Growth Data in One Place
Apptenium brings ASO scanning, competitor intelligence, keyword tracking, and app performance insights together in one platform.
Explore Apptenium

TL;DR

Table of Contents

What linking Firebase and Google Ads actually does

Firebase collects what happens inside your app. Google Ads spends your budget to bring people to it. Without a link, those are two separate stories: Ads reports clicks and installs, and Firebase reports behavior, with no shared thread between them.

According to Google Ads Help, the link lets you view Google Ads data in Firebase or Analytics, import Firebase conversions, measure installs and in-app actions, choose Firebase events as conversion actions, and use Firebase audiences for remarketing. The same page explains that the imported data shows whether advertising drives installs, in-app actions and other app goals, so you can adjust campaigns accordingly.

Firebase’s own documentation describes the flow in both directions. Campaign data from Ads becomes visible in Analytics, while Firebase-associated key events and audiences are shared with Ads, and Analytics features such as cross-channel attribution become available inside Ads.

In practice, that gives you three capabilities:

  1. Better bidding signals. Instead of optimizing for installs alone, you can optimize for a purchase, a subscription start or a completed tutorial.
  2. Audience reuse. A segment you build in Firebase, such as people who opened the app in the last 60 days, can be targeted or excluded in Ads.
  3. A closed loop. You import app outcomes, assess advertising impact, and change campaigns toward the actions that matter.

Most failed links trace back to a missing prerequisite. Check these first.

Requirement Why it matters
Google Ads administrative access Required to connect products in the Data manager
Auto-tagging enabled Needed for conversion tracking on linked data; Ads requires it to track app conversions in Engagement and web campaigns
Firebase project ownership Firebase links require the Owner role on the project
Edit access on a GA4 property Required if you link through a GA4 property instead
Firebase linked to GA4 A Firebase project must first be linked to a GA4 property before Ads can be linked
Personalized advertising on Needed so Firebase or Analytics lists can be used for remarketing in App engagement or Web campaigns

Two habits save time. First, confirm that the person doing the setup holds both roles, since a marketer with Ads admin rights often cannot see the Firebase project owner settings, and a developer who owns the project often has no Ads access. Second, decide in advance which events you want as conversions. If your app does not yet log a purchase or subscription event, add it to your Firebase instrumentation first, so the link has something meaningful to import.

If you are also deciding whether to run campaigns in-house or hire help, a breakdown of Google Ads management costs gives a sense of what agency support typically covers, which is useful context before you decide who owns the account.

There are three official paths. They end in the same link, so use the one where you have the right permissions.

Option 1: from Google Ads

This is the route most advertisers use.

  1. In Google Ads, open Tools > Data manager > Connect product.
  2. Choose Google Analytics (GA4) & Firebase.
  3. Select the property or project you want.
  4. Optionally turn on app and web metrics and audiences.
  5. Review the settings and link.

These steps are documented in Google Ads Help on product linking. A second documented Ads-side route goes through Admin > Google Analytics (GA4) and Firebase > Details, where you select the property or project, choose additional data such as audiences, then link and activate.

Option 2: from Firebase

Firebase Help describes the link from the console side. Because the project must already be tied to a GA4 property, start by confirming that Analytics is enabled for your project. Then open the Ads integration and select the Google Ads account to connect. The Firebase Help page on linking Ads lists the details.

Developer linking Firebase and Ads accounts

Option 3: from Google Analytics

In Analytics, the path is Admin > Product links > Google Ads links > Link. You choose the Ads accounts, confirm, review the personalized advertising and auto-tagging settings, and submit. Analytics Help documents each screen. If you manage several properties and want to confirm that each one is connected as expected, a guide on how to connect Google Analytics 4 can help you check the basics of your property setup.

Linking multiple accounts

A single Firebase project can connect to several Google Ads accounts. Firebase documentation notes that each linked account can access Firebase-created audiences. That matters for agencies and for companies that run separate Ads accounts per region or per brand: you build the segment once and share it widely.

How long until data shows up

Google Analytics Help says Google Ads campaign data becomes available in Analytics within 48 hours after linking. Do not judge the setup in the first hour. Check back after two days before you assume something is broken.

Turn Firebase events into Google Ads conversions

Linking alone does not change how your campaigns bid. You have to tell Ads which events count.

After the link is active, you choose which Firebase events to track as conversion actions. Google Ads states that no new app code is needed, because Ads uses the Firebase code already installed in your app. For bidding or for adding audiences to a campaign or ad group, Analytics Help says you need to create Ads conversions from Analytics key events.

Here is a sensible way to pick events:

  • Start with one primary conversion. For a subscription app, that is usually the trial start or first paid purchase. For a game, it might be a level reached that correlates with retention.
  • Add one or two secondary events. Registration or onboarding completion can feed learning when your primary event is rare.
  • Avoid importing everything. Too many conversion actions dilute bidding and make reports hard to read.
  • Match event timing to your decision window. An event that fires on day 14 is a poor signal for a campaign you want to adjust weekly.

A practical test: if a campaign doubled its volume of this event tomorrow, would your business be better off? If the answer is yes, it is a good conversion. If the answer is “maybe”, keep it as an observation metric instead.

Share Firebase audiences for remarketing

Firebase documentation says the integration supports audience segmentation, exporting audience lists to Ads, and importing Analytics events into Ads. That opens a few high-value uses:

  • Re-engagement. Target users who installed but have not opened the app recently.
  • Upsell. Reach people who finished onboarding but never hit the paywall.
  • Exclusion. Keep paying subscribers out of install campaigns so you stop spending on people who already converted.
  • Lookalike-style expansion. Use your best segment as a signal for who to find next.

Build audiences with a clear business rule rather than a vague one. “Opened the app in the last 30 days and has not purchased” is a list you can write a message for. “Active users” is not. If you want a deeper look at how segmentation shapes ad results, this overview of the role of segmentation in ads is a helpful companion.

Remember the privacy dependency: Google Ads requires that personalized advertising remain enabled for Firebase or Analytics lists to be used for remarketing in App engagement or Web campaigns. Treat it as a campaign-level prerequisite, not a footnote. If your legal or consent setup disables personalization for certain regions, expect smaller lists there.

Read the combined data to improve campaigns

Once data flows, the useful question is not “how many installs did Ads report?” It is “which campaigns bring people who do what we need?”

Google Ads frames this as a loop: use imported installs and in-app actions to judge performance, then make changes in the account that push toward those goals. A weekly routine keeps it manageable:

  1. Compare cost per install with cost per key event. A cheap install that never reaches your key event is expensive.
  2. Split by campaign and creative. Look for campaigns whose users reach the key event at a clearly higher rate.
  3. Check audience size and overlap. Small lists limit remarketing reach; heavy overlap suggests you are paying twice for the same people.
  4. Shift budget gradually. Move spend toward the winners in steps, and give bidding time to relearn after each change.
  5. Record what you changed. Annotate dates so a later drop in performance has an explanation.

If you want to go further and forecast which users are likely to convert or churn, predictive modeling is the next layer many teams explore once the event data is clean and consistent.

Fix the most common problems

The ranking threads for this topic are full of the same complaints: conversions not importing, audiences showing zero, accounts that cannot see each other. Most are settings issues.

Audiences show zero or do not appear in Ads

Google’s troubleshooting guidance points to a short checklist. Confirm that Enable Personalized Advertising is on, that Firebase’s audience-sharing settings are enabled, and that user-provided data collection is on if you need it for Customer Match. User-provided data collection allows consented first-party data to be sent to Analytics, which supports features such as Customer Match for exported audiences.

Also remember that new audiences need time to populate, and a list has to reach a minimum size before Ads will serve to it. If you built the audience a few days ago, check again later before changing settings.

Manager accounts

If you work through a manager account, set the manager as the audience manager for all sub-accounts, and then select it in each sub-account’s audience-manager setting. Skipping the second half is a common reason audiences appear in one account but not another, as described in the same troubleshooting page.

Conversions are missing

Work through these in order:

  • Is the link active, and did you finish the activation step?
  • Is auto-tagging on in the Ads account?
  • Did you actually select the events as conversion actions, or only link the accounts?
  • Has the event fired in Firebase at all in the reporting period?
  • Are you comparing the same attribution window and date range in both tools?

Differences between the two tools are normal. Each uses its own attribution logic, so expect totals to be close but not identical. Pick one as your source of truth for decisions and use the other to sanity-check.

Build errors with ads libraries

Some of the posts that rank for this keyword are about SDK conflicts, such as Firebase and mobile ads libraries clashing in a project, or Unity and Flutter setups. Those are code-level dependency problems, separate from the account link described here. If you hit one, check version compatibility between the Firebase and ads SDKs in your project before changing anything in Ads.

Our perspective

We built Apptenium on a simple observation: app teams do not suffer from a lack of data. They suffer from data scattered across too many places. Firebase has behavior, Google Ads has spend, the app stores have listing performance, and the ad networks have monetization. Each tool answers one slice of the question, and the person who has to decide what to do next ends up with six tabs open.

Linking Firebase and Google Ads is the right first move, and we recommend every team do it. But paid traffic is only one source of installs. Organic search inside the stores often drives a large share of downloads, and it responds to different levers: your title, subtitle, keywords, icon and screenshots. If you judge paid campaigns without seeing what your organic listing is doing, you can credit or blame the wrong thing.

That is why we put ASO scanning, keyword tracking, competitor intelligence and performance reporting in one place, with Firebase, Google Analytics and ad network data alongside. Our AI recommendations turn each scan into copy-ready fixes, so improving your listing becomes a task you can finish this afternoon rather than a research project. We think a serious app marketer should be able to see downloads, revenue and ad performance together, and act on them without a sales call.

Mike

Connect paid data to the rest of your growth work

Paid and organic installs feed each other. Strong paid campaigns raise store visibility, and a stronger listing raises the conversion rate of every paid click. Once your Firebase and Ads link is working, a few habits make the combination more valuable:

  • Keep the landing experience consistent. Your store listing is where paid clicks land, so a weak icon or unclear first screenshot wastes ad spend. Our free ASO tools let you scan a listing and test icon ideas before you send traffic to it.
  • Use keyword data to guide ad themes. Terms that already bring organic installs are good candidates for ad copy and creative angles.
  • Watch competitors. When a rival changes its listing or starts a new push, your cost per install can move even if nothing changed on your side.
  • Report on one page. Stakeholders want to know downloads, revenue, subscriptions and ad monetization together, not in separate exports.

These are the kinds of questions our app analytics view is designed to answer, and our ASO tools cover the listing side.

Put it all in one place with Apptenium

If you are already doing the Firebase and Google Ads work, the next gain usually sits in your store listing and in how you read results across sources. Apptenium combines ASO scanning, keyword tracking, competitor intelligence and performance reporting, and it integrates with Firebase and Google Analytics plus ad networks, so you are not stitching reports together by hand.

There is a Free plan with a limited number of scans per month, and a Pro plan at $9.99 per month with unlimited scans and premium features. You can compare them on the pricing page and start with the free tier to scan your own listing.

Apptenium

If you manage several apps, our competitor intelligence pages show how to track rivals across your whole portfolio.

FAQ

Do I need to add new code to my app to import Firebase conversions into Google Ads?

No. Google Ads says it uses the Firebase code that is already installed in your app. You link the accounts, then choose which Firebase events to track as conversion actions. If an event is not logged in Firebase yet, it needs to be added to your instrumentation first.

Why do my Firebase audiences show zero users in Google Ads?

The usual cause is a setting. Check that Enable Personalized Advertising is on and that Firebase’s audience-sharing options are enabled. For manager accounts, the manager must be set as audience manager for each sub-account. Also allow time for a new audience to populate.

You need administrative access in Google Ads and auto-tagging enabled. Firebase links require ownership of the project, while a GA4 link requires Edit access on the property. The Firebase project must also already be linked to a GA4 property.

Can one Firebase project connect to more than one Google Ads account?

Yes. Firebase documentation says a project can connect to multiple Google Ads accounts, and each linked account can access the audiences created in Firebase. This suits agencies and companies with separate accounts per market or brand.

How soon will I see data after linking?

Google Analytics Help says Google Ads campaign data becomes available in Analytics within 48 hours after linking. Wait at least that long before troubleshooting, and make sure the events you want have actually fired during the period you are checking.

Sources

← Back to Guides · Home