Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Specific consent for remote config
See original GitHub issueRequest:
- The ability to turn on remote configuration without any other features.
Use case:
I plan to use Countly to provide remote configuration. I also take GDPR consent for analytics. I want to be able to turn on remote config without enabling any analytics.
Currently consent can be recorded for a fine-grained range of analytics collection.
["sessions", "events", "views", "scrolls", "clicks", "forms", "crashes", "attribution", "users", "star-rating", "location", "apm"]
http://countly.github.io/countly-sdk-web/countly.js.html#line103
Consent for remote config does not have a named feature. Instead it is assumed when consent has been added for at least one feature. http://countly.github.io/countly-sdk-web/countly.js.html#line999
Suggestion:
- A new consent feature “config” be added to the list of available features.
- This consent be used when providing remote config, instead of
Countly.check_any_consent().
Workaround:
Countly.group_features({
config: ["unrecognised feature to allow remote config"],
})
Countly.add_consent("config")
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hello, sorry for delay, yes we are going with that for next release 😃
This was added here: https://github.com/Countly/countly-sdk-web/commit/9f8a08b69b76e6227e2c008960ff08ded2f836f4