Use FXMacroData in Looker Studio
Build native charts, tables and scorecards from official macroeconomic releases, calendars and market datasets. Google also calls Looker Studio Data Studio; the same Community Connector works with your reports.
Access and permissions
Public USD indicator history covers the last 90 days with a 15-minute release delay and needs no FXMacroData account or API key. Public catalogue and USD calendar data are also available. Full history, non-USD data and protected market datasets require an appropriate FXMacroData subscription.
Authorize the connector with Google. If a key prompt appears for public data, enter public. For protected data, use Looker Studio's key authorization and your own FXMacroData API key. The connector requests permission to make external requests; it does not request access to your Gmail, contacts or spreadsheet contents.
Connect your first data source
- Open the connector and complete Google's authorization flow.
- Choose All API datasets, then select the announcement history dataset:
GET /v1/announcements/{currency}/{indicator}. - Choose
USDandinflation. Set a populated date window within your available history. Optional filters keep their API names. - Leave Nested table blank for the primary table. Click Connect, then Create Report.
- Add a time-series chart with
dateas its dimension andvalas its metric. Choose an aggregation appropriate to the indicator and its unit. - Match the chart's date filter to your intended window. For monthly or quarterly data, set Missing data to Line Breaks and enable Show points so missing dates do not appear as zero.
Use a populated window when discovering fields. An empty window after connecting returns no rows. Refresh the data-source fields after changing the dataset, nested table or a column's type.
Choose a dataset
The dataset selector provides native date, number, boolean and text fields. Availability depends on the selected dataset, history window and your access.
| Dataset family | Report workflow |
|---|---|
| Catalogue and coverage | Find available series, sources and coverage. |
| Macro history and latest values | Chart indicators with their periods, units and publication evidence. |
| Release calendars and archives | Build release tables and inspect calendars as known at an earlier time. |
| Predictions and official forecasts | Keep target periods and publication vintages alongside forecast values. |
| Central-bank news | Display official headlines, publishers and original links. |
| FX and market sessions | Chart rates, reference fixings, session rates and returned technical fields. |
| Positioning and COT | Compare positioning by instrument, report and date. |
| Commodities and seasonality | Chart commodity histories and monthly return statistics. |
| Rates and research tables | Work with curves, rate differentials, financial prices, factors, risk sentiment and research panels. |
To select another repeated group, enter its response path in Nested table, such as official_forecasts, overlaps or data.components. Object fields retain their names; parent.* identifies the enclosing record and metadata.* retains response metadata. Do not sum metadata repeated on every row.
The existing Announcements, Forex and Commodities modes remain available. Their field IDs are preserved. The all-announcements mode is a latest-100-per-series view; select a single history dataset for complete paginated history within your access.
Refresh and troubleshooting
- Explicit API date filters take precedence over report dates. Report dates are sent only to datasets that support those parameters.
- Results follow the API's returned pages. A result above the configured maximum of 5,000 rows stops with an explanation; narrow the window or filters.
- Authentication errors require reauthorization. Entitlement errors require an allowed dataset or history window. Request limits or Google Apps Script quotas can require waiting before another refresh.
- Unknown publication times remain empty. An observation date does not establish when its publisher released it.
Privacy and support
A supplied API key is saved in Google Apps Script properties for your Google user and sent to FXMacroData in the X-API-Key header, never in a URL. Do not put keys in dataset paths, filters, screenshots or report text. Reauthorize the connector to change credentials.
Google handles your report and data-source settings. Review the data-source credential and sharing settings before sharing or embedding a report. Your FXMacroData licence and each dataset's publisher conditions govern redistribution.
Read the Privacy Policy and Terms of Service. For help, use the support page or email info@fxmacrodata.com.