Step-by-step guide to ingest event data from Looker into RudderStack

Looker is a popular Business Intelligence and data analytics platform, that allows you to explore your data for actionable, business-oriented insights.

You can now use Looker as a source of data, where it can be used to send user-related looks to RudderStack. Looker sends the enriched user activities and their associated properties over a period of time to RudderStack. RudderStack can then forward this data to the desired destinations for real-time syncing of the newly created properties and actions.

Getting Started

After creating your views in Looker, you need to set-up Looker actions. Go to your Looker Actions dashboard. One can enable RudderStack Actions on Looker as below:

Adding RudderStack Action Hub Server

RudderStack hosts a Looker Action Hub Server that communicates with your Looker instance. Once you connect the Action Hub Server to your Looker instance by clicking on the Add Action Hub button present at the bottom of Looker Actions dashboard, you can start viewing the three RudderStack actions as above.

The RudderStack Action Hub Server can be found at https://looker-action-hub.rudderstack.com

The authorization token to be used is:


RudderStack-hosted Action Hub: Once the connection is successful, you should start seeing the RudderStack actions

To enable any of the above actions, go to its Settings page where you need to give the Looker Source <write-key> from your RudderStack dashboard and the Rudder Server URL to which the RudderStack actions will be forwarding the user looks data.

Configuring the Write Key and the RudderStack Server URL

RudderStack Actions Overview

RudderStack actions support sending query results to RudderStack as configured above. When defining your columns for the Looker models attached to the look that you will be sending to RudderStack, it's important to tag the user identifier column as email or user_id or rudder_anonymous_id. Additionally, to use the RudderStack Group action, you need to tag your group identifier column as rudder_group_id.

The other user and activity columns will be sent as traits or properties along with the payload that is being sent to RudderStack by the above three actions.

A sample track payload from the look's row data send by RudderStack Track action is as below:

"userId": "test@rcomp.es",
"anonymousId": null,
"properties": {
"tracks_flow.event_2": "Destination_Clicked",
"tracks_flow.event_3": [
"tracks_flow.event_4": [
"tracks_flow.event_5": [
"tracks_flow.event": "User_Logged_In"
"event": "single",
"context": {
"library": {
"name": "analytics-node",
"version": "0.0.3"
"app": {
"name": "looker/actions",
"version": "dev"
"timestamp": "2020-06-18T08:21:01.644Z",
"type": "track",
"_metadata": {
"nodeVersion": "12.13.0"
"originalTimestamp": "2020-06-18T08:21:03.049Z",
"messageId": "node-c33eb51666f6470bf4aa415c7431aba4-ffd5e198-05a1-477a-9c2c-85be30749b8b",
"sentAt": "2020-06-18T08:21:03.050Z"

The column names in your looks are transformed as <Looker view name>.<column name> in the payload sent to RudderStack by the RudderStack actions. If you want to change the names to your end destination needs, you can use our User-Transformer feature to transform them.

Contact Us

If you come across any issues while configuring Looker as a source with RudderStack, please feel free to contact us. You can also start a conversation on our Slack channel; we will be happy to talk to you!