After you've created an embed — which can be donepublicly,privately, withsigned embedding, or through theAPI — you can interact with those iframes using JavaScript. You can make your page more dynamic based on the status of the embedded item, and you can even make changes to the embedded item from your web page.

Be aware that Looker doesn't control the order in which browsers dispatch events to web applications. This means that the order of events is not guaranteed across browsers or platforms. Be sure to write your JavaScript appropriately to account for the event handling of different browsers.

You can use JavaScript in one of the following ways for Looker embedded content:

• Using Looker's embed Software Development Kit (SDK), described on theEmbed SDK documentation page
• Using JavaScript events, described in theAccessing events in JavaScript section on this page

Preparation

Before you can interact with the embedded iframe, follow these steps:

• Add an ID to the iframe.
• Add the embed domain to the iframesrc attribute.
• Add the embed domain to the allowlist.

Adding an ID to the iframe

Later, when youretrieve data from the iframe, you'll need to validate that the information you're working with has actually come from Looker's iframe. To facilitate this, be sure to add an ID to your iframe, if you haven't done so already. In the following example, you set the ID tolooker by addingid="looker" to the iframe:

<iframeid="looker"src="https://instance_name.looker.com/embed/dashboards/1"></iframe>

Adding the embed domain to the iframesrc attribute

In the iframe'ssrc attribute, include the domain where the iframe is being used. In the following example, you can specifymyownpersonaldomain.com as the domain by adding?embed_domain=https://myownpersonaldomain.com" to the end of the URL in thesrc attribute:

<iframeid="looker"src="https://instance_name.looker.com/embed/dashboards/1?embed_domain=https://myownpersonaldomain.com"></iframe>

If you're usingsigned embedding, make sure you add theembed_domain to theembed URL.

If you're using theEmbed SDK, addsdk=3 to the end of the embed URL. Thesdk=3 parameter indicates that the SDK is present and that Looker can take advantage of additional features that the SDK provides, such as passing JavaScript events between the Looker iframe and your domain. The SDK can't add this parameter itself because it is part of the signed URL. For example:

<iframeid="looker"src="https://instance_name.looker.com/embed/dashboards/1?embed_domain=https://myownpersonaldomain.com&sdk=2"></iframe>

Adding the embed domain to the allowlist

Finally, you'll need to add the domain where the iframe is being used to the allowlist on theEmbed page of Looker'sAdmin panel by following these steps:

1. In theEmbedded Domain Allowlist field, enter the domain where the iframe is being used, and then press the Tab key so that the domain appears in a box within the field.

   Important: Don't include a trailing slash (/) in the domain URL.

2. ClickUpdate.

You can use the* wildcard in the allowlist to create a domain pattern. For example,https://*.myownpersonaldomain.com would allow bothhttps://analytics.myownpersonaldomain.com andhttps://data.myownpersonaldomain.com.

If you're usingcookieless embedding with Looker 23.8 or later, the embed domain can be specified when the cookieless session is acquired. This is an alternative to adding the embed domain to the allowlist using theAdmin > Embed panel. Review thesecurity best practices if you decide to take advantage of this feature.

Retrieving data from the iframe

After completing thepreparation steps, you can access the events that are passed between the Looker iframe and your domain by listening forpostMessage events.

The embedded iframe can create a few event types, as described in theEvent type reference section on this page.

Accessing events in JavaScript

Here is an example of listening for these events in JavaScript, and then logging the events to the console:

window.addEventListener("message",function(event){if(event.source===document.getElementById("looker").contentWindow){if(event.origin==="https://instance_name.looker.com"){console.log(JSON.parse(event.data));}}});

Here is an example of listening for these events in jQuery, then logging them to the console:

$(window).on("message",function(event){if(event.originalEvent.source===$("#looker")[0].contentWindow){if(event.origin==="https://instance_name.looker.com"){console.log(JSON.parse(event.data));}}});

Event type summary table

