Posthog Integration - Custom Domain

[orcist]

What's your feature/idea?

Current Posthog Integration doesn't allow customization of URL. Some ad blockers have recently started blocking requests to the official posthog domain, which means we are losing usage data of about 30-50% of users. Posthog introduced the reverse proxy feature which allows configuring a custom domain to bypass this problem, but this is not configurable in the gitbook integration.

What's your desired outcome?

Restore Posthog Integration functionality by allowing configuration of custom domain for the Posthog SDK.

What's the impact of this for you?

Critical

Anything else?

No response

[addisonschultz]

Hi @orcist - I’m having a look at this. Can you please help me test out a beta version?

Can you please install https://app.gitbook.com/integrations/posthog-reverse-proxy-beta and test it with your proxied endpoint?

[orcist]

tested, seems to be working correctly! thank you 🙏

[addisonschultz]

Thank you! I’ll work on getting this live in the main version - Please keep an eye on this PR: GitbookIO/integrations#1164

I would recommend to continue using the main version instead of this beta testing version you’ve just tested, as that one will not be maintained or updated after this!

[orcist]

thank you as well! I'll use the beta version until the PR is merged and then switch back.

[mahum-26]

Allow setting a custom domain for PostHog in the integration so tracking isn’t blocked by ad blockers. This would restore accurate analytics by routing requests through a user-controlled domain instead of the default one.