User Matching

User matching connects Mapp Intelligence with the Mapp Engage SDK so that the Engage dmcUserId can also be used in Intelligence. This helps align data across both products.

Important
User matching does not work while anonymous tracking is enabled.

Requirements

Mapp Intelligence Android SDK v5.1.5 or later
Mapp Engage Android SDK com.mapp.sdk:mapp-android:6.1.3 or later
Anonymous tracking must be disabled

Configuration options

Method	Description
`WebtrekkConfiguration.Builder(...).setUserMatchingEnabled(true)`	Enables user matching during SDK initialization.
`Webtrekk.getInstance().setUserMatchingEnabled(enabled)`	Enables or disables user matching at runtime.
`Webtrekk.getInstance().getDmcUserId()`	Returns the current Engage user ID when user matching is enabled. Otherwise the SDK returns `null`.

Enable during initialization

val configuration = WebtrekkConfiguration.Builder(trackIds, trackDomain)
    .setUserMatchingEnabled(true)
    .build()

Change at runtime

Webtrekk.getInstance().setUserMatchingEnabled(true)

val dmcUserId = Webtrekk.getInstance().getDmcUserId()

Things to keep in mind

User matching depends on the Mapp Engage SDK providing a dmcUserId.
If user matching is disabled, getDmcUserId() returns null.
If anonymous tracking is enabled, user matching is effectively unavailable.