Token Values, Maps, and Map Groups

Token Values

A token defines the name of a field. A token value
represents a specific value observed for a token, with an
optional comparison operator (for example, equals, not
equals, greater than, less than, regex match, negative
regex match). Token values are the building block for
value-based filtering: they are attached to other records
(for example, a buyer conversion that only pays out when
state equals CA) to express conditional predicates.

Token Value Maps: Conditional Value Mapping

A token value map writes a new key/value into a call's
token data based on a predicate. Each map belongs to an
owner (an outgoing webhook, a buyer conversion, or a map
group) and carries:

• A key to set on the call.
• A value and optional expression that determine what to set.
• A set of token values that form the predicate: if the call's existing tokens match every value comparison, the map fires.

Maps are processed in order. When the system evaluates
maps, it iterates them in sequence, checks each map's
predicate against the call, and accumulates the resulting
key/value pairs.

A map's value type may be "expression," in which case the
expression is evaluated as a formula (numeric) or a
token-interpolated string.

Token Value Map Groups: Organized Sets of Maps

A token value map group is a named container of maps.
Groups exist so that operators can manage a reusable set
of conditional mappings in one place and reference the
group from multiple call-routing contexts.

System Token Values

A distinct set of token keys are classified as
system-only. These cannot be used as regular custom tokens
because the platform reserves the names for internal
purposes. The autocomplete excludes them from results
unless explicitly requested.