Linking Expo (EAS) as a source

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

Alpha release

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

The Expo connector syncs EAS builds and store submissions for one project into the PostHog data warehouse, so you can track build duration, queue time, and failure reasons alongside your product data.

Prerequisites

An Expo account with access to the project you want to sync, and an access token. A robot user's token works too, and is the better choice for a shared integration.

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.

Create a personal access token at expo.dev under Access tokens.

You'll be asked for:

Access token: a personal or robot access token.
Project ID: run eas project:info to see it, or copy it from the project page on expo.dev.

One source syncs one project, so add a source per project you want to track.

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.

Both tables are full refresh. EAS pages these collections by offset and offers no date filter, so each sync replaces the contents of the table.

Configuration

Option	Description
`Access token` Type: password Required: True	A personal or robot access token, created at expo.dev under Access tokens.
`Project ID` Type: text Required: True	Run `eas project:info` to see this, or copy it from the project page on expo.dev.

Supported tables

Table	Description	Sync method	Incremental field	Primary key
`builds`	An EAS Build job for the project, with its platform, outcome, and timing.	Full refresh	—	—
`submissions`	An EAS Submit job that uploaded a build to the App Store or Google Play.	Full refresh	—	—

Troubleshooting

If the connection fails with an authorization error, the access token is wrong or has been revoked. Create a new one at expo.dev under Access tokens, then reconnect the source.
If the connection reports that the project cannot be read, check the project ID and that the token belongs to the account that owns the project.

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.