Issue

When syncing Segment Engage audiences to a downstream destination, nested traits included in the audience do not appear in the payload sent to downstream destination. This results in missing user attributes and can cause downstream processes to fail or reject events.

Product

Segment

Environment

Segment Console

Cause

The enrichment platform treats trait names with dot notation as a single key, rather than as a nested object. As a result, nested traits are not properly included in the outgoing event payload.
 

Resolution

Configure trait enrichment to include the entire parent object for any nested trait required downstream. This ensures the nested structure is preserved and traits are available for mapping in the destination. Downstream mappings should reference the nested trait path to ensure correct data delivery.