Use Lumina in Looker Studio

The Lumina connector for Looker Studio reads your clients' synced numbers, so you can build dashboards in Looker Studio next to your other data. Owners and admins set it up.

Who it is for

Agencies that already build client dashboards in Looker Studio, or that want to mix Lumina numbers with other data there. Lumina pulls the numbers from each ad platform, and Looker Studio reads them from Lumina with one API key. API keys and the connector come with the Scale package, or with the API and Looker Studio add-on on Growth and Agency.

How to set it up

1. 1In Lumina, go to Settings, API keys.
2. 2Under Create an API key, give the key a name (like Looker Studio), choose every client or only some, and click Create API key.
3. 3Copy the key. It is shown only once; Lumina keeps only a fingerprint of it.
4. 4On the same page, click Open the Lumina connector. Looker Studio opens. Click Authorize and allow access with your Google account.
5. 5Paste your Lumina API key and click Submit.
6. 6Pick a client and a level (ad account, campaign, ad set or ad), then click Connect.
7. 7Click Create report. Add charts with the Lumina fields and use the date range control to pick dates.

Fields you can use

Fields: date, platform, ad account, currency, campaign, objective, ad set and ad (by level), and the numbers Lumina syncs: spend, impressions, clicks, link clicks, reach, conversions, conversion value, leads, app installs, engagements and video views. CTR, CPC, CPM, CPA, CPL, CPI, CPE, CPV and ROAS are worked out by Looker Studio from those totals.

Because rates and costs are worked out from the totals, they stay right when you group by week, platform or campaign. A number that no row reports shows as empty, not as zero.

A typical example

An agency wants one Looker Studio dashboard for a client that runs Meta and Google Ads, with a weekly spend chart and a campaign table.

1. 1An admin creates a key named Looker Studio, picks Only some clients and ticks this client.
2. 2In Looker Studio, the admin adds the Lumina connector, pastes the key, picks the client and the Campaign level, and clicks Connect.
3. 3The admin adds a time series of Spend by Date, and a table with Platform, Campaign, Spend, Clicks and CPC.
4. 4A date range control sets the dates the charts show.

Settings and limits

• Spend: by default it includes each client's markup, the same as the client sees in Lumina. Tick Show real spend when you create a key for your team's own dashboards.
• Currencies: money comes in the currency the client's reports use. When a client's ad accounts mix currencies that Lumina cannot convert, add the Currency field to charts with money.
• Limits: each key can make 120 requests a minute, and one request reads at most 50,000 daily rows. For long ranges at ad level, pick a shorter range or a higher level.
• Revoke a key in Settings, API keys. Dashboards using it stop updating right away. Creating and revoking keys shows in the activity log.
• A workspace can have up to 20 active keys. The list shows each key's clients, whether it shows real spend, and when it was last used.
• One data source in Looker Studio reads one client. Add a data source for each client you want in the dashboard.
• Lumina keeps 90 days of history, so dates before that show no data.
• Reach is daily reach added up, so people reached on more than one day count more than once.
• Looker Studio has no currency type for some currencies, such as KWD, QAR, BHD, OMR and JOD. For these, money shows as a plain number with the currency code in the field name.