> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking DebugBear as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/debugbear

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).

## On this page

- [Prerequisites](#prerequisites)
- [Adding a data source](#adding-a-data-source)
- [Sync modes](#sync-modes)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Troubleshooting](#troubleshooting)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

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.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

The DebugBear connector syncs your website performance monitoring data – projects and synthetic Lighthouse / Core Web Vitals test results – into the PostHog Data Warehouse. This lets you analyze web performance metrics alongside your product data, join performance scores with user behavior, and track Core Web Vitals trends over time.

## Prerequisites

You need a [DebugBear](https://www.debugbear.com) account with an Admin API key. Generate one from **Account settings** > **API Keys** in DebugBear – see the [DebugBear API docs](https://www.debugbear.com/docs/api) for details.

An Admin key is required so PostHog can list every monitored project in your account.

## Adding a data source

1.  In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section.
2.  Click **\+ New source** and click **Link** next to this source.
3.  Enter your credentials (see [Configuration](#configuration) below) and click **Next**.
4.  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 DebugBear, you'll need:

-   **API key** – an Admin API key from your DebugBear account settings. Go to **Account settings** > **API Keys** and generate a new key.

## 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](https://posthog.com/docs/data-pipelines/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them.

The `PageMetrics` table supports incremental syncs on the `analysis_date` field. The `Projects` table is full refresh only.

## Configuration

| Option | Description |
| --- | --- |
| `API key` **Type:** password **Required:** True | Use an Admin API key so PostHog can list every monitored project. Generate one from DebugBear's account settings — see the [API docs](https://www.debugbear.com/docs/api). |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `Projects` | A DebugBear project — a group of monitored pages that share alerting and reporting settings. | Full refresh | — | — |
| `Pages` | A monitored page inside a DebugBear project — the URL, its test schedule, and the device it is tested on. | Full refresh | — | — |
| `PageMetrics` | A single synthetic (Lighthouse-based) lab test result for a monitored page — performance/accessibility/SEO scores, Core Web Vitals, and page weight for one build. | Incremental, Full refresh | analysis\_date | — |
| `RumMetrics` | Real user monitoring aggregates for a project, one row per metric per day. Values are the 75th percentile by default and cover the page views recorded in that day. | Incremental, Full refresh | date | — |
| `RumPageViews` | An individual real user page view, with the metric values, page, device, and location recorded for it. | Incremental, Full refresh | date | — |
| `Annotations` | A timeline annotation marking an event, such as a release or a configuration change, on a project's performance charts. | Full refresh | — | — |

## Troubleshooting

-   If you see a **401 error**, your API key is invalid or expired. Generate a new key from **Account settings** > **API Keys** in DebugBear, then reconnect.
-   If you see a **403 error**, your API key doesn't have sufficient permissions. Make sure you're using an Admin API key, not a read-only key.

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](https://posthog.com/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.