Looker Source

Looker is a business intelligence software platform that helps you explore, analyze and share real-time business insights easily. Create custom cohorts of customers in Looker’s powerful and flexible exploration tool and pass your analysis into your marketing tools for activation and engagement using the Looker Source in Segment.

Getting Started

To enable the integration service in Looker, please contact your account representative. They will walk you through the implementation on the Looker side.

From Segment’s end, you will need to create a Looker source, and copy your write key into the Looker integration admin settings.

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: 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.

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.

looker-screenshot

Below is an example of the identify() call Looker will send to Segment for the first user in the Look shown above:

{
  "type": "identify",
  "traits": {
    "name": "Ty Arthur",
    "email": "ty.arthur@segment.com",
    "sessions count": 2
  }
  "userId": "00MWWFOLRcETcTCf"
  }

Send Looks to your Segment Destinations

Customer identifiers to include The end goal of using the Looker Source is to trigger actions in your marketing tools, or Segment Destinations. These Destinations require either a userId or an email with an identify() call. To air on the side of caution, we recommend including userId and email whenever possible.

Below is a chart of all the server side Destinations that will accept identify() calls from Looker and any required identifiers you must pass through. Be sure to include the required trait(s) when setting up your Look, otherwise your user profiles will not make it into your Segment Destinations.

Supported destinations

DestinationEmailUserIdEitherSpecial Note
aboardlyX
activecampaignX
amazon-kinesisX**or anonymousId
amazon-kinesis-firehoseX
amplitudeX
appboyX
appcuesX
attributionX
autopilothqX
blueshiftXX
calqX**or anonymousId
castleX
chameleonX
clearbit-enrichmentXX
clientsuccessX
convertroX
customer.ioXX
delightedXX
driftX
dripX
eloquaX
freshsalesX
gainsightX
goedleX
gosquaredX
heapX
help-scoutX
hubspotX
hullX
indicativeX
infinarioX
intellimizeX
intercomX
iron.ioX
iterableX
kahunaX
kissmetricsX**or anonymousID
klaviyoX
knowtifyX
leanplumX
lyticsX
madkuduX
mailchimpX
marketo-v2X*You must create the custom traits in Marketo and map it in your integation settings before sending the look
mixpanelX
nateroX
nudgespotX
onesignalX
outboundX
pardotX**you need to put the pardot field you’d like to be the unique identifier in your Pardot destination settings
planhatX
pointillistX
promoter.ioXX
ramenX
relayX
responsysX
sailthruX
salesforceX
salesforce-marketing-cloudX
salesmachine*account_uid
satismeterX
segX
sendwithusX
slackX
smyteX
totangoX**Also requires context.groupId
tractionboardX
tray.ioX
treasure-dataX
tuneX
veroX
webhooksX
whale-alertsX
wigzoX
woopraX**or cooke set in destination settings
zaiusX
zendeskX**Also requires a name trait

If you have any questions or see anywhere we can improve our documentation, please let us know or kick off a conversation in the Segment Community!