Q - For analytics if you disable automatic collection by default and enable it programmatically at run-time, will it still collect automatic app install data and app launch events?

[TowhidKashem]

In the docs it's recommended that we set options like these:

    "app_data_collection_default_enabled": false,
    "analytics_auto_collection_enabled": false,

to false in firebase.json, which essentially prevents analytics from sending any outbound requests on app start. Then if we get the user's consent to track them we can programmatically enable analytics in the app like so:

await firebase.analytics().setAnalyticsCollectionEnabled(true);

we can also enable individual config values like:

  await firebase.analytics()..setConsent({
    ad_user_data: true, // `analytics_default_allow_ad_user_data`
    ad_storage: true, // `analytics_default_allow_ad_storage`
    ad_personalization: true // `analytics_default_allow_ad_personalization_signals`
  });

This let's us be GDPR compliant, since we only track things if the user gives consent.

My question is, if we initialize analytics this way, is it still able to detect events like App Launch or able to do attribution like being able to tell if a user has installed the app after clicking on a google ad that we used to advertise our app?

These events seem to occur prior to the JS runtime being initialized, and sine we programmatically enable analytics from there I have a feeling we sacrifice being able to track these things if we don't initialize everything natively via the firebase.json config. Is this the case?