Integrations · Analytics Built · awaiting Google’s verification of the OAuth app

Liftable and Google Analytics 4: channel context on every opportunity

Liftable reads landing page by channel from GA4, read-only, so each opportunity says which traffic it affects. Google OAuth with one read-only scope; test users only until Google verifies the app.

Status as of 6 October 2026
Read-only

Scan your store Security and data

What connecting it does for you

Which channel and campaign send the shoppers each opportunity affects, so a product-page finding can say ‘mostly paid social, mostly mobile’.

What Liftable reads

Sessions by landing page and channel, from the GA4 Data API.

What Liftable can write

Nothing. This connector is read-only: there is no write call in it.

What it never reads or does

Nothing is written to GA4.
No user-level data: the Data API returns aggregates, and that is all that is requested.

The permissions requested

https://www.googleapis.com/auth/analytics.readonly

These are the permissions the connector asks the vendor for, as the vendor names them. The Connections page shows the same list on the row before you connect.

How to connect

Connect with Google from the Connections page. analytics.readonly is a sensitive scope, so until Google has verified Liftable’s app only test users can connect; the row says so.

How often, and where the data lands

Hourly, into a per-store table of landing page by channel.

Questions

Why only test users?

Google treats analytics.readonly as a sensitive scope and requires an app verification before the public can grant it. The verification is in progress; the code is built and tested against Google’s API.

Solutions it feeds

Also in analytics

Last reviewed against the product on 6 October 2026.

Scan your store.

See where your store is losing revenue and what to fix first. It is free, takes about a minute, and needs no install.

Scan your store