Skip to content

Remove SQL screenshot (#4166) #4173

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 2, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions src/engage/audiences/sql-traits.md
Original file line number Diff line number Diff line change
Expand Up @@ -182,7 +182,7 @@ For each SQL Trait you create, you can set a compute schedule to query the data

### What identifiers can I use to query a list?

You can query based on `email`, `user_id` or `anonymous_id`. If Segment doesn't locate a match based on the chosen identifier, it creates a new profile. See more below.
You can query based on `email`, `user_id`, or `anonymous_id`. If Segment doesn't locate a match based on the chosen identifier, it creates a new profile. See more below.

### Can I use SQL Traits to create users in Segment? Or do SQL Traits only append Traits to existing users?

Expand Down Expand Up @@ -225,8 +225,6 @@ Segment supports returning only 25 columns. [Contact Segment](https://segment.co

### I'm seeing a duplicate `user_id` error.

![An example of a duplicate user_id error](../images/troubleshoot3.png)

Each query row must correspond to a unique user. Segment displays this error if it detects multiple rows with the same `user_id`. Use a `distinct` or `group by` statement to ensure that each row has a unique user_id.

### I'm seeing some users/accounts in my preview with question marks. What does that mean?
Expand Down