我是否需要填写Firebase Analytics的广告标识符表格？
我从Play Store获得了下面的邮件。因此，我们在应用程序中使用Firebase SDK进行分析。 你们可以帮助我们需要填写以下表格。
新的广告ID声明表格
即将到7月，您需要在Play Console中告诉我们您的应用程序是否使用广告标识符。如果您的发布有可能将广告标识符归零的风险，这将使我们提供有用的反馈。在完成广告ID声明表格之前，您将无法创建针对Android 13的发行版。
提醒您，针对API级别33（Android 13）或更高版本并使用广告ID的应用程序必须包括正常的许可com.google.android.gms.permission.ad_id.ad_id在其Android Subtest.xml中。这将阻止您的广告标识符归零。如果您不在清单文件中声明许可，或者使用省略其库清单许可的SDK，则可能会影响您的广告和分析用例。
I got below mail from play store. so we are using firebase sdk for analytics in our app.
Could you guys help we need to fill the below form.
New Advertising ID declaration form coming to Console
Starting July, you'll need to tell us in Play Console if your app uses an advertising identifier. This will let us provide helpful feedback if your release is at risk of having an advertising identifier zeroed out. You will not be able to create releases targeting Android 13 until you complete the advertising ID declaration form.
As a reminder, apps that target API level 33 (Android 13) or later and use advertising ID must include the normal permission com.google.android.gms.permission.AD_ID in their Android Manifest.xml. This will prevent your advertising identifier from zeroing out. If you do not declare the permission in your manifest file, or if you use an SDK that omits the permission from their library manifest, this may impact your advertising and analytics use cases.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
我也有同样的问题，所以我联系了Firebase支持，他们回答说Firebase的Google Analytics（默认情况下）使用广告ID。更多信息： https://support.google.com/firebase/firebase/answer/answer/answer/6318039？ hl = en
I had the same question so I contacted Firebase Support and they replied that Google Analytics for Firebase uses Advertising ID by default. More info: https://support.google.com/firebase/answer/6318039?hl=en
很可能是，但这取决于您使用的确切壁炉库。
我的应用不使用广告，但是我会执行以下firebase库。
这个答案
我检查了我的应用程序合并的清单文件和
com.google.android.gms.permission.ad_id包含在最终清单中。Most likely yes, but it depends on the exact firebase libraries your using.
My app doesn't use ads, but I do the following firebase libraries.
This answer states that
I checked my app's merged manifest file and the
com.google.android.gms.permission.AD_IDwas included in the final manifest.问别人的答案一点也不有帮助。尤其是当您没有“数字分析团队”或“营销团队”作为单个应用程序开发人员时。问题是Firebase是否在内部使用AD_ID来跟踪访客，而不是要问谁。
好吧。我做了一些研究，发现Firebase根本不使用AD_ID。同样，在Firebase插件的代码库中，我无法在某处找到AD_ID字符串 - 仅用于iOS实现。因此，我想（假设大约90％）您可以通过说“不，我不使用AD_ID”来填写声明表格，而当您仅使用Firebase而没有其他跟踪 /广告插件时。
另一个信息：如果您在此处犯错，Google将不会删除您的应用程序。因此，如果您的应用程序实际使用AD_ID，而您不知道，那么最坏的情况是，他们将AD_ID填充零，意味着您会在跟踪或分析访问者/客户的情况下遇到麻烦。
The answer to ask someone else is not helpful at all. Especially when you don't have a "digital analytics team" or a "marketing team" as a single app developer. The question is whether Firebase uses the AD_ID internally to track visitors or not, not whom to ask.
Ok then. I did some research and and I found that Firebase is not using the AD_ID at all. Also in the codebase of the Firebase plugins I was not able to find the AD_ID string somewhere - just for the iOS implementations. So I guess (let's say about 90 %) you can fill the declaration form by saying "no, I am not using the AD_ID", when you are only using Firebase and no other tracking / advertising plugins.
Another information: Google will not remove your app, if you do a mistake here. So if your app actually uses the AD_ID and you don't know it, the worst case which would happen then is that they are filling the AD_ID with zeros, means you would get in trouble "only" with tracking or analyzing your visitors/customers.
您可以从Android视图切换到项目视图，然后导航到App -＆gt;构建 - ＆gt;中间人 - ＆gt; MERGED_MANIFEST-＆GT; androidManifest.xml并检查文件是否包含“ com.google.android.gms.permission.ad_id”。
如果确实如此，则可以在第三方库之一的AndroidManifest.xml文件合并期间将权限添加到文件中。
要识别哪个库将其添加到AndroidManifest.xml中，您可以从build.gradle（App）中顺序删除依赖项，同步项目并重建它。在删除包括com.google.android.gms.permission.ad_id的库后，该许可应从合并的androidManifest.xml中消失。
就我而言，它是Appsflyer，而不是Firebase Crashlytics。
You can switch from Android view to Project view, then navigate to app -> build -> intermediates -> merged_manifest -> AndroidManifest.xml and check if the file contains "com.google.android.gms.permission.AD_ID".
If it does, the permission might be added to the file during the merging of AndroidManifest.xml files from one of the third-party libraries.
To identify which library is adding it to AndroidManifest.xml, you can sequentially remove dependencies from build.gradle (app), synchronize the project and rebuild it. After removing the library that includes com.google.android.gms.permission.AD_ID, the permission should disappear from the merged AndroidManifest.xml.
In my case it was AppsFlyer, not Firebase Crashlytics.