Skip to content

remove erroneous info #1956

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.

Sign up for GitHub

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 3 commits into from
Oct 5, 2021
Merged

remove erroneous info #1956

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
10fa8a2
Merge pull request #1954 from segmentio/develop
Oct 5, 2021
9007bc8
remove erroneous info
nomad-david Oct 5, 2021
60eb080
Apply suggestions from code review
stayseesong Oct 5, 2021
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
7 changes: 5 additions & 2 deletions src/connections/sources/catalog/cloud-apps/looker/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,9 +12,12 @@ From Segment's end, you will need to create a Looker source, and copy your write

### Defining Looks

Using this Source, Looker will send Look (query) results into Segment as `identify` calls. This is the only API method that Looker sends to Segment. Any user trait that you include as a column in your Look will be included as a user trait on these identify call. **Note: Arrays are not currently supported. Only properties that are strings or numbers are supported.**
Using this Source, Looker sends Look (query) results into Segment as `identify` calls. Any user trait that you include as a column in your Look will be included as a user trait on these identify call.

Note: When you set up your Look and generate new user traits (column names), avoid using trait names that may already exist in your marketing tools. If you create a new user trait in Looker (e.g. "churn risk") and that trait already exists in your tools, syncing the user profile to the downstream tool will override the existing trait value with the new one.
> note ""
> **NOTE:** Segment doesn't support arrays. Segment supports properties that are strings or numbers.

When you set up your Look and generate new user traits (column names), avoid using trait names that may already exist in your marketing tools. If you create a new user trait in Looker (e.g. "churn risk") and that trait already exists in your tools, syncing the user profile to the downstream tool overrides the existing trait value with the new one.

Below is an example of a cohort of users in Looker who have been active on toastmates.com (example website) at least once in the last 30 days.

Expand Down