Linking Bettermode as a source
This source is currently in alpha. The interface and available tables may change.
The Bettermode (formerly Tribe) connector syncs your community data into the PostHog Data Warehouse, so you can join community activity (members, spaces, posts, replies, and moderation items) with your product, CRM, and support data.
Prerequisites
You need a Bettermode plan with API access, and permission to create an app in the Bettermode developer portal. The app must be published and installed on your community before PostHog can connect.
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 Bettermode, you'll need:
- Region – where your community is hosted. Most communities use the US region; pick EU if your community is hosted in Bettermode's EU (eu-central-1) region.
- Client ID and Client secret – from your app in the Bettermode developer portal. Create an app, publish it, and install it on your community.
- Network ID – your community's unique ID, shown for your community in the developer portal.
PostHog exchanges the client ID and secret for a short-lived app access token, and refreshes it automatically on every sync.
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.
The posts table supports incremental syncs on createdAt, publishedAt, or updatedAt. Other tables sync as full refreshes: Bettermode's API doesn't expose server-side timestamp filters for them.
Configuration
| Option | Type | Required |
|---|---|---|
Region | select | Yes |
Client ID | text | Yes |
Client secret | password | Yes |
Network ID | text | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
members | People in the community, including their profile, role, and activity timestamps. | Full refresh | — | — |
spaces | Spaces (groups, channels, or sections) that organize the community's content. | Full refresh | — | — |
posts | Top-level posts published in the community's spaces, including reaction summaries. | Incremental, Full refresh | createdAt, publishedAt, updatedAt | — |
replies | Fetches direct replies of every post that has replies (one request per post), so syncs scale with the number of posts in the community | Full refresh | — | — |
tags | Tags available for categorizing posts in the community. | Full refresh | — | — |
moderation_items | Items (posts or members) flagged for moderation review, with their resolution status. | Full refresh | — | — |
Reaction data is included on each post and reply row: reactionsCount holds the total, and reactions holds a per-reaction summary of {reaction, count} objects.
The replies table fetches the direct replies of every post that has replies, one post at a time, so its sync time grows with the size of your community.
Troubleshooting
- App not found – the client ID or secret is wrong. Copy both again from your app in the developer portal.
- Forbidden / access errors – the app isn't published and installed on the community, or the network ID doesn't match the community the app is installed on.
- Slow syncs – Bettermode rate-limits API traffic per 10-second window and per day. PostHog honors these limits and retries automatically, but very large communities may take a while to backfill, especially the replies table.
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.