enablePerformanceMonitoring vs features

I'm confused by the API for enablePerformanceMonitoring vs. the API for features. Why is `enablePerformanceMonitoring` a separate property on the `config`, and not a part of the `features` enum? Is it somehow different?

If I do not set `enablePerformanceMonitoring` to true on my config, but I do give consent for performance monitoring, will Countly not do any performance monitoring until I set it on the config?



1 comment
  • Official comment

    Hello, if 'enablePerformanceMonitoring' would not be set to 'true' but consent would be given, APM functionality would not work.

    Consents are kinda a secondary level "check" as all features can also be used/enabled without using consent.

    The 'features' array is an older way of enabling features.

    Comment actions Permalink

Please sign in to leave a comment.