Identifiers

When tracking user behavior, it may be beneficial to use custom IDs that do not map directly to the user types codified in Relewise to begin with. Such IDs can be saved to the User-object in a collection called Identifiers, as a list of key/value pairs.

There is no limit to the amount of identifiers that can be appended to a User-object.

Identifiers are commonly used for something like a nonstandard Customer ID, an ID generated by an Email marketing system, a rewards club membership number, etc.

By appending these to the User-object, Relewise is able to link it to other registered user-types associated with the User-object, and thus serve personalized recommendations and search results on the basis of the user's entire user journey through your site.

Appending additional user IDs to a User-object is made easy in Relewise. Every time a request containing User data is sent to the Relewise API, the User-object automatically gets updated with any new information that may be appended.

This means that any Recommendation or Search request that you serve via Relewise's service automatically binds the userdata together, ensuring that you will serve as much personalized data as possible back to the user.

In terms of the merging of userdata, Relewise prioritizes userdata from strongest to weakest key, starting with:

• Authenticated IDs
• Custom IDs
• Temporary IDs
• Email IDs

All of these are, naturally, optional. If no ID is assigned to a session, the user is considered anonymous.

User-objects may also be updated with the use of the TrackUserUpdateRequest.