Users

Users represent individuals who engage with your strategy in Mambo. Whether they're customers, employees, partners, sports fans, or citizens, effective user management is crucial for your engagement strategy.

Key user fields

Understanding the essential user fields helps you manage user data effectively:

Unique user ID (UUID)

The UUID is your primary identifier for all API interactions. Choose a UUID that matches your existing unique identifiers, for example:

For customers: email address
For employees: employee number
For partners: partner ID

Example UUID usage:

HTTP

// Creating an activity
POST /v1/activities
{
  "uuid": "employee123",
  ...
}

// Fetching user profile
GET /v1/users/employee123

Member status

The member field controls participation in the engagement strategy:

Set to "Yes" in the UI or true in the API to enable participation
Users can opt-in/opt-out via API if self-selection is desired
Non-members cannot earn points or receive rewards

Personal information

Core identification fields used across the platform:

First name and last name: Displayed in widgets, leaderboards, and activity streams
Email: Used for communications and notifications

Creating users

API integration

The most common method is via the POST User API. This approach:

Integrates with your existing user repository
Enables automated user creation

LDAP or SAML directory integration

Connect to your LDAP or SAML User Directory to:

Enable direct Mambo login
Auto-create users on first login
Support User Portal access

Manual creation

Create test users directly through the users interface to:

Test your engagement strategy
Create sample users for demonstrations
Validate reward configurations

Data privacy considerations

Anonymised users

When handling sensitive data:

Use pseudonymised values for personal fields
Maintain UUID mapping in your system
Use API responses to display correct values in your application

Troubleshooting

Common issues and solutions:

Duplicate UUID: Ensure unique identifiers across your user base
Invalid email format: Validate email addresses before creation
Member status conflicts: Check user opt-in status
Missing required fields: Verify all mandatory fields are provided

Key user fields​

Unique user ID (UUID)​

Member status​

Personal information​

Creating users​

API integration​

LDAP or SAML directory integration​

Manual creation​

Data privacy considerations​

Anonymised users​

Troubleshooting​