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.

SQL Trait Removes Users Between Computations in Segment Engage

Issue

In Segment Engage, users may notice that SQL traits are removed from user profiles between trait computations, resulting in unexpected loss of trait values and users dropping from audiences.

 

Product

Twilio Segment

 

Environment

Segment Console

 

Cause

By default, SQL traits operate in a delta mode. If a user is not returned in the SQL query during a subsequent computation, Segment Engage will remove all trait values for that user. This behavior can lead to traits being nulled out if the user is no longer present in the source database or query results.

 

Resolution

To prevent SQL traits from being removed between runs, we configure the SQL trait as "additive." Additive traits only update with new information and do not null out values when a user or column disappears from the query. Each SQL trait must be individually set to additive; this is not a space-level setting.

Changing a SQL trait to additive ensures that trait values persist even if users are not returned in subsequent query runs. This prevents users from being dropped from audiences due to missing trait values.

If you need to set a SQL trait as Additive, please reach out to support.

Have more questions? Submit a request
We can’t wait to see what you build.
Powered by Zendesk