Google Analytics offers features which allow you to control the collection and use of Analytics data.
Disable Analytics data collection
In some cases, you may wish to temporarily or permanently disable collection of Analytics data, such as to collect end-user consent or to fulfill legal obligations. Google Analytics offers multiple options for disabling and deactivating Analytics collection. Used together, they support many typical use cases.
Temporarily disable collection
If you wish to temporarily disable Analytics collection, such as to get
end-user consent before collecting data, you can set the value of
firebase_analytics_collection_enabled to false in your app's
AndroidManifest.xml in the application tag. For example:
<meta-data android:name="firebase_analytics_collection_enabled" android:value="false" />
To re-enable collection, such as after an end-user provides consent, call the
setAnalyticsCollectionEnabled()
method of the FirebaseAnalytics class. For example:
setAnalyticsCollectionEnabled(true);
If you need to suspend collection again for any reason, you can call
setAnalyticsCollectionEnabled(false);
and collection is suspended until you re-enable it.
Permanently deactivate collection
If you need to deactivate Analytics collection permanently in a version of
your app, set firebase_analytics_collection_deactivated to true in your app's
AndroidManifest.xml in the application tag. For example:
<meta-data android:name="firebase_analytics_collection_deactivated" android:value="true" />
Disable Advertising ID collection
If you wish to disable collection of the
Advertising ID
in your Android app, you can set the value of
google_analytics_adid_collection_enabled to false in your app's
AndroidManifest.xml in the application tag. For example:
<meta-data android:name="google_analytics_adid_collection_enabled" android:value="false" />
Disable SSAID collection
If you wish to disable collection of SSAID (Settings.Secure.ANDROID_ID) in
your Android app, you can set the value of
google_analytics_ssaid_collection_enabled to false in your app's
AndroidManifest.xml in the application tag. For example:
<meta-data android:name="google_analytics_ssaid_collection_enabled" android:value="false" />
Configure the use of Analytics data
Disable personalized advertising features
If you have linked your Google Analytics project to an ads account or
otherwise enabled an ads integration, or opted into
data sharing,
your Analytics data may be eligible for use in personalized advertising.
This means for instance, that you may use collected events such as first_open
to create and deploy audience lists for remarketing unless you indicate that
such data is not available for personalized advertising.
To programmatically control whether a user's Analytics data should be used for personalized advertising, set the appropriate default behavior in the app's AndroidManifest.xml file, and then use the methods described below to override that default behavior.
To set the default personalized advertising behavior, specify the following
field in your app's AndroidManifest.xml in the application tag:
<meta-data android:name="google_analytics_default_allow_ad_personalization_signals" android:value="false" />
You can also control whether data collected from end users may be used for ads personalization via the ads personalization setting, found in Google Analytics’ Property settings.
Re-enable personalized advertising features
To re-enable personalized advertising features for a user at run-time, such as after an end-user provides consent, use thesetUserProperty
method as shown below:
setUserProperty( ALLOW_AD_PERSONALIZATION_SIGNALS, "true" );
If you have chosen to temporarily disable analytics collection (for example, until an end-user provides consent), and you want to control personalized advertising features upon re-enabling analytics collection for a user, ensure that your call to specify this setting precedes your call to re-enable analytics collection. For example:
setUserProperty( ALLOW_AD_PERSONALIZATION_SIGNALS, … );
setAnalyticsCollectionEnabled(true);
Confirm your settings
When ad personalization signals have been disabled for a user via one of the mechanisms defined above, subsequent event bundles logged from that user's device will contain a user property named "non_personalized_ads" with a value of 1 to indicate that events in that bundle are not available for personalized advertising. Disabling personalized advertising does not affect the use of the data for measurement purposes, including reporting and attribution.
See your configuration changes
Once you've made changes to your Google Analytics settings, the SDK downloads the changes. The process is fast and seamless, so you can quickly test your changes. When you make changes in Analytics, it may take a few minutes to deploy in your app. If your app is live, the full deployment process may take up to one hour to complete.