Get the current context asynchronously. ContextSDK will automatically figure out, if a context object can be generated immediately (in that case, your callback is instantly executed), or if it needs to run for a little while, until it's ready to execute your callback. The callback will be excuted on the main thread.
Get the current context synchronously. The signal may not include all the information, if the duration wasn't reached.
Be sure that the majority of the times when calling this method, the SDK has already had enough time to reach the duration you've set.
Call this method to obtain a context for the given flow name.
By default the callback will operate in calibration mode and always be called asynchronously within in 3 seconds (or sooner if the app has already been running for more than 3 seconds)
Once a custom model has been created for a flow the callback will only be called if ContextSDK determined it to be a good moment, otherwise this method will simply do nothing, and your callback will not be invoked
Set custom signals that will be used for all ContextSDK events on this instance.
We recommend using this to provide generic information that's applicable to all calls, like any AB test information, or other data that may be relevant to calculate the likelihood of an event.
Please be sure to not include any PII or other potentially sensitive information.
You can overwrite values by using the same key again, and remove them by setting them to null.