It’s important to know which marketing efforts are most effective at acquiring new users and keeping them engaged. The Attribution tab shows how many conversion events were driven by each source and ad network.

In this article:

Conversion Events tab

In Firebase, your most important events are called conversions. The table lists the events defined as conversions, three of which are predefined by Firebase:

To enable or disable an event as a conversion, flip the switch in the Mark as conversion column in the row for that event.

Click an event in the table to see how many conversions are attributed to each source. When you're evaluating an event, choose an attribution model:

  • Cross-channel last click: Firebase looks at clicks from all sources and attributes the conversion to the last click.
  • AdWords-preferred last click: Firebase attributes the conversion to AdWords whether or not there is a click from another source.

In addition to choosing an attribution model, you can also choose to see the origin of the events by Source, Medium, and Campaign.

To see AdWords-attributed Conversion Events in your AdWords attribution reports, link your Firebase project to AdWords, and then import the Firebase Conversion Events to AdWords (Tools > Conversions > Firebase).

iOS installation metrics and in-app event-attribution data for Google AdWords iOS Search App Install campaigns are visible under direct in the Firebase Analytics Attribution tab, and do not appear in the AdWords console.

Add a network

To add a network:

  1. In Analytics, navigate to your app.
  2. Click Attribution, then click Network Settings.
  3. Click NEW NETWORK.
  4. Select a network from the menu.
  5. Source is automatically the Network name. Some networks also offer metadata about Campaign medium and Campaign name, so no additional input is needed. For other networks, we’ve provided the Campaign medium and Campaign name fields to capture custom information. Use the generated URL as your referral link (copy and paste the URL).
    • DOWNLOAD: If you’re running a campaign to drive users to download the app, use the URL you generate here.
    • DEEP LINK: If you’re running a campaign to re-engage existing app users, use the DEEP LINK tab. In this section, enter the URL scheme and path information. The same parameters will be appended.
  6. To send conversion information back to the network, turn on the Configure Postback switch. Otherwise, click Save.


A Postback sends your conversion data back to an ad network. Postbacks are optional. You may send first_open data in addition to other in-app conversion events. If you decide to set up a Postback, you also choose whether to send the network all conversions, or just the conversions that Firebase attributes to that particular network.

Postbacks help networks optimize the traffic they send you. For example, if a network knows that an app has been downloaded to a device, then it also knows not to serve that device any additional ads for that app.

If you send the network all conversion data, then that network is able to optimize its own traffic based on an awareness of conversions from all networks. When you send all conversion data to a network, the other networks involved in delivering conversions are anonymized.

To configure a Postback:

  1. In Analytics, navigate to your app.
  2. Click Attribution, then click Network Settings.
  3. In the row for the network, click Configure postback.
  4. Select the conversions you want to send, and select Only this network or All sources.
  5. Enter the network parameters (e.g., Tracking ID, Advertiser Password). Parameters vary by network.
  6. Click Save.

Custom campaigns for Google Play apps

When you use a custom campaign for an app you're distributing via Google Play, use the Google Play URL Builder to generate your custom URLs.

Was this article helpful?
How can we improve it?