The following table summarizes event types. Select an event type to see the details about that event.

Event type reference

The embedded iframe can create many different types of events:

dashboard:loaded

On dashboards where the tiles are not set to auto-run, this event is created after a dashboard and its elements have loaded but before queries are run.

type:"dashboard:loaded",status:"complete",dashboard:{id:1,title:"Business Pulse",canEdit:true,dashboard_filters:{"date":"Last 6 Years","state":""},absoluteUrl:"https://self-signed.looker.com:9999/embed/dashboards/1?embed_domain=https%3A%2F%2Fself-signed.looker.com%3A9999&date=Last+6+Years&state=",url:"/embed/dashboards/1?embed_domain=https%3A%2F%2Fself-signed.looker.com%3A9999&date=Last+6+Years&state=",options:{layouts:[{id:1,dashboard_id:1,type:"newspaper",active:true,column_width:null,width:null,deleted:false,dashboard_layout_components:[{id:1,dashboard_layout_id:1,dashboard_element_id:1,row:0,column:0,width:8,height:4,deleted:false},{id:2,dashboard_layout_id:1,dashboard_element_id:2,row:0,column:8,width:8,height:4,deleted:false}]}],elements:{1:{title:"Total Orders",title_hidden:false,vis_config:{type:"single_value",font_size:"medium",title:"Total Orders"}},2:{title:"Average Order Profit",title_hidden:false,vis_config:{type:"single_value",title:"Average Order Profit"}}}}}

dashboard:run:start

This event is created when a dashboard has begun loading, when its tiles will start loading and querying for data.

type:"dashboard:run:start",dashboard:{id:23,title:"My Dashboard",canEdit:true,url:"/embed/dashboards/...",absoluteUrl:"https://instance_name.looker.com/embed/dashboards/...",dashboard_filters:{"Date":"Last 28 days","Total Orders":"Greater than 100"}}

dashboard:run:complete

This event is created when a dashboard has finished running and all tiles have finished loading and querying. This event is created whether or not all tiles load successfully.

type:"dashboard:run:complete",status:"complete",dashboard:{id:23,title:"My Dashboard",canEdit:true,url:"/embed/dashboards/...",absoluteUrl:"https://my.looker.com/embed/dashboards/...",dashboard_filters:{"Date":"Last 28 days","Total Orders":"Greater than 100"}options:{layouts:[{id:1,dashboard_id:1,type:"newspaper",active:true,column_width:null,width:null,deleted:false,dashboard_layout_components:[{id:1,dashboard_layout_id:1,dashboard_element_id:1,row:0,column:0,width:8,height:4,deleted:false},{id:2,dashboard_layout_id:1,dashboard_element_id:2,row:0,column:8,width:8,height:4,deleted:false}]}],elements:{1:{title:"Total Orders",title_hidden:false,vis_config:{type:"single_value",font_size:"medium",title:"Total Orders"}},2:{title:"Average Order Profit",title_hidden:false,vis_config:{type:"single_value",title:"Average Order Profit"}}}}}

dashboard:download

This event is created when a PDF of a dashboard has started downloading.

type:"dashboard:download",dashboard:{id:23,title:"My Dashboard",canEdit:true,url:"/embed/dashboards/...",absoluteUrl:"https://instance_name.looker.com/embed/dashboards/...",dashboard_filters:{"Date":"Last 28 days","Total Orders":"Greater than 100"}}fileFormat:"pdf"

dashboard:edit:start

Added 22.20 This event is created when a dashboard isswitched into edit mode.

type:"dashboard:edit:start",dashboard:{id:23,title:"My Dashboard",canEdit:true,url:"/embed/dashboards/...",absoluteUrl:"https://instance_name.looker.com/embed/dashboards/...",dashboard_filters:{"Date":"Last 28 days","Total Orders":"Greater than 100"}}

dashboard:edit:cancel

Added 22.20 This event is created when a dashboard that is inedit mode is exited from edit mode without saving.

type:"dashboard:edit:cancel",dashboard:{id:23,title:"My Dashboard",canEdit:true,url:"/embed/dashboards/...",absoluteUrl:"https://instance_name.looker.com/embed/dashboards/...",dashboard_filters:{"Date":"Last 28 days","Total Orders":"Greater than 100"}}

dashboard:save:complete

This event is created when a dashboard isedited and then saved.

type:"dashboard:save:complete",dashboard:{id:23,title:"My Dashboard",canEdit:true,dashboard_filters:{"Date":"Last 28 days","Total Orders":"Greater than 100"}absoluteUrl:"https://instance_name.looker.com/embed/dashboards/...",url:"/embed/dashboards/...",options:{layouts:[{id:1,dashboard_id:1,type:"newspaper",active:true,column_width:null,width:null,deleted:false,dashboard_layout_components:[{id:1,dashboard_layout_id:1,dashboard_element_id:1,row:0,column:0,width:8,height:4,deleted:false},{id:2,dashboard_layout_id:1,dashboard_element_id:2,row:0,column:8,width:8,height:4,deleted:false}]}],elements:{1:{title:"Total Orders",title_hidden:false,vis_config:{type:"single_value",font_size:"medium",title:"Total Orders"}},2:{title:"Average Order Profit",title_hidden:false,vis_config:{type:"single_value",title:"Average Order Profit"}}}}}

dashboard:delete:complete

This event is created when adashboard is deleted.

type:"dashboard:delete:complete",dashboard:{id:23,title:"My Dashboard",canEdit:true,dashboard_filters:{"Date":"Last 28 days","Total Orders":"Greater than 100"}absoluteUrl:"https://instance_name.looker.com/embed/dashboards/...",url:"/embed/dashboards/...",options:{layouts:[{id:1,dashboard_id:1,type:"newspaper",active:true,column_width:null,width:null,deleted:false,dashboard_layout_components:[{id:1,dashboard_layout_id:1,dashboard_element_id:1,row:0,column:0,width:8,height:4,deleted:false},{id:2,dashboard_layout_id:1,dashboard_element_id:2,row:0,column:8,width:8,height:4,deleted:false}]}],elements:{1:{title:"Total Orders",title_hidden:false,vis_config:{type:"single_value",font_size:"medium",title:"Total Orders"}},2:{title:"Average Order Profit",title_hidden:false,vis_config:{type:"single_value",title:"Average Order Profit"}}}}}

dashboard:tile:start

This event is created when a tile starts loading or querying for data.

type:"dashboard:tile:start",dashboard:{id:23,title:"My Dashboard",canEdit:true,url:"/embed/dashboards/...",absoluteUrl:"https://instance_name.looker.com/embed/dashboards/...",dashboard_filters:{"Date":"Last 28 days","Total Orders":"Greater than 100"}}tile:{id:123,title:"Quarterly Sales",listen:{"Date":"order.date","Total Orders":"order.count"}}

dashboard:tile:complete

This event is created when a tile has finished running the query.

type:"dashboard:tile:complete",dashboard:{id:23,title:"My Dashboard",canEdit:true,url:"/embed/dashboards/...",absoluteUrl:"https://instance_name.looker.com/embed/dashboards/...",dashboard_filters:{"Date":"Last 28 days","Total Orders":"Greater than 100"}}status:"complete",truncated:false,tile:{id:123,title:"Quarterly Sales",listen:{"Date":"order.date","Total Orders":"order.count"}}

dashboard:tile:download

This event is created when a tile's data has started downloading.

type:"dashboard:tile:download",dashboard:{id:23,title:"My Dashboard",canEdit:true,url:"/embed/dashboards/...",absoluteUrl:"https://instance_name.looker.com/embed/dashboards/...",dashboard_filters:{"Date":"Last 28 days","Total Orders":"Greater than 100"}}tile:{id:123,title:"Quarterly Sales"listen:{"Date":"order.date","Total Orders":"order.count"}}fileFormat:"pdf"

dashboard:tile:explore

This event is created when a user clicks theExplore From Here option in a dashboard tile.

This event is cancellable, meaning that the embedding application can return{cancel: true} and Looker won't proceed with the triggering event.

type:"dashboard:tile:explore",label:'Explore From Here',url:'/embed/explore/model/view...',dashboard:{id:23,title:"My Dashboard",canEdit:true,url:"/embed/dashboards/...",absoluteUrl:"https://instance_name.looker.com/embed/dashboards/...",dashboard_filters:{"Date":"Last 28 days","Total Orders":"Greater than 100"}}tile:{id:123,title:"Quarterly Sales",listen:{"Date":"order.date","Total Orders":"order.count"}}

dashboard:tile:view

This event is created when a user clicks theView Original Look option in a dashboard tile.

This event is cancellable, meaning that the embedding application can return{cancel: true} and Looker won't proceed with the triggering event.

type:"dashboard:tile:view",label:'View Original Look',url:'/embed/look/...',dashboard:{id:23,title:"My Dashboard",canEdit:true,url:"/embed/dashboards/...",absoluteUrl:"https://instance_name.looker.com/embed/dashboards/...",dashboard_filters:{"Date":"Last 28 days","Total Orders":"Greater than 100"}}tile:{id:123,title:"Quarterly Sales",listen:{"Date":"order.date","Total Orders":"order.count"}}

dashboard:tile:merge

Added 25.14 This event is generated when the user clicks theEdit Merged Query button or theEdit Merged Query menu item. The default behavior for this button is to open a new top-level window that allows the merge query to be edited.

This event is cancellable, meaning that the embedding application can return{cancel: true} and Looker won't proceed with the triggering event. This event allows the embedding application to open the merge query edit in an iframe rather than a top-level window. The embedding application shouldn't attempt to load the URL in the iframe that triggered the event. Instead, a new iframe should be created.

dashboard:filters:changed

This event is created when a dashboard's filters have been applied or changed.

type:"dashboard:filters:changed",dashboard:{id:23,title:"My Dashboard",canEdit:true,url:"/embed/dashboards/...",absoluteUrl:"https://instance_name.looker.com/embed/dashboards/...",dashboard_filters:{"Date":"Last 28 days","Total Orders":"Greater than 100"}options:{layouts:[{id:1,dashboard_id:1,type:"newspaper",active:true,column_width:null,width:null,deleted:false,dashboard_layout_components:[{id:1,dashboard_layout_id:1,dashboard_element_id:1,row:0,column:0,width:8,height:4,deleted:false},{id:2,dashboard_layout_id:1,dashboard_element_id:2,row:0,column:8,width:8,height:4,deleted:false}]}],elements:{1:{title:"Total Orders",title_hidden:false,vis_config:{type:"single_value",font_size:"medium",title:"Total Orders"}},2:{title:"Average Order Profit",title_hidden:false,vis_config:{type:"single_value",title:"Average Order Profit"}}}}}

look:ready

This event is created when a Look begins to load query data, whether the query runs or not.

type:"look:ready",look:{url:"/embed/looks/...",absoluteUrl:"https://instance_name.looker.com/embed/looks/...",}

look:run:start

This event is created when a Look begins to load query data and the query begins to run.

type:"look:run:start",look:{url:"/embed/looks/...",absoluteUrl:"https://instance_name.looker.com/embed/looks/...",}

look:run:complete

This event is created when a Look has finished running the query.

type:look:run:completelook:{url:"/embed/looks/...",absoluteUrl:"https://instance_name.looker.com/embed/looks/...",}

look:edit:start

Added 25.10 This event is fired when a Look is switched into edit mode.

type:"look:edit:start",look:{id:46,title:"My Look",url:"/embed/looks/46",absoluteUrl:"https://instance_name.looker.com/embed/looks/46",}

