I am working on a project which doesn't allow us to use the AdSupport Framework. We are wondering what data we will lose / won't have access to with Firebase because of that.
The official documentation only states that "Some Analytics features, such as audiences and campaign attribution, and some user properties, such as Age and Interests, require the AdSupport framework to be enabled. Without this framework, Analytics cannot collect information needed for these features to function properly."
I can't find any additional details anywhere (including here).
I would appreciate the feedback from experts who faced the same situation.
Thanks a lot!
Related
I have a question I can't find any answer in the official documentation nor in the community forums (I found a few threads without clear answers - or old, like this on).
We are planning on building a quite complex GA4 properties structure which are going to require each of our apps to be linked to several GA4 properties.
I know that a Firebase project can't be linked to more than one GA4 property.
Would anyone would have a workaround (if one exist)?
Thanks a lot for your help.
I read Firebase and GA4 official documentation and checked the Firebase projects settings for linking GA4 properties.
Currently working on a CMF for a web platform that uses firebase, Firebase Analytics and AdSense. However firebase's docs on consent and user privacy for the web are either missing a lot of stuff or the api doesn't have granular control over it.
The app config property I'm referring to is not explained by The settable config flag for GDPR opt-in/opt-out. Can anybody explain what it does and controls? And, possibly out of the scope of this question, how to granularly enable and disable data collection on specific firebase services and the related AdSense? Of course gtag commands would solve this but as I'm using gtag via FB Analytics, it's possibly not exposed(certainly not in the docs) and I don't think loading the gtag again is a good solution, if it'd even work.
There is a warning on the Firebase best practices documentation against using Firebase with multi-tenant applications: https://firebase.google.com/docs/projects/learn-more#multi-tenancy
This is what I am most concerned about: "Multi-tenancy can lead to serious configuration and data privacy concerns problems, including unintended issues with analytics aggregation, shared authentication, overly-complex database structures, and difficulties with security rules."
There is also plenty of official Google documentation supporting the use of Firebase for multi-tenancy, for instance: https://cloud.google.com/identity-platform/docs/multi-tenancy-authentication .
Do you know why they would have these conflicting recommendations and examples? Does use of Google Identity Platform fix the core security deficits mentioned in the warning?
I am re-posting this question, with additional clarification in the title, and a few edits/removals from the body, to specify that I am only looking for why this widely used product has this particular warning in its official documentation. I have removed most subjective content. I have no opinion on this that is relevant to the question - I am only looking to understand the warning. It seemed there was one good answer before the previous question was closed, so I will link that here for reference: Why is Google Firebase not recommended by Google in their own documentation for multi-tenant applications?
That does make sense if you manage 2 separate applications which have no relation with each other. Let's say you have an app that manages a school's information and other one is a restaurant management app. Now in this case I don't see any event that the school app might need access to restaurant data.
If you use the same project, then all the firebase services (auth, database, analytics, etc) will be shared among them. It'll be hard for you to separate analytics for each of the app. As the database is shared, you'll have to explicitly separate data of both apps by separating the path in db. (/apps/school for school, /apps/restaurant for restaurant).
That being said, any user registered on the school app can login on restaurant app without creating a new account there as you are sharing the same project among them.
Now if your client pays you a the Firebase costs every month, you cannot distinguish between how much should the school client pay. Now even if both the apps are your, the complexity will increase significantly if you go on using it.
https://firebase.google.com/docs/projects/learn-more#multi-tenancy <-- this explains how "Firebase Projects" works and https://cloud.google.com/identity-platform/docs/multi-tenancy-authentication explains about "Google Identity Kit" multi-tenant auth. So that's not a Firebase-only thing.
I provide some training content (video) on my app and I want to ensure that the content cannot be played from anywhere else (i.e. only available to devices that have downloaded and installed my app). The videos themselves can be stored in either my google cloud or aws.
Is this security capability available from firebase? Is there any code / documentation that may point me in the right direction? My searches so far have been fruitless but I must admit I don't even know what this type of security feature would be called.
Thank you in advance,
Andres
There is no DRM functionality provided by any product in the Firebase platform.
I'm trying to find a way to allow users to create and setup firebase project on their own google account from a client app, and get all their project information, urls and so on.
I took a look at the new project management api but can not figure out how to achieve this.
The management API currently does not support the creation of a new Google Cloud project. You are free to file a feature request for that, but it's worth pointing out that project creation is a complex issue and needs to be gated by abuse prevention measures.
You might also want to look into Google Cloud APIs for dealing with projects.