Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

next
mdx 21 lines 1.71 KB
Raw
1 ---
2 title: "PostHog connections: set your data region (US or EU) per connection"
3 description: "The PostHog region is now a per-connection setting. Existing connections keep their current region, so nothing changes for you."
4 date: "2026-06-17"
5 ---
6
7 The PostHog **region** (`us` or `eu`) now lives on the **connection** instead of the auth config. Region is genuinely per-connection — different users can sit in different PostHog regions — so fixing it at the auth config forced everyone through one region. Each connection now carries its own.
8
9 You don't need to do anything. We migrated every existing connection with no re-auth: connections on the default (`us`) stay on `us`, and any that used another region such as `eu` keep that value.
10
11 ### Going forward
12
13 - Set `us` (US Cloud) or `eu` (EU Cloud) on the connection. The host is built as `<region>.posthog.com`, so a full URL won't work and self-hosted PostHog isn't supported.
14 - **[Link flow](/reference/api-reference/connected-accounts/postConnectedAccountsLink)**: the Region field appears when the user connects, prefilled with your default and editable.
15 - **[Initiate flow](/reference/api-reference/connected-accounts/postConnectedAccounts)**: you set the region, and the end user never sees it.
16
17 ### Setting a default on your auth config
18
19 An auth config's region default lives in its `shared_credentials`. If you were on the default (`us`), nothing was written there. To pin a region explicitly, set `shared_credentials` when you [create an auth config](/reference/api-reference/auth-configs/postAuthConfigs), or [patch an existing one](/reference/api-reference/auth-configs/patchAuthConfigsByNanoid).
20
21 See the [PostHog toolkit docs](/toolkits/posthog) for the current connection fields.