Users Data

The table below specifies data to be provided in the Users migration template.

Mandatory fields are marked with an asterisk (*).

Please ensure your data adhere to the data specification guidelines before submission.

Column Name

Format

Description

Example

First Name

string

First name of the customer (user).

Joe

Last Name

string

Last name of the customer (user).

Doe

Email*

string

The email address of the customer. It is a unique user identifier in Cleeng.

[email protected]

Locale*

string

Customer language and text formatting. See Cleeng Help Center for the current list of supported values.

en_US

Last login

YYYY-MM-DD

Last login date Default: current date

2025-09-30

Create date

YYYY-MM-DD

Customer account creation date Default: current date

2025-09-30

Country Code*

string

2-letter country code, ISO 3166-2 format, used for reporting on a user level and to calculate specific TAX based on the country

US

Currency*

string

The currency code in which a user is charged and must be from Cleeng’s supported currencies list.

Default: EUR

USD

IP Address (Mandatory for US and CA for Tax Collecting)

string Both IPv4 and IPv6 supported

IP address of the customer. Required for customers in the US and Canada to accurately calculate state taxes. Not required for customers based outside the US and Canada.

Timezone

string

Customer timezone Default: Europe/Amsterdam

America/New_York

External ID (Mandatory only for integrations with third-party identity systems)

string

Mandatory only for integrations with third-party identity systems such as Gigya, Okta, Microsoft ADB2C and enables connection between external identity management and Cleeng.

Password Hash

string

Optional for password migration


📘

Protip

  • Before export, verify that all locales and currencies in your user data are supported by Cleeng to avoid import failures. Users with unsupported locale or currency values will not be migrated to Cleeng.
  • In cases where in-app subscribers use currencies not included in the supported list, it is possible to default their currency to USD. This approach will not affect the actual amount they are charged as they are charged by app stores. This workaround ensures that users are migrated and continue to pay the correct value while allowing the system to handle unsupported currencies seamlessly.