Home » Android » android – How to configure/display attribution sources in Firebase Analytics?

android – How to configure/display attribution sources in Firebase Analytics?

Posted by: admin May 14, 2020 Leave a comment


All my attribution sources in Firebase Analytics for our Android and iOS apps are “(direct)”, even though we have over 250k first_open events showing up since we migrated from Google Analytics to Firebase Analytics.

Is there something we need to configure for these to register properly, or am I not using the Console reporting correctly, or maybe something else?

I am expecting at least some basic sources like “organic search” to show up.

How to&Answers:

You can get this to work for your Android app by implementing Google Play Campaign attribution in your app. Checkout the latest instructions. After adding this to your Android app, you can use UTM parameters on your links and the correct campaign attribution will show up in Firebase.


The Firebase SDK library uses an app-instance identifier to identify a unique installation of the App.

When using the SDK, an app-instance identifier gets generated at the app level.

By default, the Firebase SDK collects identifiers for mobile devices (for example, Android Advertising ID and Advertising Identifier for iOS) and utilizes technologies similar to cookies.

On iOS, the SDK collects the Advertising Identifier if it is available. For IDFA to be available, a developer has to link in the following libraries:

If the Advertising Identifier is unavailable, the SDK collects the Vendor Identifier. If the Advertising Identifier becomes available after the Vendor Identifier was reported, the SDK stops collecting the Vendor Identifier.

By default, on Android the SDK collects the Advertising ID. If the Advertising ID is not collected, the device’s hardware identifier, e.g., Android ID (SSAID), is collected instead. This alternative Android identifier cannot be reset.

source: https://support.google.com/firebase/answer/6318039?hl=en