Ability to disable IDFA/IDFV/AAID collection

[max-tgam]

Is your feature request related to a problem? Please describe.
With Apple releasing iOS 14 and putting further pressures on type of information you can collect ideally developer should be able to choose wherever they need to collect IDFA/IDFV/AAID in app. Right now there is no way to opt out from this in React Native SDK without completely disabling mobile context.

Describe the solution you'd like
Ability to opt out from IDFA/IDFV/AAID collection without disabling mobile context.

Describe alternatives you've considered
Completely disabling mobile context is not best as it contains some other useful device information.

Additional context
https://developer.apple.com/support/app-privacy-on-the-app-store/

[colmsnowplow]

Hey @max-tgam - you make a good point. I think we can improve dev experience in the mobile trackers themselves as well as the react-native tracker, I've raised this with the team so we can plan it into our backlog.

Currently, it is technically possible to track the mobile context without these values, but it's quite awkward.

On iOS if you haven't imported the ad support library, the mobile context won't contain the IDFA. If you have, but still don't want it, it's possible via manually changing the build settings for the tracker's package.

On Android it won't be populated unless you have imported the Google Mobile Ads library. I'm not aware of a way to turn it off if that library is present.

Both should hold true for react-native also - hopefully those workarounds are useful to anyone who needs to do this until we can implement a smoother opt in/out mechanism.

[max-tgam]

@colmsnowplow I see good to know about workaround. Thank you!

[adatzer]

Update for v1: (cc @max-tgam )
For the time being, preprocessor definitions are needed for iOS, so there is not yet an option to configure this at runtime.
We have added relevant documentation here describing the steps needed in order to track user identifiers beyond the default tracker behavior.
Leaving the issue open, for future reference. (removing from v1.0.0 milestone).