2.2. How to read a profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 2.2.3. How to update a profile from the public internet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.2.4. How to search for profile events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.3.3. Accessing profile properties in a context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

multiple IDs. The Unomi ID still exists, but a new index with aliases can reference a single Unomi profile. This enables more flexible integrations with external systems, as well as provide more flexible REST API makes it easy to define, update and remove aliases for profiles. You can read more about profile aliases here. 1.1.2. SCOPES DECLARATIONS ARE NOW REQUIRED Scopes declarations are now required will only load the tracker. To initialize it use a snipper like the following code: Initializing user list service endpoint... Initializing geonames service endpoint... Initializing segment service endpoint

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 2.6.5. Automatic profile merging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . information can then be used to personalize content, derive insights on user behavior, categorize the user profiles into segments along user-definable dimensions or acted upon by algorithms. 1.1.1. ITEMS AND processing events, Unomi progressively builds a picture of who the user is and how they behave. This knowledge is embedded in Profile object. A profile is an Item with any number of properties and optional segments