- 1 Minute to read
- Print
- DarkLight
User Matching
- 1 Minute to read
- Print
- DarkLight
How User Matching Works
User matching allows you to connect data between the Mapp Engage and Mapp Intelligence SDKs, enabling deeper insights and better targeting of users. When user matching is enabled, Intelligence analytics data can be leveraged to enhance user engagement through mobile push notifications, in-app messages, and other features.
Technical Requirements
To use user matching, the following requirements must be met:
Mapp Intelligence SDK version 5.1.5 or later.
Mapp Engage SDK version 6.0.19-rc03 or later (com.mapp.sdk:mapp-android:6.0.19-rc03).
Anonymous tracking must be disabled.
User matching does not work when anonymous tracking is active.
Configuration Fields
Field | Possible Values | Description | Default |
---|---|---|---|
enabled: Boolean | true, false | Enables user matching. When set to true, the Mapp Engage dmcUserID is shared with Mapp Intelligence, allowing the user to be recognized across both products. | false |
Methods
Method | Description |
---|---|
fun setUserMatchingEnabled(enabled: Boolean) = apply { | Enables or disables user matching between Engage and Intelligence. |
Example Usage
Enable User Matching
You can enable user matching during the initialization of the Mapp Intelligence SDK:
WebtrekkConfiguration.Builder(elements, domain)
.setUserMatchingEnabled(true)
WebtrekkConfiguration.Builder(elements, domain)
.setUserMatchingEnabled(true);
Disable User Matching
You can disable user matching at runtime using the following function:
Webtrekk.getInstance().setUserMatchingEnabled(false)
Webtrekk.getInstance().setUserMatchingEnabled(false);
Key Points
User matching enhances targeting by connecting user data between Mapp Engage and Mapp Intelligence.
Ensure anonymous tracking is disabled for user matching to work.
The dmcUserID from Mapp Engage is shared with Mapp Intelligence when user matching is enabled.