Looker Studio Connector

This is the installation and configuration guide for Looker Studio Connector, the module you downloaded from your ECOSIRE dashboard or the Odoo Apps Store. Everything on this page describes the ecosire_looker_studio_connector module exactly as it ships today.


Technical name	`ecosire_looker_studio_connector`
Odoo versions	17.0, 18.0, 19.0 (Community or Enterprise)
Current shipped version	17.0 → `17.0.1.0.1`, 18.0 → `18.0.1.0.1`, 19.0 → `19.0.1.0.2`
Price	$499 USD, one-time, per Odoo version
Odoo module licence	`OPL-1`
Category	Productivity / Reporting

What changed in 19.0.1.0.2

No licence activation. The module no longer depends on a separate ECOSIRE licence module, and nothing has to be activated: Auto-map Fields and Generate / Regenerate Token work as soon as the module is installed. Licensing is contractual under OPL-1. The 17.0.1.0.1 and 18.0.1.0.1 builds ship the same way.

What it does

The module is the Odoo side of a Google Looker Studio data source. It lets you decide exactly which Odoo data may be reported on, and exposes that data, read-only, to a Looker Studio Community Connector.

Datasets. A dataset is one Odoo model (for example Sales Orders, Invoices, CRM leads, POS orders, stock moves or purchase orders), the fields you choose to expose, and an optional base filter that is always applied.
Reporting tokens. Each token runs as one Odoo user. Every read is performed as that user, so the user's access rights, record rules and company restrictions apply to every row Looker Studio receives.
Read-only bridge. Four HTTPS endpoints under /looker_studio/ answer the connector. They only ever search and read; they never create, change or delete Odoo records. Data flows from Odoo to Looker Studio only.

The Looker Studio side

Looker Studio reads this data through a Community Connector, a Google Apps Script project. The connector script is not part of the Odoo download. It calls the four endpoints described under Connector reference. For help connecting a Looker Studio report, email info@ecosire.com.

Requirements

Odoo 17.0, 18.0 or 19.0, Community or Enterprise.
The module depends only on base and web. The models you expose (sales, invoicing, CRM, POS, inventory, purchase) must of course be installed for their datasets to have data.
Your Odoo must be reachable over HTTPS from Google's servers, because the connector fetches the data from your Odoo URL.

Installation

Install ECOSIRE Looker Studio Connector from Apps in your Odoo database.
Give the right people access (next section). The Looker Studio app appears in the main menu for users in one of its groups.

Access levels

Two groups ship with the module, under Settings → Users & Companies → Users:

Group	Can do
Looker Studio / User	See the datasets, and create, regenerate and revoke their own reporting tokens.
Looker Studio / Manager	Everything a user can do, plus create and edit datasets and manage every user's tokens.

All three records (datasets, dataset fields, tokens) carry a company and are isolated per company in a multi-company database.

Configure a dataset

Go to Looker Studio → Datasets and create a dataset (Manager):

Field	Meaning
Dataset Name	The label shown in the Looker Studio connector's dataset list, e.g. Sales Orders.
Dataset Key	The stable identifier the connector sends, lowercase with no spaces, e.g. `sales_orders`. Unique per company.
Odoo Model	The model to expose, e.g. `sale.order`.
Base Domain	An Odoo domain always applied to every read, e.g. `[('state', '=', 'sale')]`. It must be a valid list, or the dataset cannot be saved.
Max Rows Per Call	Rows returned per request (default 10,000; never more than 50,000). The connector pages through larger results.
Active	Inactive datasets are not offered to Looker Studio.

Then fill the Exposed Fields tab. Click Auto-map Fields to add every stored field of the model (binary, one-to-many and many-to-many fields are skipped), then delete the rows you do not want to share and reorder the rest. Only the fields listed here can ever be returned; a dataset with no exposed fields returns nothing.

Each row maps one Odoo field to a Looker Studio field:

Column	Meaning
Odoo Field	The technical field name on the model.
Looker Field Name	The name Looker Studio uses. Unique within the dataset.
Label	The display name in Looker Studio.
Data Type / Concept	`STRING`, `NUMBER` or `BOOLEAN`; `DIMENSION` or `METRIC`.
Semantic Type	Optional; set automatically for dates.

Auto-map applies these types:

