From 810b0ea7401718cd9faa95cbdec4ab33d998c6d5 Mon Sep 17 00:00:00 2001 From: Zach Waterfield Date: Mon, 18 Mar 2024 16:07:29 -0400 Subject: [PATCH] Update frontend/src/scenes/onboarding/OnboardingReverseProxy.tsx Co-authored-by: Raquel Smith --- .../scenes/onboarding/OnboardingReverseProxy.tsx | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/frontend/src/scenes/onboarding/OnboardingReverseProxy.tsx b/frontend/src/scenes/onboarding/OnboardingReverseProxy.tsx index 6ef969bfc09ce8..4d5c5c2797b4f8 100644 --- a/frontend/src/scenes/onboarding/OnboardingReverseProxy.tsx +++ b/frontend/src/scenes/onboarding/OnboardingReverseProxy.tsx @@ -66,16 +66,15 @@ export const OnboardingReverseProxy = ({ stepKey }: { stepKey: OnboardingStepKey } >
-

A reverse proxy allows you to send events to PostHog Cloud using your own domain.

+

A reverse proxy allows you to retrieve flag information from PostHog Cloud using your own domain.

- This means that events are sent from your own domain and are less likely to be intercepted by - tracking blockers. You'll be able to capture more usage data without having to self-host PostHog. + Network calls to and from your own domain and are less likely to be intercepted by + tracking blockers. With a reverse proxy, all your users will be exposed to the flag + variants you intend. (Plus, you'll get more accurate event tracking, too!)

- Setting up a reverse proxy means setting up a service to redirect requests from a subdomain you - choose (like e.yourdomain.com) to PostHog. It is best - practice to use a subdomain that does not include posthog, analytics, tracking, or other similar - words. + This step is optional, especially as you are getting started. If you aren't the + right person to set this up, invite a team member to do it for you.

Documentation

Here are some popular reverse proxy options: