Overview
The Universal Data Mapper is a configurable mapping tool within your integrations. It allows you to map lead data (standard and custom fields) to the fields of an external system – including conditions, fixed values, placeholders and automatic type casting.
Step-by-step instructions
- Navigate to Settings → Integrations and open the integration in question.
- Scroll to the “Custom Data Mapping” section.
- Click “Add new Lead Data Mapping” to create a new mapping.
- In the “Parameter” dropdown, select the lead field you want to map (e.g. first name, email or a custom field).
- Add one or more conditions to define how the value should be transferred.
- Save the integration – the mapping is saved along with it automatically.
Which operators / conditions are available?
Each mapping row can contain one or more conditions. The following operators are available:
| Operator | Description | Example |
|---|---|---|
| Just Map (map) | Direct 1:1 mapping of the lead field to the target field. The value is transferred unchanged. | Lead field email → target field contact_email |
| Is Equal (equal) | The value is only transferred if the lead field exactly matches the specified comparison value. Also supports is_empty for empty fields. |
If gender = male → target field anrede = Herr |
| It Contains (contains) | The value is transferred if the lead field contains the specified text. Several search terms can be specified separated by commas. | If city contains Berlin,Hamburg → target field region = Nord |
| Fix Param (fix_param) | Transfers a fixed, static value – regardless of the lead content. Ideal for API keys, campaign IDs or constant values. | Target field source = leadnodes (always) |
How do the input fields of a condition work?
Each condition consists of up to four fields:
-
Operator – Select the type of condition (see table above).
-
Lead value (top left) – Determines which value is compared:
- Lead Value – The actual value of the lead field
- Is Empty – Checks whether the field is empty
- Fix Param – A fixed comparison value
- Custom Value – Your own text input as the comparison value
-
Target parameter (bottom left) – The field name in the external system. Choose from preset fields or enter your own field name (Custom Value).
-
Target value (bottom right) – The value that is transferred:
- Lead Value – The original lead value
- Custom Value – Your own fixed value
- Preset Values – Predefined values of the integration
How can I change the data type of a parameter (type casting)?
By default, all values are transferred as text (string). However, many external systems expect specific data types such as integers or booleans. For this purpose, the Data Mapper offers the prefix system:
In the target parameter (Custom Value), put a type prefix in front of the field name, separated by a dot:
| Prefix | Data type | Input in target parameter | Result |
|---|---|---|---|
int. |
Integer | int.anzahl_personen |
"anzahl_personen": 3 |
integer. |
Integer | integer.menge |
"menge": 5 |
arrayint. |
Integer | arrayint.category_id |
"category_id": 42 |
bool. |
Boolean | bool.is_active |
"is_active": true |
boolean. |
Boolean | boolean.opt_in |
"opt_in": false |
float. |
Decimal number (float) | float.preis |
"preis": 19.99 |
double. |
Decimal number (float) | double.betrag |
"betrag": 100.50 |
string. |
Text (string) | string.plz |
"plz": "01234" |
array. |
Array | array.tags |
"tags": [...] |
unix_timestamp_int. |
Unix timestamp (number) | unix_timestamp_int.created |
"created": 1710240000 |
unix_timestamp_string. |
Unix timestamp (text) | unix_timestamp_string.datum |
"datum": "1710240000" |
Important: The prefix is removed automatically on export – only the field name after the dot appears in the external system.
Automatic boolean detection
If you enter exactly true or false (in lower case) as the target value, the value is automatically transferred as a boolean – without a prefix being required.
Which placeholders can I use?
In target values (Custom Value), you can use placeholders that are automatically replaced with the real lead data on export:
Lead placeholders
| Placeholder | Description |
|---|---|
[lead.id] |
Lead ID |
[lead.salutation] |
Salutation |
[lead.first_name] |
First name |
[lead.last_name] |
Last name |
[lead.street_no] |
Street and house number |
[lead.zip_code] |
Postcode |
[lead.city] |
City |
[lead.phone] |
Phone number |
[lead.email] |
Email address |
[lead.birth_date] |
Date of birth |
Lead type placeholders
| Placeholder | Description |
|---|---|
[lead.type.short_code] |
Short code of the lead type |
[lead.type.name] |
Name of the lead type |
Supplier placeholders
| Placeholder | Description |
|---|---|
[supplier.company] |
Company name |
[supplier.salutation] |
Salutation |
[supplier.first_name] |
First name |
[supplier.last_name] |
Last name |
[supplier.phone] |
Phone number |
[supplier.email] |
Email address |
Buyer placeholders
| Placeholder | Description |
|---|---|
[buyer.company] |
Company name |
[buyer.salutation] |
Salutation |
[buyer.first_name] |
First name |
[buyer.last_name] |
Last name |
[buyer.phone] |
Phone number |
[buyer.email] |
Email address |
Custom data placeholders
For custom fields, use the format: [lead.data.feldname]
Example: If your lead has a custom field stromverbrauch, use [lead.data.stromverbrauch].
Umlauts and special characters in the field name are also supported (e.g. [lead.data.wärmepumpe]).
Can I combine placeholders in text?
Yes! You can embed placeholders in any text. Example:
Sehr geehrte/r [lead.first_name] [lead.last_name] aus [lead.city]
On export, this is automatically resolved to, for example, Sehr geehrte/r Max Mustermann aus Berlin.
Further frequently asked questions
Can I create several conditions per parameter?
Yes. Click the plus icon (+) next to an existing condition to add further conditions. This lets you define, for example, several “Is Equal” rules for different values of the same field (e.g. different salutations depending on gender).
What happens if no condition applies?
If none of the configured conditions for a parameter is met, no value is transferred for this field to the external system. So nothing incorrect is sent – the field is simply skipped.
What does the “Auto-mapped” display under the mapping mean?
Some integrations have predefined standard mappings that are transferred automatically (e.g. first name → first_name). These are shown below the mapping under “Auto-mapped”. You do not need to configure these fields manually in the Data Mapper.
Why is my value transferred as text instead of a number?
By default, all values are sent as text. To send a value as a number, use the prefix system: enter, for example, int.feldname in the target parameter (see the “Type casting” section above). The int. prefix is removed on export and the value is automatically converted to an integer.
Can I map fields from different lead types?
Yes. The parameter dropdown shows you both the standard lead fields (first name, email, etc.) and all custom fields of your lead types. Custom fields are labelled with the short code of the respective lead type (e.g. PV > stromverbrauch).