Odoo field type	Looker Studio type	Value sent
Integer, Float, Monetary	`NUMBER` metric	The number
Char, Text, HTML, Selection, Reference	`STRING` dimension	The text (selection fields send the stored key)
Many2one	`STRING` dimension	The linked record's display name
Boolean	`BOOLEAN` dimension	`true`; a false value arrives empty
Date	`STRING` dimension, `YEAR_MONTH_DAY`	`YYYYMMDD`
Datetime	`STRING` dimension, `YEAR_MONTH_DAY_SECOND`	`YYYYMMDDHHMMSS`

Issue a reporting token

Go to Looker Studio → Reporting Tokens and create a token:

Enter a Token Label (e.g. Finance Dashboard) and choose the Run As User. The token sees exactly what that user sees in Odoo, so pick a user with the access the report needs and no more.
Optionally set an Expiration Date; after it the token stops working.
Optionally list Allowed Datasets. Leave it empty to allow every dataset the run-as user can see.
Click Generate / Regenerate Token. The token (it starts with lkr_) is shown once in a notification. Copy it now: Odoo stores only a hash of it and cannot show it again. The form keeps the first characters as Token Hint so you can recognise it.

Regenerating replaces the token, so any report using the old one stops refreshing until you paste the new one. Revoke deactivates the token. Last Used shows when it last called Odoo.

Connector reference

The connector authenticates every request with the reporting token in either header:

Authorization: Bearer lkr_xxxxxxxxxxxxxxxx
X-Api-Key: lkr_xxxxxxxxxxxxxxxx

Endpoint	Connector function	Returns
`GET /looker_studio/ping`	`isAuthValid`	`ok`, the run-as user's login, the company and the bridge version
`GET /looker_studio/datasets`	`getConfig`	The datasets the token may use: key, name, model, description
`GET /looker_studio/schema?dataset=<key>`	`getSchema`	The dataset's exposed fields with name, label, data type, concept and semantic type
`POST /looker_studio/data`	`getData`	Rows for the requested fields, with paging

Body of POST /looker_studio/data:

{
  "dataset": "sales_orders",
  "fields": ["name", "amount_total", "date_order"],
  "date_field": "date_order",
  "date_range": { "start": "2026-01-01", "end": "2026-12-31" },
  "filters": [ { "field": "state", "op": "=", "value": "sale" } ],
  "offset": 0,
  "limit": 10000
}

fields may name only exposed fields; others are ignored. Omit it to get every exposed field.
date_field and every filter field must also be exposed fields. Filter operators allowed: =, !=, >, >=, <, <=, in, not in, like, ilike, =like, =ilike.
The response is { "schema": [...], "rows": [{ "values": [...] }], "total": N, "offset": N, "limit": N }. Keep requesting with a higher offset until offset + limit reaches total.

Responses:

Status	Meaning
`200`	Success
`400`	The body is not a JSON object, or none of the requested fields is exposed
`401`	Missing, unknown, revoked or expired token, or the run-as user is archived
`403`	The dataset does not exist, is inactive, is not visible to the run-as user, or is not in the token's Allowed Datasets
`429`	More than 60 requests per minute on this token

Security model

Tokens are stored only as a SHA-256 hash and are never written to the Odoo log.
Every read runs as the token's user, so access rights, record rules and multi-company isolation apply.
Only exposed fields can be read, filtered or returned; caller filters are checked against a fixed operator list and never evaluated as raw code.
The dataset's Base Domain is always applied on top of any caller filter.
No endpoint can create, modify or delete Odoo data.

Troubleshooting

Symptom	Fix
Connector says the credentials are invalid	Check the token was copied completely, is active and has not expired, and that the run-as user is not archived. Regenerate it if in doubt.
A dataset is missing from the list	Make sure it is Active, belongs to the run-as user's company, and is in the token's Allowed Datasets (or that list is empty).
Fewer rows than expected	The Base Domain, the run-as user's record rules and company access all restrict rows. Check them in Odoo as that user.
A column is missing	Add the field to the dataset's Exposed Fields and refresh the data source fields in Looker Studio.
Errors with status 429	The report sends more than 60 requests per minute on one token. Raise Max Rows Per Call so fewer pages are needed, or use separate tokens per report.

Support

Email info@ecosire.com with your Odoo version, the module version shown in Apps, and what you see.

What it does​

Requirements​

Installation​

Access levels​

Configure a dataset​

Issue a reporting token​

Connector reference​

Security model​

Troubleshooting​

Support​