Monterosa Identifiers

A guide to the Identifiers used within Monterosa Audience Profile datasets

Identifiers for Projects, Events, Elements

Within Monterosa / Interaction Cloud, content is organised into a hierarchy as follows:

• Individual questions, polls and votes are “Elements” with an element_id

• Groups of questions together in the same game or Experience are “Events” with an event_id

• A set of Events together are part of a “Project” that represents an environment such as Production or Staging, with a project_id

• Projects are grouped together into distinct functions called “Brands” with a brand_id

• Brands belong to a customer organisation with an organisation_id

User identifiers

Users of Monterosa / Interaction Cloud are assigned one of more unique user identifiers when they connect with the platform. These are explained in detail here:

• sid is a Unique user identifier assigned to both Anonymous and signed-in users when they first connect on a browser or device. It persists across multiple users sessions stored locally on the device. This identifier does not change when the user signs in. Sid is scoped to an instance of the platform and does not change across projects.

• user_id is a Unique user identifier assigned to users who are signed into Monterosa Identify (and therefore signed into a customer SSO). This identifier is not set for all users, but when it is set, the user ID can be cross-referenced in the Users table to find the external_id. Note that user_id is scoped to an individual Project.

• external_id is the unique user_id assigned by a customer Identity platform/SSO service when a user is signed in. The scope of this is global across all projects and instances of Monterosa / Interaction Cloud.

All Monterosa identifiers are stored in UUID format. The format of external_id is determined by the customer Identity service.