Linking Embrace 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.
This source is currently in alpha. The interface and available tables may change.
The Embrace connector syncs mobile observability data from Embrace.io into the PostHog data warehouse, so you can analyze your mobile app metrics alongside your product data.
Prerequisites
You need an Embrace account with access to the Metrics API. You'll need:
- Metrics API token – found in your Embrace dashboard under Settings > Organization > API.
- App ID – your Embrace application identifier.
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 Embrace, you'll need:
Metrics API token – get this from your Embrace dashboard under Settings > Organization > API.
App ID – your Embrace application identifier.
Region – select your Embrace region:
- Default (
api.embrace.io) - United States (US1) (
api-us1.embrace.io) - European Union (EU1) (
api-eu1.embrace.io)
- Default (
If you change your region, you'll need to re-enter your API token. Make sure to select the region that matches your Embrace account.
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.
Important limitations:
- Imports cover the latest 30 days of hourly metrics only. Older data cannot be recovered by this source.
- Data has a one-hour delay from Embrace.
- Incremental syncs overlap the previous hour and merge by label hash plus timestamp. This retains older imported rows.
- Full refresh replaces the entire table with the latest 30 days of data.
Available tables
| Table | Description | Sync method |
|---|---|---|
sessions | Hourly counts of session parts. Embrace metric names use "sessions" to mean session parts. | Incremental or full refresh |
crashes | Hourly crash counts for Android and iOS apps. | Incremental or full refresh |
network_4xx | Hourly counts of network errors with HTTP status codes in the 400 range. | Incremental or full refresh |
network_5xx | Hourly counts of network errors with HTTP status codes in the 500 range. | Incremental or full refresh |
Table schema
All tables share the same schema:
| Column | Description |
|---|---|
series_id | Stable hash of all metric labels, including the metric name. |
timestamp | UTC timestamp of the hourly metric sample. |
value | Metric value for this hour and label combination. Non-finite values are null. |
labels | Metric labels, including app ID, app version, OS version, and device model. |
Configuration
| Option | Type | Required |
|---|---|---|
Metrics API token | password | Yes |
App ID | text | Yes |
Region | select | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
sessions | Hourly counts of session parts. Embrace metric names use sessions to mean session parts. | Incremental, Full refresh | timestamp | — |
crashes | Hourly crash counts for Android and iOS apps. | Incremental, Full refresh | timestamp | — |
network_4xx | Hourly counts of network errors with HTTP status codes in the 400 range. | Incremental, Full refresh | timestamp | — |
network_5xx | Hourly counts of network errors with HTTP status codes in the 500 range. | Incremental, Full refresh | timestamp | — |
Troubleshooting
- Authentication error (401): Your API token was rejected. Get a new Metrics API token from Settings > Organization > API in your Embrace dashboard.
- Access denied (403): Check that your Metrics API token, app ID, and region are all correct.
- Missing data: This source only imports the latest 30 days of data with a one-hour delay.
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.