Linking Lokalise as a source
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.
The Lokalise connector syncs your localization and translation data into the PostHog data warehouse, so you can analyze your translation projects alongside your product data.
Prerequisites
You need a Lokalise account with permission to create API tokens. A read-only token is sufficient.
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.
When linking Lokalise, you'll need:
- API token – create one in your Lokalise personal profile settings. A read-only token is sufficient.
The token must have read access to the projects you want to sync. The source imports data from all projects the token can access.
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_attimestamp). 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 Lokalise tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
projects | Localization projects that the API token can access. | Full refresh | — | — |
keys | Translation keys and their metadata in each project. | Full refresh | — | — |
translations | Translations for each key and language in a project. | Full refresh | — | — |
languages | Languages configured in each project. | Full refresh | — | — |
contributors | Project contributors and their access permissions. | Full refresh | — | — |
comments | Comments on translation keys in each project. | Full refresh | — | — |
screenshots | Screenshot metadata and links attached to project keys. | Full refresh | — | — |
tasks | Translation tasks and their status in each project. | Full refresh | — | — |
Troubleshooting
- If you see an authentication error, your API token is invalid or has been revoked. Create a new token in your Lokalise profile settings, then reconnect.
- If a table syncs no rows, the token may not have access to that project. Check the token's project permissions in Lokalise, then reconnect.
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.