User tracking in Mapp Intelligence enables you to identify visitors based on unique customer information rather than relying solely on cookies. This ensures consistent user recognition — even when cookies are deleted, browsers are switched, or users access your website from different devices.
Note on Data Privacy
Always transmit personal information in encrypted or hashed form.
Mapp recommends using SHA256 or MD5 hashing to ensure compliance with data-protection standards.
User data can be sent to Mapp Intelligence after a successful login, registration, or purchase.
Each user is identified through a Customer ID and can optionally be enriched with User Categories for segmentation and analysis.
Customer ID
The Customer ID serves as a unique identifier for a user.
It can be:
a customer number from your CRM or shop system, or
the user’s email address.
Note
If an email address is used, it must be encrypted or hashed before transmission to comply with data-protection requirements. Mapp recommends using SHA256 or MD5 hashing to ensure that the email address cannot be read directly.
If a plain (unhashed) email address is sent, the library automatically converts it to a SHA256 hash before storing it as the Customer ID.
User Categories
User Categories capture additional attributes about a user — for example, loyalty level, subscription type, or login source. They allow you to enrich user profiles with contextual or behavioral data for deeper segmentation and analysis.
They must also be configured in Mapp Q3 before tracking. Find more information here.
When implementing, include the ID number and the value as a string.
Method | Description | Where to configure * | Where to analyze |
|---|---|---|---|
constructor | Initializes a user object and defines the unique Customer ID. | – | Visitors > User Relationship Management > Custom Visitor ID |
setId | Sets the Customer ID — a unique identifier from your CRM, shop system, or hashed email address. | – | Visitors > User Relationship Management > Custom Visitor ID |
setCustomIdentifier | Defines a secondary unique identifier for the user (optional). | – | Visitors > User Relationship Management > Custom Visitor ID |
setEmailRID | Transmits the user’s email receiver ID for linking marketing communications with behavior data. | – | Visitors > User Relationship Management > [Name of User Category] |
setEmailOptin | Tracks whether the user has granted email permission (opt-in status). | – | Visitors > User Relationship Management > [Name of User Category] |
setGender | Tracks the user’s gender (1 = male, 2 = female). | – | Visitors > User Relationship Management > [Name of User Category] |
setValidation | Enables validation for overwriting existing user category values. | – | Visitors > User Relationship Management > [Name of User Category] |
setCategory | Adds or updates a User Category to describe additional user attributes. User Categories must be created beforehand in Mapp Intelligence. | UC > New Category | Visitors > User Categories > [Name of Category] |
* Configuration Path Abbreviations:
UC = Mapp Q3 > Configuration > Categorization > URM Categories > …
constructor
const mappCustomerData = new MappIntelligenceCustomer();/**
* @param i Use this to transmit a unique identifier of the user
*/
const mappCustomerData = new MappIntelligenceCustomer(i: string);setId
/**
* @param i Use this to transmit a unique identifier of the user
*
* @return this
*/
mappCustomerData.setId(i: string);setEmailRID
/**
* @param eRID Use this to transmit the e-mail receiver ID of the user
*
* @return this
*/
mappCustomerData.setEmailRID(eRID: string);setEmailOptin
/**
* @param eOptin Use this to transmit the e-mail opt-in status of the user
*
* @return this
*/
mappCustomerData.setEmailOptin(eOptin: boolean);setGender
/**
* @param g Use this to transmit the gender of the user (1 = male | 2 = female)
*
* @return this
*/
mappCustomerData.setGender(g: number);setValidation
/**
* @param v Overwrites existing URM categorize
*
* @return this
*/
mappCustomerData.setValidation(v: boolean);setCategory
/**
* The optional category (User Relation Management) can be used to categorize a customer. URM categories must be
* created in the tool first of all.
*
* @param i ID of the parameter
* @param value Value of the parameter
*
* @return this
*/
mappCustomerData.setCategory(i: number, value: string);const mic = new MappIntelligenceConfig(
"111111111111111",
"analytics01.wt-eu02.net"
);
const mit = new MappIntelligenceTracking(mic);
const mappCustomerData = new MappIntelligenceCustomer();
mappCustomerData.setId("user5684798169")
.setEmailRID("")
.setEmailOptin(true)
.setGender(1)
.setBirthday("~!jX7E0tqd3BTIXVNX+jJnOQ==!~") // 19900215 [ JJJJMMDD ]
.setCountry("~!epld8YhkcFY=!~") // Germany
.setCity("~!9Hn50gRUKpw=!~") // Berlin
.setPostalCode("~!dZVg2aMOE2Q=!~") // 10115
.setStreet("~!vOSHjdTscdK8BCw0pNyQ2lcLKg5PY70N!~") // Robert-Koch-Platz
.setValidation(true)
.setCategory(5, "login");
mit.track((new MappIntelligenceDataMap()).customer(mappCustomerData));