Linking LogRocket as a source

Alpha release

This source is currently in alpha. The interface and available tables may change.

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

Learn more

Note: This connector is in alpha. The interface and available tables may change.

The LogRocket connector syncs audit logs and session events into the PostHog data warehouse, so you can analyze them alongside your product data.

Prerequisites

A LogRocket account on the Professional plan (required for audit logging).
An API key created in LogRocket under Settings > API Keys.
If you want to sync session events, the legacy Data Export add-on must be enabled. LogRocket has deprecated this add-on for SaaS accounts, so it may not be available.

Adding a data source

In PostHog, go to the Sources tab of the data pipeline section.
Click + New source and click Link next to this source.
Enter your credentials (see Configuration below) and click Next.
Select the tables you want to sync, choose a sync method and frequency, then click Import.

Once the syncs are complete, you can start querying this data in PostHog.

You need three values to connect:

API key – create one in LogRocket under Settings > API Keys. PostHog authenticates with the Authorization: token <key> header.
Organization ID – the organization ID in your LogRocket project URL.
Project ID – the project ID in your LogRocket project URL.

This source connects to api.logrocket.com. Self-hosted LogRocket instances aren't supported.

Sync modes

Each table can be synced in one of several modes, depending on what the source supports:

Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
Incremental – only new or updated rows are synced on each run, using a cursor field (such as an updated_at timestamp). Cheaper than a full refresh, but deletes aren't captured.
Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.

See sync methods for a full explanation of how each mode works and how to choose between them.

All LogRocket tables use full refresh. Each sync replaces the contents of the table.

Configuration

Option	Description
`API key` Type: password Required: True
`Organization ID` Type: text Required: True	The organization ID in your LogRocket project URL.
`Project ID` Type: text Required: True	The project ID in your LogRocket project URL.

Supported tables

Table	Description	Sync method	Incremental field	Primary key
`audit_logs`	Administrative actions and session access recorded in the LogRocket audit log.	Full refresh	—	—
`session_events`	Session metadata, user traits, navigation, clicks, errors, network events, and custom events from legacy exports.	Full refresh	—	export_file_id, export_line

The session_events table is disabled by default because the Data Export add-on is deprecated for SaaS accounts. Enable it manually if you have the add-on active.

Troubleshooting

Authorization error (401) – LogRocket rejected your API key. Create a new key in Settings > API Keys, then reconnect the source.
Forbidden error (403) – LogRocket denied access. Check the API key permissions and confirm the required audit or export add-on is enabled for your account.
Session events table shows no data – The legacy Data Export add-on must be enabled. Check your LogRocket account settings to confirm it's active.

If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.