🙈 Analytics conversions attribution: 🙉 no UTM source in first_open event 🙊

[Scino]

Step 1: Describe your environment

• Android Studio version: 4.0
• Firebase Component: Analytics
• Component version: 17.6.0 (Firebase BoM 25.12.0)

Step 2: Describe the problem

Firebase analytics is not collecting anymore utm_source parameters in first_open events.

Since INSTALL_REFERRER broadcast's deprecation (march 2020), Firebase Console and Google Analytics are not correctly showing sources for first_open conversions anymore.

NOTE: on Google Play Console, conversions are attributed properly. Our Google Play links are well built.

Firabase Console conversions view:

Google Play Console conversions view:

What we did to mitigate the problem:

• Removed BroadcastReceiver
• Updated MMP tracker SDKs like Kochava and Appsflyer
• Upgraded to new Install Referrer API following the official doc.
• Removed any old Google Analytics service or library
• Switched to Firebase Android BoM to avoid any library conflict
• We are able to retrieve and save utm_source to UserProperties as a temporary workaround. This means that the value exists, but on first_open we don't have this extra data and the SDK seems to not gather any information about utm_source on his own, as it actually should.
• Google Play links are correctly built and Google Play Console properly shows sources
• Enabled Firebase Analytics collection by default in AndroidManifest

AndroidManifest.xml:

<meta-data
            android:name="firebase_analytics_collection_enabled"
            android:value="true" />
<meta-data
            android:name="google_analytics_adid_collection_enabled"
            android:value="false" />

Firebase Analytics logs:

(Installing on Emulator from Android Studio)

2020-11-19 17:33:36.838 5702-6725/? V/FA-SVC: Install Referrer Service is: available
2020-11-19 17:33:36.850 5702-5702/? V/FA-SVC: Install Referrer Service connected

2020-11-19 17:33:36.891 5702-6725/? V/FA-SVC: Logging event: origin=auto,name=first_open(_f),params=Bundle[{ga_conversion(_c)=1, _r=1, engagement_time_msec(_et)=1, previous_first_open_count(_pfo)=44, system_app(_sys)=0, update_with_analytics(_uwa)=0, system_app_update(_sysu)=0}]

2020-11-19 17:33:37.083 5702-6725/? V/FA-SVC: InstallReferrer API result: utm_source=google-play&utm_medium=organic
2020-11-19 17:33:37.084 5702-6725/? V/FA-SVC: Logging Install Referrer campaign from gmscore with : referrer API v2

first_open event object

event {
          name: first_open(_f)
          timestamp_millis: 1605803612746
          previous_timestamp_millis: 0
          param {
            name: ga_conversion(_c)
            int_value: 1
          }
          param {
            name: ga_event_origin(_o)
            string_value: auto
          }
          param {
            name: _r
            int_value: 1
          }
          param {
            name: engagement_time_msec(_et)
            int_value: 1
          }
          param {
            name: previous_first_open_count(_pfo)
            int_value: 44
          }
          param {
            name: system_app(_sys)
            int_value: 0
          }
          param {
            name: update_with_analytics(_uwa)
            int_value: 0
          }
          param {
            name: system_app_update(_sysu)
            int_value: 0
          }
}

ga_campaign event object:

event {
          name: ga_campaign(_cmp)
          timestamp_millis: 1605803617084
          previous_timestamp_millis: 0
          param {
            name: medium
            string_value: organic
          }
          param {
            name: source
            string_value: google-play
          }
          param {
            name: ga_event_origin(_o)
            string_value: auto
          }
          param {
            name: campaign_info_source(_cis)
            string_value: referrer API v2
          }
}

[google-oss-bot]

I found a few problems with this issue:

• I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
• This issue does not seem to follow the issue template. Make sure you provide all the required information.

[riccardo91]

Same iussue since March and not able to fix with the support. The firebase-analytics sdk is the only one not open source. We don't even have the chance to investigate on our own.

[bobsmits]

Same issue, but with the automated dynamic link events, dynamic_link_app_open and dynamic_link_first_open. The dynamic link attributes are collected correctly seen in Big Query but they are not visible in Firebase -> Analytics -> Conversions or Google Analytics. But logging them manually with the campaign_details event does seem to work for me, the first_open event is attributed(after a day or so). I'm using the rn package. But this seems to be the Java variant. Also building a link via the Google Play store link builder and using that in a dynamic link is working for me. (bom 25.12.0)

[riccardo91]

Same issue, but with the automated dynamic link events, dynamic_link_app_open and dynamic_link_first_open. The dynamic link attributes are collected correctly seen in Big Query but they are not visible in Firebase -> Analytics -> Conversions or Google Analytics. But logging them manually with the campaign_details event does seem to work for me, the first_open event is attributed(after a day or so). I'm using the rn package. But this seems to be the Java variant. Also building a link via the Google Play store link builder and using that in a dynamic link is working for me. (bom 25.12.0)

Do you have utm source in first_open if you export on bigquery? Or just in dynamic link?

[bobsmits]

The first_open is attributed in Firebase and Analytics but i cant find anything in bigquery, i'm not a big query expert by any means so i could be looking in the wrong place.

[riccardo91]

The first_open is attributed in Firebase and Analytics but i cant find anything in bigquery, i'm not a big query expert by any means so i could be looking in the wrong place.

I'll try to export our events to bigquery and explore it. By the way you are already able to see different utm source from firebase dashboard. Our problem is that all source are not tracked even if our configuration is ok. It seems also that the problem is limited to few account.

[aleinnocenzi]

Same issue here

[riccardo91]

Hello,
The problem is definetely on firebase side. 3 days ago something changed and data start to be collected but with a really strange behavior.

this screen has been taken on 22 november with date filetr for "today

"
this screen has been taken on 23 November with date filter "yesterday"

as you can see data disappear from the analytics

[riccardo91]

@rlazo maybe you should tag for for api analytics ?
thanks

[riccardo91]

by the way i noticed a bug in data aggregation.
if you look in the intradays collection you can notice that events have utm_source

SELECT * FROM [project].analytics_151396105.events_intraday_20201123 where Platform="ANDROID" and traffic_source.source="google-play" and app_info.version="2.3.8"

but if i move to eventsn dataset the day after

SELECT * FROM [project].analytics_151396105.events_20201123 where traffic_source.source="google-play" and app_info.version="2.3.8"

all data disappear