Search
Clear search
Close search
Google apps
Main menu

Attribution

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: first_open, in_app_purchase, and ecommerce_purchase.

Click the selector menu action menu (far right of the table row) to disable an event as a conversion.

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

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

To see AdWords-attributed Conversion Events in your attribution reports, import the Firebase Conversion Event to AdWords. Once you have linked your project to AdWords, then those conversion events will also be available in AdWords. You can import them under Tools → Conversions → Firebase.

Add a network

To add a network:

  1. In Google Analytics or Firebase, navigate to your app.
  2. Google Analytics: Click Attribution in the report navigation, then click Network Settings.
    Firebase: In Analytics, click Attribution, then click Network Settings.
  3. Click ADD A NETWORK.
  4. Select a network from the menu.
  5. Source is automatically the Network name. Some networks also offer metadata about Medium and Campaign information, so no additional input is needed. For other networks, we’ve provided the Medium and Campaign fields to capture custom information. Use the generated URL as your referral link. (Copy and paste the URL.)
  6. DOWNLOAD: If you’re running a campaign to drive users to download the app, use the URL you generate here.
  7. 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.
  8. To send conversion information back to the network, click Configure postback. Otherwise, click Done.

Postbacks

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 Google Analytics or Firebase, navigate to your app.
  2. Google Analytics: Click Attribution in the report navigation, then click Network Settings.
    Firebase: In Analytics, 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.
Was this article helpful?
How can we improve it?