Issue
A computed trait in Segment Unify, such as a "last device ID on sign up" trait, appears to show the wrong value. The value in the Profile Explorer or in Profile Sync (for example, in Databricks) doesn't match the value you expect from your event data, or it differs from the same trait in another warehouse table such as BigQuery. It can look like the trait is holding an older value instead of the one from the most recent event.
Product
Segment
Environment
Segment Console
Cause
A computed trait set to return the most recent (last) value of an event property uses the event with the latest timestamp on the profile. If a profile has more than one qualifying event, for example two Signed Up events a year apart, the trait takes its value from the newer one.
Discrepancies usually come from comparing the trait against a different source that uses different logic. A warehouse table or a custom query may pick a value by a different rule, such as the first row returned, a MIN or MAX aggregation, or a filter that leaves out the newer event. That source then shows the older event's value while Segment shows the newer one.
Resolution
- In the Segment Console, go to Unify > Profile Explorer and open the affected profile.
- Note the current value of the computed trait on the Computed Traits tab.
- Open the Events tab and find every event that feeds the trait. Compare their timestamps and property values.
- check that it's set to the most recent value and that it isn't filtered to a subset of events.
- If the trait value matches the property on the event with the latest timestamp, the trait is computing correctly.