User Tracking Identifier Header

In the scenario of a solution where user navigation occurs only in an external system with an independent domain using the REST API or Javascript monitoring to track this user, and other data is accessed in LumisXP using other REST APIs, these other calls would not be able to recognize the user, as monitoring did not occur during navigation in LumisXP itself, so no corresponding cookies were generated for this user in this domain.

In this case, it is possible to use in REST calls an HTTP header containing the tracking identifier of the user so that LumisXP can execute these calls in a context where they can recognize who this tracked user is and thus be able to perform their personalized behaviors accordingly.

For example, when calling a REST that returns a list of news, there could be news published for a segmentation of users that the currently tracked user may or may not belong to. By providing this header, the REST is able to include or exclude published news in such segmentation depending on whether this user belongs to it.

This header is named x-lum-monuid and its value must be the user tracking identifier. There is an example of its usage in the examples of the ready operation in the Javascript API.