Fundamentals

Getting started

Setup

Integrations

Integrations catalog

Strategies

All strategies

Security

Troubleshooting

Compliance

Data Platform

Data Onboarding

Data Specification

Data Types

Attributes catalog

Data Management

Developer API

Forms

Javascript Tag

Insights

Segment

Compare

Track

Activity

Listen

Visualize

Engagement

Activate

Contact

Respond

Schedule

Serve

Activation field mapping

The new Event Activations feature introduces field mapping, allowing you to map fields from Lexer (attributes or events) to destination platforms like Braze (custom events or attributes).

In this article:

Edit a field mapping
Field handling options
Field transformations

Edit a field mapping

Each field that is mapped between Lexer and the destination can be configured by clicking the edit icon displayed here:

Each field mapping can be edited by clicking this button.

In the Edit Mapping sheet you can configure:

Name: the name of the field in the external system
Type: the data type of the field to be sent
Field Handling: what to do when this field is empty
Transformations: optional modifications to make to the data before it’s sent

Edit Mapping sheet allows you to configure field name, type, and transformations.

Each field you send to your destination will need to have a name defined. This will determine how the field is received and displayed in your destination platform. You can either provide the name of an existing field or a new name to create a new field in the destination.

Field type behaves differently depending on the destination platform. Braze, for example, will infer the field type based on the actual data that is sent for each customer, and can be modified at any time in Braze > Data Settings > Custom Attributes.

‍

Field handling options

Field handling controls the behaviour when a specific customer profile or event is missing any value for the field we’re trying to send to your destination.

Option	Description	Example Input	Example Output
Omit Field	Removes the field entirely if its value is empty — the rest of the object is still sent.	{"event": "purchase", "sku": ""}	{"event: "purchase"}
Use Default Value	Replaces an empty field with a specified fallback value.	{"event": "purchase", "currency": ""}	Default Value: "AUD” {"event": "purchase", "currency": "AUD"}
Skip Object	Skips the entire object if the field is empty.	{"event": "purchase", "email": ""}	Nothing is sent — the event is dropped entirely
Skip Parent	Skips the parent object within a collection if the field is empty.	{"event": "purchase", "products": [{ "sku": "123", "price": 19.99 }, { "sku": "", "price": 29.99 }]}	{"event": "purchase", "products": [{ "sku": "123", "price": 19.99 }]}

‍

Field transformations

Field transformations allow you to modify data before it’s sent to your destination. There are three types: Aggregations (used when you need to combine multiple values into a single one), Formatters (which reshape or standardize individual values), and Filters (which remove unwanted or invalid values).

Aggregations

Combine multiple values into a single value, such as picking the first item or summing a list of numbers.

Option	Description	Example Input	Example Output
Sum	Adds together all numeric values in the array.	[5, 10, 2]	17
Sort	Orders the values in ascending order (e.g. alphabetically or numerically).	["banana", "apple", "cherry"]	["apple", "banana", "cherry"]
Pick Nth	Selects the value at a specific index (e.g. 0 for the first item) from the array.	["first", "second", "third"]	Pick Nth: 0 “first”

‍

Formatters

Modify the format or structure of a value, like converting it to lowercase or hashing it.

Option	Description	Example Input	Example Output
Sha256	Hashes the value using the SHA-256 algorithm, commonly used for anonymization.	"hello"	"2cf24dba5fb0a30e26e83b2ac5b9e29e 1b161e5c1fa7425e73043362938b9824”
ISO Currency Code	Validates that the value is a valid ISO 4217 currency code; raises an error if it’s not.	“USD”	“USD”
Lowercase	Converts the value to all lowercase letters.	"EMAIL@EXAMPLE.COM"	"email@example.com"
Uppercase	Converts the value to all uppercase letters.	"email@example.com"	"EMAIL@EXAMPLE.COM"
Capitalize	Converts the value to lowercase and then capitalizes the first letter	“dog”	“Dog”

‍

Filters

Remove values that don't meet certain conditions, such as nulls, empty strings, or negative numbers.

Option	Description	Example Input	Example Output
Positive	Keeps only values greater than or equal to 0.	[-5, 0, 12, -1]	[0, 12]
Negative	Keeps only values less than 0.	[-5, 0, 12, -1]	[-5, -1]
Lowercase	Removes any values that are null or nil.	[nil, "apple", nil, "banana"]	["apple", "banana"]
Uppercase	Removes values that are empty strings (""); keeps all others.	["", "apple", "", "banana"]	["apple", "banana"]

‍

Sequencing transformations

Your transformations will be applied in the sequence displayed on the screen (top to bottom), allowing you to chain transformations for a single value. In the example below, the transformations will be applied in the following order:

Input field is sorted alphabetically (it may contain multiple email values)
The first value is selected from the sorted list
This email value converted to a Sha256 hash format
The Sha256 hashed email is lowercased (the format required by the destination platform)

You can sequence multiple transformations together.

‍

That’s it! We’ll continue to expand field handling and transformation options based on your feedback and use cases. Please reach out to your Success Manager or our Support team with any questions.

Updated:

May 16, 2025