Merge branch 'master' into docs-writer-ai-update-2026-02-27T22-37-27-813Z-ydcabm

Author: willwearing

contents/blog/best-inapp-survey-tools.mdx

@@ -1,23 +1,18 @@
 ---
+date: 2026-02-26
 title: The best in-app survey tools for product teams, compared
-date: 2026-02-23
 rootPage: /blog
-sidebar: Blog
-showTitle: true
-hideAnchor: true
-author:
-    - jina-yoon
 featuredImage: >-
     https://res.cloudinary.com/dmukukwp6/image/upload/v1720536764/posthog.com/contents/surveys-hog.png
 featuredImageType: full
+author:
+    - jina-yoon
 category: General
 tags:
     - Comparisons
 seo:
-    {
-        metaTitle: 'The best in-app survey tools for product teams, compared',
-        metaDescription: 'Compare the top in-app survey tools. See how PostHog, Hotjar, Sprig, Survicate, Pendo, and SurveyMonkey stack up for collecting user feedback.',
-    }
+    metaTitle: The best in-app survey tools for product teams, compared
+    metaDescription: Compare the top in-app survey tools. See how PostHog, Hotjar, Sprig, Survicate, Pendo, and SurveyMonkey stack up for collecting user feedback.
 ---
 
 import { CalloutBox } from 'components/Docs/CalloutBox'

contents/blog/best-mobile-app-analytics-tools.mdx

@@ -1,5 +1,5 @@
 ---
-date: 2026-02-06
+date: 2026-02-26
 title: The 7 best mobile app analytics tools
 rootPage: /blog
 featuredImage: >-

contents/docs/_snippets/identify-backend-callout.mdx

@@ -0,0 +1,3 @@
+> **Identifying users is required.** Backend events need a `distinct_id` that matches the ID your frontend uses when calling `posthog.identify()`. Without this, backend events are orphaned — they can't be linked to frontend event captures, [session replays](/docs/session-replay), [LLM traces](/docs/ai-engineering), or [error tracking](/docs/error-tracking).
+>
+> See our guide on [identifying users](/docs/getting-started/identify-users) for how to set this up.

contents/docs/_snippets/identify-frontend-callout.mdx

@@ -0,0 +1,3 @@
+> **Identifying users is required.** Call `posthog.identify('your-user-id')` after login to link events to a known user. This is what connects frontend event captures, [session replays](/docs/session-replay), [LLM traces](/docs/ai-engineering), and [error tracking](/docs/error-tracking) to the same person — and lets backend events link back too.
+>
+> See our guide on [identifying users](/docs/getting-started/identify-users) for how to set this up.

contents/docs/advanced/proxy/_snippets/managed-reverse-proxy.mdx

@@ -21,7 +21,7 @@ If you're onboarding a web-based product like Web Analytics, Surveys, or LLM Ana
 
 <CalloutBox icon="IconInfo" title="Before you start" type="fyi">
 
-Choose a neutral subdomain that doesn't include words like `analytics`, `tracking`, `telemetry`, or `posthog`. Ad blockers target obvious terms.
+Choose a neutral subdomain that doesn't include words like `analytics`, `tracking`, `telemetry`, `posthog`, or `ph`. Ad blockers target these terms. If ad blockers block your domain, the proxy won't achieve its intended effect.
 
 </CalloutBox>
 
@@ -35,7 +35,11 @@ Go to your DNS provider and create a new **CNAME record**:
 2. Set the **Target** to the proxy domain PostHog generated in the previous step. You'll see it in your proxy settings, it looks like `4854cf84789d8596ad01.proxy-us.posthog.com`
 3. Save the record
 
-> **Note:** If you're using Cloudflare, disable proxying on this CNAME record by clicking the cloud icon and set it to **DNS only**. Cloudflare's proxy interferes with PostHog's SSL certificate provisioning.
+<CalloutBox icon="IconWarning" title="Disable DNS provider proxy features" type="caution">
+
+If you're using a DNS provider like Cloudflare that offers proxy options (orange cloud), make sure the proxy is **disabled** (gray cloud) for this CNAME record. Enabling the proxy at your DNS provider may interfere with PostHog's managed reverse proxy functionality and SSL certificate provisioning.
+
+</CalloutBox>
 
 </Step>
 

contents/docs/advanced/proxy/cloudflare.mdx

