After importing our Firebase app events in Google Ads as conversions, their status stays at "no recent conversions". The events are recordeding fine in Firebase.
Both our native iOS and Android app are implemented, but none show conversions in Google Ads
The package name of one of our apps was updated
We unlinked Google Ads from Firebase and linked it again, but that didn't work either
We are talking about custom events (an in-app action) and native events (like first open)
It seems like we can't really delete conversions. We can delete and re-enable, but can't "start over".
How can we make recording our events as conversions work?
The answer was hiding in the comment made by #Akif Demirezen.
On Firebase, go to project settings
Under "Your apps" section, make sure to fill the "App Store ID" field, you can find this information on your App Store connect page, under Apple ID
Related
Currently I have a setup where the Google Analytics events for the Android and iOS apps were being tracked on the Firebase console itself (which I believe is called UA). But that data is not visible at all in the Analytics Console. Now I want to move to GA4, such that I can use the latest features. I also want our existing data which has been captured under UA to be visible in the Analytics console in the GA4 property. I have tried creating a GA4 property, but over there, it was asking to add a new Data Stream, which is leading to creation of a new Firebase Project, and thus would require us to move all our other functionalities like Firestore to the new project as well, which is not feasible. Is there a way so that all my existing and new events which are fired from the Apps are registered in the Analytics Console, be it using UA or GA4 (GA4 would be preferred).
PS - I found ample number of articles to use tag id for Websites, but none for Android or iOS Apps.
We have a web app that users log into using Firebase Auth. According to our the authentication section of our firebase console, we have 690 user that have created accounts, and we believe that is correct.
According to our Firebase Analytics console, we have 2,100 new users in the past 90 days. I think I understand that Firebase Analytics tracks users with a device ID (?). So, if this were a iOS app, an uninstall and install would trigger a a new user counted in analytics. But, how does this work on a web app? Cookie? Some kind of browser id? A session?
So, I think if we want to track unique users accurately, we would use the set the user id, with this:
https://firebase.google.com/docs/reference/js/firebase.analytics.Analytics#setuserid
Which according to the docs linked above, 'Use gtag 'config' command to set 'user_id'. So it does this: https://developers.google.com/analytics/devguides/collection/gtagjs/cookies-user-id#set_user_id
Which allows the users to be tracked across sessions. Therefore, users should not double count.
Notice that the setUserId section in the firebase analytics docs does not have a web section (although the setUserID function does exist in the javascript sdk as shown tow links above) https://firebase.google.com/docs/analytics/userid
So... would it then work to get the user id (uid) when they log in (https://firebase.google.com/docs/reference/js/firebase.User). And then use the setUserId method to set the id?
It's unclear because the documentation does not seem to be in one source. I am just trying to put it all together
You are correct that you can use the setUserId API (across iOS, web and Android) in order to identify the same user across platforms. Note that you'll need to:
Set the default reporting identity to "By User-ID then Device" in the Reporting settings for Google Analytics in the Firebase console (see attached screenshot and docs for more info).
Make sure you are following the Privacy Policy when using the User ID.
It is known that users must explicitly consent the use of tracking tools like Google Analytics, Firebase etc. by the app, I am wondering if it possible to track dropouts on the first screen since as I understand analytics tracking can only be activated once the user allowed this when starting the app for the first time. I would like to know if there are users that exited the app on the first screen before consenting the tracking and decided to uninstall the app after that.
Google Analytics for Firebase provides an API for disabling Analytics collection temporarily before getting a user consent
setAnalyticsCollectionEnabled(true);
You can log this as a event with int parameters 0 and 1 (or any other way you may want). Basically giving you the control and visibility of what you are looking for here.
My Android app right now uses Google Analytics.
However, I want to add Firebase Analytics as well.
Let's say the new version of the app now has FA.
Will the 'first_open' event be triggered for old users and mark them as they've first opened the app only now?
Is there any possibility to link FA with GA and get the correct 'first_open' for the old users?
Should I introduce my own 'user property' to mark users that had a previous version of the app when they first run the new version?
Maybe a tricky question: If a user installs the new version, and FA attempts to set such 'user property' (only once ever), but the user doesn't have an Internet connection at this moment. Will this 'user property' be sent to FA somehow in the future?
Thank you!
The current Firebase Analytics library will report first_open when an app with Firebase Analytics is first launched. This includes launch after the app is update from version w/o Firebase to version with Firebase. We are working on excluding first_open from users after update to app with Firebase but this change is not in yet.
FA is not aware of GA in the app and there is no way to tell FA if this is first_open after upgrade vs first_open after app install. This will be automated in one of the next releases as I mentioned earlier.
Setting user property will not work as first_open is recorded early in the app life cycle and before you can get access to FA singleton. You will not have a chance to set the user property before first_open event is recorded.
Setting user property is orthogonal to the app connectivity. All events logged before the property was set will not have it, all event logged after the property is set will have the property set. Connectivity only impacts when the data can be uploaded, not the content of the data. If your app is running on device that is offline the data will be uploaded when the device gains connectivity. The data itself is almost identical.
I'm still trying to get my free game app discovered, and notice that most of my new downloads are coming from '(not set)' according to Google Analytics/Aquisition/App Marketplace. And this despite a 'This report has been filtered to include only data where there are values for "App Installer ID" dimension' message on the page. According to the docs:
"A marketplace must support the App Installer ID to be recognized by Google Analytics. Not all marketplaces support the App Installer ID, which is what Google Analytics needs to recognize a marketplace. Traffic that comes from a marketplace that Google Analytics can’t identify appears in the report as (not set)."
I've only submitted my app to Google Play. Should I be concerned about these apparent rogue downloads? What marketplace are they coming from?
Several sites offer direct APK file downloads, one of the biggest being 'Apkmonk' where I found my free game app posted. As reported from the updated Google Analytics 'Acquisition/App Marketplace' graph, I now get 50-350 new user downloads a day from unidentified markets, compared to about 1-5 a day from Google Play (com.android.vending). I had to adjust the support code provided in the docs and examples (i.e. Trivial Drive) for InApp purchases and Google Play Services (particularly the IabHelper file) to support players who had neither Google Play Services nor Google Play Store installed on their devices. They all appeared to get null pointer exceptions on starting the app before I adjusted the code. I experimented uninstalling Google Play Services and turning off Google Play Store on my test device to find null pointer and other crash points in the support code.
As far as app performance in non-Google acquistion markets, I get banner and interstitial ad serves, but that's it. No leaderboard or achievement posts, promo redemptions or InApp purchases, which makes sense. I only get .00-.02 cents per banner or interstitial ad click in these markets, with demographics mostly US and India.