Liftable and PostHog: landing-page sessions from your own product analytics

What connecting it does for you

• Landing-page sessions and how many reached cart or checkout, from your own analytics, beside a landing-page opportunity.

What Liftable reads

• One aggregate HogQL query a day: sessions and cart or checkout reach by landing path, top 50, last 28 days.

What Liftable can write

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

What it never reads or does

• Distinct ids, session ids or query strings are not stored.
• No person-level data leaves PostHog.

The permissions requested

• query:read
• project:read

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

• OAuth on PostHog Cloud (US or EU) from the Connections page, where Liftable’s signing key is configured.
• Or a personal API key with the same two scopes, your project id and your host, which is the only door for self-hosted PostHog.

How often, and where the data lands

Daily. A rate limit parks the row and the next run resumes after it.

Questions