SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site, support.twilio.com, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to help.twilio.com, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

Troubleshooting Disabled Timestamp Traits in the Linked Audience Builder

Issue

When defining conditions in the Engage Linked Audience Builder, you may notice that a custom trait is disabled or greyed out in the dropdown menu. This typically happens when trying to apply a time comparison operator (such as "within last X days") to an object trait where the value is a timestamp, but the trait is not appearing as a valid date trait in the linked audience.

 

Product

Segment 

 

Environment

Segment Console

 

Cause

Only ISO timestamps can be used with time comparison operators. If the timestamp is not a valid ISO timestamp (for example, a trailing Z is missing), Segment won't process the audience in real-time. When a date is passed as a simple string (e.g., "2026-08-10") without the time component and the trailing Z for UTC, Segment parses the value as a standard text string rather than a datetime object. Consequently, the trait is disabled for time-based audience conditions because the system does not recognize it as a valid date.

 

Resolution

  1. Identify the greyed-out trait in the Audience Condition Definition interface.
  2. Review the data payload being sent from your source to verify the current format of the timestamp value.
  3. Update your source implementation to format the timestamp strictly in the full ISO 8601 format. Ensure it includes the time component and the trailing Z (for example, change "YYYY-MM-DD" to "YYYY-MM-DDTHH:MM:SSZ").
  4. Send a new event to Segment with the updated timestamp format.
  5. Once Segment ingests the newly formatted data, navigate back to the Linked Audience Builder. The trait will now be recognized as a datetime object and become selectable for time-based conditions.

 

Additional Information 

Timezones seen in the user interface are based on your local timezone, but are converted to UTC on the backend. Ensure that your source systems consistently output UTC time with the Z designation to avoid unexpected audience qualification discrepancies.

Have more questions? Submit a request
Powered by Zendesk