Open Scino opened 3 years ago
I found a few problems with this issue:
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.
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)
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?
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.
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.
Same issue here
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
@rlazo maybe you should tag for for api analytics ? thanks
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
Hello, the problem seems to be limited to first_open for Android app.
We are passing in the user properties the utm_sorce took from Install Referrer API to validate that aggregation model of google analytics has some iussue.
here how to reproduce it assuming that you are passing the utm_source param as user properties
SELECT a.utm,count(*) FROM
(SELECT user_pseudo_id FROM `[project].analytics_151396105.events_20201122`
where event_name="first_open"
group by user_pseudo_id) AS F
INNER JOIN
(SELECT user_pseudo_id,value.string_value as utm FROM `[project].analytics_151396105.events_20201122`, UNNEST(user_properties)
where key="utm_source" and event_name="screen_view" and value.string_value is not null and value.string_value !=""
group by user_pseudo_id,value.string_value) AS A
ON A.user_pseudo_id=F.user_pseudo_id
group by A.utm
but if you aggregate by traffic_source(totally managed on GA) you can see tha all that data are missing
SELECT traffic_source.name FROM `[project].analytics_151396105.events_20201122`
where event_name="first_open"
group by traffic_source.name
Any resolution to this? Should we use a direct pay store URL with a referrer param?
Is the functionality of Dynamic Link broken? With the introduction of GA4, everything is broken. Request google to help the community here!!
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)
Does anyone have any additional info on this? Is this a bug? Is it a spec? I want some kind of reaction.
Step 1: Describe your environment
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:
AndroidManifest.xml:
Firebase Analytics logs:
(Installing on Emulator from Android Studio)
first_open event object
ga_campaign event object: