Embedding a Linking API Purpose

Looker Q&A Looker Studio
, ,
1

I’m looking to use the linking api to embed a template report with Google Analytics. I needed to have a specific Google Analytics accountId and propertyId (The normal embed doesn’t allow for this hence I’m using Linking API). I was able to successfully use the Linking API to embed a report with a specific Google Analytics accountId and propertyId with the following path:

/embed/reporting/create?c.reportId=xxxxxxxxc&ds.ds0.connector=googleAnalytics&ds.ds0.accountId=xxxxxxx&ds.ds0.propertyId=xxxxxxx

However, when embedding it into my website, the user has to sign into the iframe that is used. This will not be feasible since we are using this in our platform where a user is created dynamically and only has a specific Google Analytics accountId and propertyId.

Since embedding is a standard feature in the Linking API:

image

how would I be able to include this in an iframe without having the user sign in? This doesn’t make since for the user to have to sign into an iframe to see this data. Would I be able to use OAuth sign in to provide an auth key for this? How would I go about doing this?

Thanks!

2

Thanks for the detailed explanation — this is a common point of confusion with the Linking API and embedding.

In Looker Studio, the Linking API does allow you to create or parameterize reports programmatically, but it does NOT bypass authentication. Any embedded report still requires the viewer to be authenticated and have access to the underlying data source (in this case, the Google Analytics account and property).

At the moment:

  • OAuth tokens or API keys cannot be used to authenticate iframe viewers.
  • The Linking API is not designed for fully anonymous or headless access.
  • The iframe sign-in prompt is expected behavior when the user is not already authenticated with a Google account that has permission.

Typical alternatives are:

  • Using standard embedding with users signed in to Google accounts that have GA access.
  • Sharing reports publicly (if data sensitivity allows).
  • Using a service account + BigQuery export from GA, then embedding Looker Studio reports backed by BigQuery where access control is managed differently.

So unfortunately, for GA-connected reports, there isn’t a supported way today to embed via iframe without requiring a Google sign-in.

Hope this helps clarify the limitation.