Gravity Forms
+ Looker Studio Connector

Looker Studio is a great place to turn form entries into dashboards: trends over time, breakdowns by service or campaign, date range controls and reports you can share with people who have no WordPress login. Getting Gravity Forms entries there usually means copying every entry into a spreadsheet, or setting up a data warehouse. The Gravity Forms Looker Studio Connector add-on lets Looker Studio read your entries live from your own site instead, so the report always matches WordPress and there is no second copy to keep in sync.

You create a data source for a form and tick the fields to share. That list is an allowlist: nothing else can ever be read, and personal fields such as names, e-mail addresses and phone numbers are off by default. Give the fields friendly names, choose the entry statuses (spam and trash are off by default) and an optional date window. Number, price and total fields become metrics, date fields become date dimensions and choices become text dimensions, so your charts work straight away.

Looker Studio connects through a community connector that you deploy once in your own Google account, with a step-by-step guide and copy-ready files. It reads a read-only endpoint protected by a secret key per data source. Keys are shown once and stored only as a salted hash, and can be rotated or revoked in one click. A rate limit, a wrong-key lockout, an optional IP allowlist and HTTPS only by default protect the endpoint, and a Test connection check runs on your own server. For Gravity Forms 2.9 and newer.

Each data source stores the form, the allowlisted fields with their friendly names, the entry statuses, the date window, the rate limit, an optional IP allowlist and a hash of its key. The add-on registers two read-only REST routes: one returns the Looker Studio field list of a data source, the other returns its entries as rows, page by page. Every request is checked in order: an active licence, HTTPS, the wrong-key lockout for the caller’s address, the data source id and key (compared as a salted HMAC hash in constant time), the IP allowlist and the rate limit. Only the allowlisted fields are read from each entry; a request for any other field is refused without returning a value. Looker Studio date ranges become entry date filters in your site’s time zone. The community connector, written in Apps Script, runs in your own Google account: it keeps the endpoint URL, data source id and key in its private properties, sends the key in a request header and turns the answers into the field types Looker Studio expects. The add-on itself makes no outside HTTP request beyond the licence and update checks.