Skip to content

Commit 215d241

Browse files
authored
Added information that SQL trait name should not be the same name as Identifier
Added the following question and answer to indicate that the name of SQL trait should not be the same name as the identifier. ### Why doesn't the identifier updated by SQL trait shows the correct value found in the column? Ensure that the name given to the SQL trait is not the same name as the identifier or column name from the query. To use SQL trait to update the identifier, the identifier will need to be a column in the query of your SQL trait. The column name in the query of SQL trait should be the one that Identity Resolution use to generate the identifier.
1 parent 5b843fb commit 215d241

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

src/engage/audiences/sql-traits.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -256,3 +256,7 @@ Segment added the compute schedule feature on Feb 8, 2021, so traits created pri
256256
### Why doesn't the value of a SQL trait show in a user profile after a successful sync?
257257

258258
Check that you've configured the identifier that uniquely identifies users in a SQL query (`user_id`, `anonymous_id`, `email`, or `group_id` for account traits) in Identity Resolution settings as an identifier. This ensures the trait is added to the user's profile with the correct identifier. If you don't configure the identifier in Identity Resolution settings, the trait's value is not added to the user profile.
259+
260+
### Why doesn't the identifier updated by SQL trait shows the correct value found in the column?
261+
262+
Ensure that the name given to the SQL trait is not the same name as the identifier or column name from the query. To use SQL trait to update the identifier, the identifier will need to be a column in the query of your SQL trait. The column name in the query of SQL trait should be the one that Identity Resolution use to generate the identifier.

0 commit comments

Comments
 (0)