Users

4 Minutes to read

Print
Share
Dark
Light

Article summary

Did you find this summary helpful?

Thank you for your feedback!

1 Overview

This page explains how to track and enrich user information in Mapp Intelligence. There are three primary use cases:

Improve user identification: Transmit a customer ID (e.g. hashed email address) to improve long-term and cross-device user recognition. This helps reduce fragmentation caused by cookie restrictions or device changes.
Enable user matching with Mapp Engage: IDs and attributes can be shared between Mapp Intelligence and Engage, enabling cross-system user understanding.
Send additional user-specific information: Attributes such as opt-in status or gender can be tracked and used for segmentation and analysis in Mapp Intelligence.

2 Configurable Properties

The following table shows all supported properties, their descriptions, request parameters, and data types.

Parameter	Description	Data available	Data type (Default value)	Request Parameter
id	A unique identifier of the user (e.g., a hashed email address). To comply with data protection requirements, data must be encrypted and ensured unreadable (e.g., using the MD5 or SHA256 hash). If you use an unhashed e-mail address as customer ID, the Smart Pixel automatically generates a SHA256 hash and uses that as the customer ID.	Mapp Intelligence	String	`cd`
emailRID	The email receiver ID of the user serves as a link between Mapp Intelligence and your email tool (e.g., Mapp Engage). If you are using Mapp Engage, it gets automatically filled with the Mapp Engage Contact ID when a user clicks an email. This allows for identifying users between Mapp Intelligence and Mapp Engage.		String	`uc701`
emailOptin	The e-mail opt-in status of the user (True \| False). Only relevant if you are not using Mapp Engage. If you are using Mapp Engage, it gets automatically filled with the Mapp Engage Contact ID when a user clicks an email. This allows for identifying users between Mapp Intelligence and Mapp Engage.		Boolean (false)	`uc702`
registrationEmail	The Email address used to identify the user in Mapp Engage.	Mapp Engage	String	`er1`
registrationGroupId	Provide the group ID in case of a new registration for the user in Mapp Engage.		String	`er2`
registrationMode	Provide the registration method used to register for marketing activities. c (CONFIRMED OPT IN) New contacts receive a welcome message via email when they are added to the group. The contact does not need to confirm the subscription. d (DOUBLE OPT IN) New contacts receive an invitation to join the group via email. The contact must accept the invitation before they are added to the group. Learn more here: Set up Double Opt-in with the Email Channel. o (OPT IN) (default) New contacts are added to the group without notification.		String	`er3`
registrationFirstName	First name of the user to be used in Mapp Engage.		String	`er4`
registrationLastName	Last name of the user to be used in Mapp Engage.		String	`er5`
registrationGender	Gender of the user. u: undisclosed f: female m: male		String	`er6`
registrationTitle	The title of the user to be used in Mapp Engage.		String	`er7`
registrationOptin	Provide information that the user consented to use their data. true: User consent false: No consent Only when set to ‘true’, data will be sent to Mapp Engage.	-	Boolean (false)
category	Custom user information, e.g. hashed identifiers or behavioral segments. Requires setup. It is recommended to transmit hashed personal data that is not evaluated in terms of content (e.g. with the SHA256 hash). If you would like to collect this data for analytical reasons, we recommend that you transmit the data in encrypted form (see How to Implement Server-Side Encryption in Mapp Intelligence).	Mapp Intelligence	Object	`uc[ID]`

2.1 User Categories

User categories allow you to track additional information for user segmentation and analysis. These must be configured in advance. You can track values like hashed newsletter IDs, login types, or marketing segments.

The ID and data type (text/number) are defined during setup.
These values are analyzed in Visitors > User Categories if the type is text, or as metrics if they are numbers.
Values are stored long-term and updated when new values are submitted.

Best practice: Use hashed or encrypted data if personal information is transmitted. Avoid using readable names for sensitive data.

For setup instructions: How to Set Up Categories

3 Implementation Examples

If you do not have automatic page tracking enabled, invoke the track method after adding all relevant tracking information.

import { Component } from '@angular/core';
import { WebtrekkSmartPixelAngular } from '@webtrekk-smart-pixel/angular';

@Component({
    template: `<div>[ ... ]</div>`
})
export class ExampleComponent {
    constructor(private pixel: WebtrekkSmartPixelAngular) {
        this.pixel.customer("user5684798169", {
            emailRID: "",
            emailOptin: true,
            category: {5: "login"}
        }, false);
    }
}

Please add WebtrekkSmartPixelModule to your root NgModule and configure the options before using directives.

If you do not have automatic page tracking enabled, invoke the track method after adding all relevant tracking information.

import { Component } from '@angular/core';

@Component({
    template: `<div [wt-customer-data]="webtrekkData"></div>`
})
export class ExampleComponent {
    webtrekkData = {
        id: 'test@tester.com',
        emailRID: 'emailRID',
        emailOptin: true,
        gender: 1,
        birthday: '19870913',
        country: 'germany',
        city: 'berlin',
        postalCode: '12345',
        street: 'test-street',
        validation: false,
        category: {1: 'foo', 2: 'bar'}
    }
}

Was this article helpful?

What's Next

Campaigns

Table of contents

3 Implementation Examples