Initialization Options
We support an additional TapInitOptions hash to handle aditional configuration. It's current structure is looks like this below (kotlin example):
data class TapInitOptions(
val userAttributes: HashMap<String, Any>? = null,
val clearPreviousAttributes: Boolean? = false,
)
Values and usages
Key | Description | Required? |
---|---|---|
userAttributes | User attributes hash, see usages here | No |
clearPreviousAttributes | Will clear our any attributes stored on tapresearch backend for the current user | No |
userAttributes in TapInitOptions
One potential advantage of passing user attributes at initialization is targeted content being ready faster the first time a user initializes.
Clearing previous attributes
Any time user attributes are sent from the sdk. Either through TapInitOptions or from the sendUserAttributes method, we store them on our end to use for user targeting. clearPreviousAttributes will remove any previous values attributes stored for that user.