look:edit:cancel

Added 25.10 This event is fired when a Look that is in edit mode is exited from edit mode without saving.

type:"look:edit:cancel",look:{id:46,title:"My Look",url:"/embed/looks/46",absoluteUrl:"https://instance_name.looker.com/embed/looks/46",}

look:save:complete

This event is created when a Look is edited and saved. This event is created when a user performs one of the following tasks:

• Clicks theEdit button to edit the Look and then clicksSave
• Saves a Look with theSave >Save As… menu option
• Moves a Look from one folder to another

This event is not created if the Look is saved with theSave >To existing dashboard orEdit Settings menu option.

type:look:save:completelook:{url:"/embed/looks/...",absoluteUrl:"https://instance_name.looker.com/embed/looks/...",folderid:123}

look:delete:complete

This event is created when a Look ismoved to theTrash folder.

type:look:delete:completelook:{url:"/embed/looks/...",absoluteUrl:"https://instance_name.looker.com/embed/looks/...",}

drillmenu:click

This event is created when a user clicks on a drill menu in a dashboard created with thelink LookML parameter. For example, the following LookML creates a drill menu where a user can view data filtered by thestate dimension:

dimension:state{type:stringsql:${TABLE}.state;;link:{label:"Filter by {{ state | encode_uri }}"url:"filter::q={{ state | encode_uri }}"icon_url:"https://google.com/favicon.ico"}}

When thestate filter is set toIllinois, thedrillmenu:click event returns the following to the host of the iframe:

type:"drillmenu:click",label:"Filter by Illinois",link_type:"url",modal:false,target:'_self',url:"#filter::state=Illinois"context:' '

This event is cancellable, meaning that the embedding application can return{cancel: true} and Looker won't proceed with the triggering event.

Sandboxing the iframe will prevent drill menu clicks from opening in a new window. Use these sandboxing values inside the iframe tag:

sandbox="allow-same-origin allow-scripts"

drillmodal:download

This event is created when a user opens a drill dialog from a dashboard tile and clicks theDownload option.

{type:"drillmodal:download",dashboard:{id:23,title:"My Dashboard",url:"/embed/dashboards/…",absoluteUrl:"https://instance_name.looker.com/embed/dashboards/…",dashboard_filters:{"Date":"Last 28 days","Total Orders":"Greater than 100"}}drillExploreUrl:"/embed...",fileFormat:"pdf"}

drillmodal:explore

This event is created when a user clicks theExplore From Here option in a drill dialog.

This event is cancellable, meaning that the embedding application can return{cancel: true} and Looker won't proceed with the triggering event.

type:"drillmodal:explore",label:"Explore From Here",url:"/embed/explore/model/view..."

explore:ready

This event is created when an Explore begins to load query data, whether the query runs or not.

type:"explore:ready",explore:{url:"/embed/explore/...",absoluteUrl:"https://instance_name.looker.com/embed/explore/...",}

explore:run:start

This event is created when an Explore begins to load query data and the query begins to run.

type:"explore:run:start",explore:{url:"/embed/explore/...",absoluteUrl:"https://instance_name.looker.com/embed/explore/...",}

explore:run:complete

This event is created when an Explore has finished running the query.

type:"explore:run:complete",explore:{url:"/embed/explore/...",absoluteUrl:"https://instance_name.looker.com/embed/explore/...",}}

explore:state:changed

This event is created when an Explore page URL changes as a result of the user's actions.

type:"explore:state:changed",explore:{url:"/embed/explore/...",absoluteUrl:"https://instance_name.looker.com/embed/explore/..."}

page:changed

This event is created when a user navigates to a new page within the iframe.

type:"page:changed",page:{type:"dashboard",url:"/embed/dashboards/...",absoluteUrl:"https://instance_name.looker.com/embed/dashboards/..."}

page:properties:changed

This event is created when the height of a dashboard iframe changes. It is not available for Looks or Explores because those items automatically adjust their height to the size of the iframe.

type:"page:properties:changed",height:1000

session:tokens

This event indicates that the Looker client requires tokens to continue. This event is created immediately on creation of the iframe and periodically afterwards for the duration of the session.

{"type":"session:tokens","api_token":"eyJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJodHRwczovL3NlbGYtc2lnbmVkLmxvb2tlci5jb206OTk5OSIsImV4cCI6MTY3MDYyNjMzMCwic3ViIjoiYVdrNWFGUzM4RnRwNzFFWXhuS3ZaMXdKRmV3ZjB2VzYtTV9zLWtCcHE1dXIiLCJ0b2tlbl90eXBlIjoiYXBpX3Rva2VuIiwicmFuZG9taXplciI6IkxjYnpOeDNTVjNOb3o3UVlqTVJjNmhlMkdodjh1a2UwWUhiZWNRMHVCYm1KIn0.CBv1__QGc_H7bKNe31SHMMQCsc5ya1xOiEv1UDWAyxM","api_token_ttl":463,"navigation_token":"eyJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJodHRwczovL3NlbGYtc2lnbmVkLmxvb2tlci5jb206OTk5OSIsImV4cCI6MTY3MDYyNjMzMCwic3ViIjoiYVdrNWFGUzM4RnRwNzFFWXhuS3ZaMXdKRmV3ZjB2VzYtTV9zLWtCcHE1dXIiLCJ0b2tlbl90eXBlIjoibmF2aWdhdGlvbl90b2tlbiIsInJhbmRvbWl6ZXIiOiJHVVNlc00tdTRPRDlNdktodFJDU2pEcVFhUkJNeTh5dm42Q1FDUXhuLTNxMiJ9.sWo7LUEI5LeragVmeDamUR7u2myXpFJ0aqK_IIALUqI","navigation_token_ttl":463,"session_reference_token_ttl":2924}

session:expired

Added 25.10 This event is fired when the embed user's session expires.

type:"session:expired",

This event does not have a payload.

session:status

The event is generated when the embedded Looker application handles requests for session tokens.

{"type":"session:status","session_ttl":0,"expired":true,"interrupted":false}

env:client:dialog

The event is generated when a dialog has been opened that may partially be out of view, such as a drill dialog. This event enables the hosting application to scroll the dialog into view with theenv:host:scroll action.

{type:"env:client:dialog",dialogType:'drilling',placement:'cover',open:true}

Making changes to the iframe

After you'veprepped your iframe for data retrieval, you can make changes to the iframe with the following steps:

1. Write your request in JSON.
2. Post the request to the iframe'scontentWindow.

Writing your request in JSON

You can make several changes to the iframe, which you'll submit in JSON form. The available options are described in theAction reference section on this page. Don't forget to useJSON.stringify to turn your action into JSON, like this:

varmy_request=JSON.stringify({type:"dashboard:run"});

Posting the request to the iframe'scontentWindow property

Finally, post your message to the iframe'scontentWindow, like this:

varmy_iframe=document.getElementById("my_iframe_id");my_iframe.contentWindow.postMessage(my_request,'https://instance_name.looker.com');

Action summary table

The following table summarizes actions. Select an action to see the details about that action.

Action reference

These are the available actions you can post to the embedded iframe:

page:load

Use this action to navigate to new content within the iframe, replacing the existing content. This action is similar to thedashboard:load action but is more flexible, as additional parameters can be specified in the URL.

There are differences in behavior that should be considered before usingpage:load.dashboard:load will prevent the navigation from happening if the current dashboard is being edited.page:load doesn't prevent the navigation from happening. The host application may determine if a dashboard or Look is being edited by trackingdashboard:edit:start,look:edit:start, and their corresponding edit end events. For this reason, we recommend using the embed SDK. The embed SDK tracks whether a dashboard or Look is being edited, and so the connection can be queried to see if content is being edited prior to navigation.

{type:'page:load',url:'/embed/dashboard/32?state=california,pushHistory:false}

dashboard:load

Use this action to load a new dashboard in the iframe, replacing an existing dashboard. The new dashboard will begin executing queries as if a new dashboard page had been opened.

{type:"dashboard:load",id:"101",pushHistory:false}

dashboard:run

Use this action to run the dashboard in the iframe. This is the same action as hitting theRun orReload Data button on the dashboard.

{type:"dashboard:run"}

dashboard:edit

Added 22.20 Use this action to switch an existing dashboard in the iframe toedit mode. This is the same action as selectingEdit dashboard from the dashboard menu.

{type:"dashboard:edit"}

dashboard:filters:update

Use this action to update an existing dashboard filter in the iframe. You can't add a new filter to the dashboard by using this method.

{type:"dashboard:filters:update",filters:{"Sale date":"Last 28 days","Sale amount":"Greater than 100"}}

dashboard:options:set

This action is available after thedashboard:run:complete event occurs.

The embedder creates the message and sends it to the iframe, but the dashboard does not respond until afterdashboard:run:complete occurs. Thedashboard:options:set action writes new values to dashboard layout and dashboard element properties. Only properties that have been returned in theoptions attribute of thedashboard:run:complete event can be updated usingdashboard:options:set. Any properties set that were not previously returned by theoptions attribute of thedashboard:run:complete event are ignored.

{type:"dashboard:options:set",layouts:[{id:1,dashboard_id:1,type:"newspaper",active:true,column_width:null,width:null,deleted:false,dashboard_layout_components:[{id:1,dashboard_layout_id:1,dashboard_element_id:1,row:0,column:0,width:8,height:4,deleted:false},{id:2,dashboard_layout_id:1,dashboard_element_id:2,row:0,column:8,width:8,height:4,deleted:false}]}],elements:{1:{title:"Total Orders",title_hidden:false,vis_config:{type:"single_value",font_size:"medium",title:"Total Orders"}},2:{title:"Average Order Profit",title_hidden:false,vis_config:{type:"single_value",title:"Average Order Profit"}}}}

dashboard:schedule_modal:open

Use this action to open the Scheduler, which lets usersdeliver Looker content to various destinations.

{type:"dashboard:schedule_modal:open"}

dashboard:stop

Use this action to stop a dashboard that is running or reloading data. This is the same action as clicking theCancel button on the dashboard. A dashboard that is stopped usingdashboard:stop sends adashboard:run:complete event withstatus: set to"stopped".

{type:"dashboard:stop"}

look:run

Use this action to run the query on which the Look is based in the iframe. This action is similar to hitting theRun button on the Look, with the exception thatlook:run always queries the database directly and does not retrieve data from theLooker cache.

{type:"look:run"}

look:filters:update

Use this action to update an existing Look filter in the iframe. You can't add a new filter to the Look by using this method.

{type:"look:filters:update",filters:{"orders.created_at":"90 days","products.department":"sweaters"}}

explore:run

Use this action to run the Explore in the iframe. This action is similar to hitting theRun button on the Explore, with the exception thatexplore:run always queries the database directly and does not retrieve data from theLooker cache.

{type:"explore:run"}

explore:filters:update

Use this action to update or remove an existing Explore filter in the iframe. Including a new filter that references a valid field will add the new filter to the Explore.

{type:"explore:filters:update",filters:{"orders.created_at":"90 days","orders.status":"complete"}deleteFilters:["products.department"]}

session:tokens:request

Use this action to send tokens in response to asession:tokens:request request.

{type:"session:tokens:request",}

env:host:scroll

Use this action to send information about the current scroll position of the host iframe to the embedded Looker application.

{type:"env:host:scroll",offsetTop:10,offsetLeft:10,scrollX:5,scrollY:5}