@@ -161,7 +161,7 @@ In the Cloudflare dashboard, follow [Cloudflare's custom domains guide](https://
 
 Using your own domain instead of the default `*.workers.dev` domain makes the proxy less likely to be blocked. Ad blockers recognize and block `*.workers.dev` patterns.
 
-Avoid obvious terms like `tracking`, `analytics`, `posthog`, or `telemetry` in your subdomain name. Use something neutral like `e`, `ph`, or `ingest` instead.
+Avoid obvious terms like `tracking`, `analytics`, `posthog`, `telemetry`, or `ph` in your subdomain name. Use something neutral like `e`, `t`, or `ingest` instead.
 
 </Step>
 
@@ -227,7 +227,7 @@ Configure the record:
 
 The CNAME points your subdomain to PostHog's proxy endpoint. The orange cloud means Cloudflare will proxy the traffic instead of just doing DNS resolution.
 
-Avoid obvious terms like `tracking`, `analytics`, `posthog`, or `telemetry` in your subdomain. Use something neutral like `e`, `ph`, or `ingest` instead.
+Avoid obvious terms like `tracking`, `analytics`, `posthog`, `telemetry`, or `ph` in your subdomain. Use something neutral like `e`, `t`, or `ingest` instead.
 
 </Step>
 

contents/docs/advanced/proxy/proxy-reference.mdx

@@ -23,7 +23,7 @@ Check your project URL in the [PostHog app](https://app.posthog.com) to confirm
 - Allow `GET` and `POST`** on all paths.
 - Support 64MB request bodies, session recordings can be large.
 - Forward `X-Forwarded-For` to preserve client IPs for geolocation.
-- Avoid obvious paths** like `/analytics` or `/posthog`, use `/e` or `/ph` instead.
+- Avoid obvious paths like `/analytics`, `/posthog`, or `/ph`. Use `/e` or `/ingest` instead.
 
 ### SDK configuration
 
@@ -81,14 +81,14 @@ Use a relative path to avoid cross-origin issues:
 
 ```js file=US
 posthog.init('<ph_project_token>', {
-  api_host: '/ph',
+  api_host: '/ingest',
   ui_host: 'https://us.posthog.com'
 })
 ```
 
 ```js file=EU
 posthog.init('<ph_project_token>', {
-  api_host: '/ph',
+  api_host: '/ingest',
   ui_host: 'https://eu.posthog.com'
 })
 ```

contents/docs/ai-engineering/ai-wizard.mdx

@@ -2,6 +2,8 @@
 title: AI wizard
 ---
 
+import WizardInstall from 'getting-started/_snippets/wizard.mdx'
+
 The PostHog wizard automatically installs and instruments PostHog into your application codebase using AI. It's an agentic CLI tool that handles the entire PostHog integration process on your behalf.
 
 Set up the PostHog platform in minutes, with a single command.

contents/docs/integrations/replit.mdx

@@ -5,8 +5,6 @@ icon: >-
   https://res.cloudinary.com/dmukukwp6/image/upload/replit_logo_9526a2cdb8.svg
 ---
 
-import { CalloutBox } from 'components/Docs/CalloutBox'
-
 <iframe
     width="560"
     height="315"
@@ -27,12 +25,6 @@ import ReplitBadge from 'components/ReplitBadge'
 2. When prompted, log in to PostHog to authorize access
 3. The PostHog MCP server is now available in your Replit Agent
 
-<CalloutBox icon="IconFlag" title="EU region users" type="fyi">
-
-If your PostHog project is on EU Cloud, use `https://mcp-eu.posthog.com/mcp` instead.
-
-</CalloutBox>
-
 ## Set up PostHog in your project
 
 Once connected, give Replit Agent this prompt to add PostHog with error tracking and source maps:

contents/docs/integrations/v0.mdx

@@ -3,8 +3,6 @@ title: v0 integration
 sidebarTitle: v0
 ---
 
-import { CalloutBox } from 'components/Docs/CalloutBox'
-
 The PostHog MCP lets v0 query your analytics data, investigate errors, manage feature flags, and run experiments - all through natural language.
 
 ## Connect PostHog to v0
@@ -19,12 +17,6 @@ The PostHog MCP lets v0 query your analytics data, investigate errors, manage fe
 
 The PostHog MCP server is now available in your v0 chats.
 
-<CalloutBox icon="IconFlag" title="EU region users" type="fyi">
-
-If your PostHog project is on EU Cloud, use `https://mcp-eu.posthog.com/mcp` instead.
-
-</CalloutBox>
-
 ## Set up PostHog in your project
 
 Once connected, give v0 this prompt to add PostHog with the Vercel Flags SDK: