We're users of Google Analytics on our organization. We've recently received an email from them saying that they're discontinuing Google Analytics for App Reporting next year (info [here])(https://support.google.com/analytics/answer/2621230). At the moment we use Google Analytics on web and apps (android/ios) jointly.
I understand the focus of Firebase is apps, and having all Analytics information together for both Android and iOS.
My question is: is the previous SDK for apps going to disappear altogether?
What would be the standard approach from this point onwards if you also have a web? Add the Firebase SDK on apps, and track with Google Analytics for Firebase, and keep Google Analytics standard SDK on web? I believe this approach would be even more cumbersome since we'll need two interfaces to follow metrics.
From the email, it stated that by OCT 2019, data processing will stop and by Jan 2020, everything will be gone/inaccessible from GA. Hopefully, by then you'll have moved to Firebase Analytics.
GA is still the standard for web and that's not going away.
For Firebase, you can use GTM with it, maybe it might make maintenance easier.
Related
At my company we are making a new iOS + Android app.
We need to get screen views analytics.
At my company doesn't like Firebase Analytics because with the new events analytics (vs the old page views) marketing team can't get enought information from the new events reports.
So I was requested to implement this app analytics using the "old" Google Analytics for Mobile SDK (the one that was used before Firebase) using a Universal Analytics property.
In iOS seems to be working. At least I see myself as active user in Google Analytics. But it's not saving the screen paths.
In Android it doesn't even push the screen views to Google Analytics.
Does anyone knows if Google Analytics for Mobile with a universal analytics property can still be used in 2021?
Or I am obliged to use Firebase Analytics?
For some reason the historical hits data in Analytics Universal Mobile always seems to be accessible in Google Analytics. However Google sent an email to Analytics's users where it communicated that:
We want to let you know that in October 2019 we will begin to sunset our Google Analytics for mobile apps reporting and the Google Analytics Services SDK. We are investing our resources in the latest style of app reporting in Google Analytics that works in conjunction with Firebase – Google’s integrated app developer platform. As such, the following will take place:
In 2019, we will begin to decommission properties that receive data exclusively from the Google Analytics Services SDK.
Data collection and processing for such properties will stop on October 31, 2019.
Reporting access through our UI and API access will remain available for these properties’ historical data until January 31, 2020.
After our service is fully turned down, these properties will no longer be accessible via our Google Analytics UI or API, and their data will be removed from Google Analytics servers. You will receive further notification when this time nears.
At this time, no Analytics 360 properties are impacted by these changes.
Anyway Google want to focus on Firebase (GA4) as the new paradigm for Google’s mobile app (and web) analytics soit is appropriate to use the new data collection model and not the old SDK.
I am new to Google Analytics.
I added Google Analytics to my hybrid app built with react native. I used "#react-native-firebase" to implement GA into my app.
When I added my app to internal testing release on "Google Play Store Console", immediately after some time there were more than 30 plus users showed up on Google Analytics console. This is highly unlikely considering I didn't share the link. Also all these users were in United States with the event first_open_time using wide range of os version and device model.
So my suspicion is Google is internally testing my app before actually rolling out the application.
Has anyone else faced this or something similar to this before? If yes, is there any workaround on how to identify these fake triggers and not log them to Google Analytics? (I assumed that for the proper workflow with the GA these fake triggers would be hindrance, right?)
I use a Google Analytics in my android application, a few days before today I receive an email that means In Oct. 2019 Google will sunset Google Analytics for mobile apps reporting and the Google Analytics Services SDK.
So I decided to migrate to Firebase Analytics.
I am a little bit disgusted because Firebase Analytics doesn't have a feature called 'Behaviour Flow'.
I want to track user behaviour / flow, how can I achieve this with Firebase Analytics?
You can't do exactly the same thing as you did in GA. There is no "behavior flow" that you can turn on or track. Even the "screen views" have turned into just event based.
I think the closest thing out of the box would be using funnels, identifying the funnels that you care about and track those.
Alternatively, you can connect the firebase data to bigquery, export and analyse the data that way, but you probably would need to do a lot of processing.
Firebase Analytics is event-based so they don't support the features that exist in Google Analytics. However; it lets you ingest the raw data into your BigQuery project for free unlike Google Analytics so you can do path analysis either with SQL or use a tool that works on top of Firebase export such as Rakam.
I have followed this tutorial: https://support.google.com/firebase/answer/7378163 and tried to integrate Admob and Firebase Analytics but I can't see any events (ad_click, ad_impression) in Debug View (as described in verify section).
I have tried with both 11.0.1 version and 10.2.3 (beta) with no success (for Firebase Analytics SDK and Mobile Ads SDK dependencies).
I have also added exception (keep) to Proguard file for FirebaseAnalytics and AppMeasurement.
Admob is correctly linked with Firebase - I know that because I already can see some data from Admob in Firebase Analytics in production where I use version 10.2.6.
Is there a reason why this still wouldn't work?
Reply from Firebase support regarding missing Admob events in Firebase Analytics:
"I just heard back from our engineers. They've confirmed that you've configured things correctly, but we're still in the midst of rolling out this functionality, which is why you're only seeing a portion of the traffic. In the near term though, we expect the metrics to converge. "
When I specifically asked about why I don't see events at least in DebugView:
"Same cause - not all devices have this functionality enabled at this time and thus ad_click/ad_impression events are not logged."
Might be that Firebase doesn't refresh their analytics data right away, as, with Google Analytics, it might take a couple of hours, even a day to fully send the reports to the dashboard as mentioned in these posts:
How Long Does it Take for My Firebase Analytics Data to Show Up?
How much time does it take for firebase analytics first report?
To understand latency with Firebase Analytics, there are two potential
delays you need to be aware of:
The time it takes for analytics data on the client to be sent over to
the Firebase Analytics servers.
The time it takes for Firebase Analytics data to be displayed to you in the Firebase console once
it's been received on the server.
I've connected my application to Google Analytics but it shows different data than Google Play. For example at 26th November Google Play shows 262 new installations but in Google Analytics for that day I have 1012 new users. Why there is such a big difference?
There are more bots running to spam Google Analytics report like you may get unexpected lot of user from any country or like if you developed your app for android. In your analytics report you may see the platforms mac, linux etc., but you actually developed your app only for Android or IOS
So Be aware of Spammers
Take a look at this article it may help you how to see your original reports on your tracking ID