Looker Data Apps enters preview with reporting limits to check

What changed

A new interface on governed data

Google Cloud announced Looker Data Apps on 13 October. Applications use the existing LookML layer and viewer permissions. AI assists authoring; published interactions do not call an AI model. This concerns Looker, not a general release for Looker Studio.

Read the preview limits before planning a client rollout

The setup documentation requires a Looker-hosted instance on version 26.18 or later, an administrator-enabled preview and the relevant folder and model permissions. It currently lists embedding, printing, PDF export and scheduled PDF delivery as unsupported.

That embedding restriction differs from the announcement's broader description of embedded use. Treat the current setup limits as the planning constraint and confirm support with the product owner before promising a client portal. Documentation review does not establish that the feature is enabled in your instance.

For a paid media reporting team, PMC suggests prototyping one internal decision view first. Write down the question, metric definition and permitted audience. Compare the displayed result against an existing trusted report using the same dates, currency, filters and conversion window. A polished interface cannot repair a poorly defined return metric or an incomplete data model.

Why it matters for advertisers

An interactive decision tool and a scheduled client report have different requirements. Keep an established delivery workflow while assessing the preview. Test with a restricted viewer as well as an administrator, and ask who will maintain the model and application when campaign definitions change. The absence of runtime model calls is not a claim that Looker hosting, queries or authoring are free.