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.

Resolving Missing Profile Traits in Linked Audience Builder Dropdowns

Issue

When building a Linked Audience, you may notice that specific custom traits or split audience traits are missing from the condition builder drop-down menu. When attempting to search for the trait manually, the autocomplete menu may display a "No traits found" message, preventing you from clicking to select the desired trait from the list.

 

Product

Segment 

 

Environment

Segment Console

 

Cause

To optimize performance, the Linked Audience builder returns a subset of available values that you can select in the input field drop-down. Specifically, it limits the autocomplete list to the top 65 profile trait key values from the data warehouse. If your workspace contains many custom traits or active audiences, recently synced traits may fall outside of this top 65 list and will not automatically populate in the user interface drop-down.

 

Resolution

You do not need to rely on the drop-down menu to use a trait in a Linked Audience. If the value you are looking for is not listed, you can enter it directly into the input field to bypass the UI limit.

  1. Navigate to your Linked Audience builder and click into the trait selection input field.
  2. Manually type the exact name of the missing trait into the field. Ensure the spelling matches exactly how it appears in your data warehouse, as entered values are case-sensitive.
  3. Ignore the "No traits found" message in the drop-down menu.
  4. Press the Enter key on your keyboard to force the builder to apply the typed text as a condition pill.
  5. Proceed to configure the rest of your condition logic.

 

Additional Information 

  • If you are trying to filter based on a split audience trait, remember that nested objects in arrays are flattened into strings. Because the Audience builder does not support accessing nested objects directly, you must use string operations like contains and does not contain to look for individual values within the flattened string.
  • Ensure that the profile data has successfully synced to the data warehouse through Profiles Sync before you reference it in the Linked Audience builder. If the trait has not successfully synced yet, it will not work as a condition.
Have more questions? Submit a request
Powered by Zendesk