---
title: "Mapp Intelligence: Language, Country and Time Zone for Engage Registrations"
slug: "mapp-intelligence-language-country-and-time-zone-for-engage-registrations"
description: "Mapp Intelligence passes language, country and time zone to Mapp Engage at registration, via Smart Pixel, SPA integrations and server-side libraries."
status: "new"
updated: 2026-11-02T15:59:59Z
published: 2026-11-02T15:59:59Z
canonical: "docs.mapp.com/mapp-intelligence-language-country-and-time-zone-for-engage-registrations"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mapp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Mapp Intelligence: Language, Country and Time Zone for Engage Registrations

**02 November 2026** You can now pass the language, country and time zone of a user to Mapp Engage when the user registers through your tracking. New contacts arrive with the correct language and country, so you can localize every message from the start, including the welcome message. The fields are optional, and existing setups keep working without changes.

---

## Summary of changes

- **Smart Pixel and single-page application integrations**: The registration data accepts three new optional fields. See [Users](/v1/docs/intelligence-smart-pixel-users).
- **Server-to-server libraries**: The Java, PHP and Node.js libraries support the same fields. See the Mapp Engage data object of the [Java Library](https://docs.mapp.com/docs/mapp-engage-data-object-java-library-s2s), the [PHP Library](https://docs.mapp.com/docs/mapp-engage-data-object-php-library-s2s) and the [Node.js Library](https://docs.mapp.com/docs/engage-2).

---

## New registration fields

| Field | Content | Format |
| --- | --- | --- |
| `registrationIsoLanguage` | Language | Two-letter ISO 639-1 code, for example `de` |
| `registrationIsoCode` | Country | Two-letter ISO 3166-1 code, for example `DE` |
| `registrationTimezone` | Time zone | IANA time zone name, for example `Europe/Berlin` |

Mapp Engage stores language and country in the standard profile attributes ISO Language Code and ISO Country Code. You can use them right away in segments, for example to [differentiate audiences by country and language](/v1/docs/differentiate-audiences-based-on-country-and-language). The formats correspond to the [Attribute Reference](/v1/docs/csv-format-for-contact-imports#attribute-reference) of Mapp Engage.

---

## Availability

The new fields are available in the following releases:

- [Smart Pixel 6.12.1](https://docs.mapp.com/docs/smart-pixel-changelog)
- [Google Tag Manager template 1.6.3](/v1/docs/changelog-gtm)
- [Angular 1.4.4 and 2.4.4](https://docs.mapp.com/docs/angular-changelog)
- [React/Next 1.5.5](https://docs.mapp.com/docs/react-next-changelog)
- [Vue 2.1.4](https://docs.mapp.com/docs/vue-changelog)
- [Java Library 1.1.1](https://docs.mapp.com/docs/java-changelog)
- [PHP Library 2.1.0](https://docs.mapp.com/docs/php-changelog)
- [Node.js Library 1.0.0](https://docs.mapp.com/docs/nodejs-changelog)

If you load the Smart Pixel from the Mapp CDN, you receive the Smart Pixel update automatically. The integrations and libraries have to be updated to the versions listed above. The server-to-server library releases also contain other changes, some of which affect existing setups. Check the upgrade notes in their changelogs before you update.

For background on creating contacts in Mapp Engage through tracking, see [Methods and Use Cases for User Matching](https://docs.mapp.com/docs/mapp-cloud-user-matching-methods-and-use-cases).