Issue

You observe that computed traits in Segment are not updating for all your user profiles as expected, even though the corresponding events are successfully arriving in your workspace.

Product

Twilio Segment

Environment

Segment Console

Cause

This behavior can occur when the property keys included in your incoming event payloads have changed and do not exactly match the property keys defined within your computed trait criteria.

Computed traits require an exact string match for both the event name and its property keys to process updates. For example, if your computed trait criteria filters for an event property named product_name, but your application sends the event payload with a property key named products_name, the trait will fail to recognize the data and will not update the user profile.

Resolution

To resolve this issue, align your event payload keys with your computed trait definition by completing the following steps:

1. In your Segment workspace, open the specific computed trait configuration and review the defined criteria to identify the exact property key and value required.

2. Navigate to your source debugger or event logs to inspect the raw payload of the triggered event (such as a Order Created event).

3. Compare the property key in the event payload against the key defined in your computed trait criteria to check for mismatches or typos.

4. Update your application's tracking code implementation so that the event payload uses the exact property key required by the trait criteria. Alternatively, edit the computed trait criteria in the Segment console to match the incoming event property key.