vybekiit 0.7.33 → 0.7.35

package/dist/global-skills/instrument-product-analytics/references/ruby.md

@@ -2,6 +2,26 @@
 
 # Ruby
 
+Canonical URL: https://posthog.com/docs/libraries/ruby
+
+> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://app.posthog.com` (app host for links).
+
+## On this page
+
+- [Installation](#installation)
+- [Configuration](#configuration)
+- [Identifying users](#identifying-users)
+- [Capturing events](#capturing-events)
+- [Person profiles and properties](#person-profiles-and-properties)
+- [Alias](#alias)
+- [Feature flags](#feature-flags)
+- [Experiments (A/B tests)](#experiments-ab-tests)
+- [Group analytics](#group-analytics)
+- [Exception capture](#exception-capture)
+- [Debug mode](#debug-mode)
+- [Test helpers](#test-helpers)
+- [Thank you](#thank-you)
+
 The `posthog-ruby` library provides tracking functionality on the server-side for applications built in Ruby.
 
 It uses an internal queue to make calls fast and non-blocking. It also batches requests and flushes asynchronously, making it perfect to use in any part of your web app or other server-side application that needs performance.
@@ -12,16 +32,12 @@ It uses an internal queue to make calls fast and non-blocking. It also batches r
 
 Add this to your `Gemfile`:
 
-Terminal
-
 ```bash
 gem "posthog-ruby"
 ```
 
 In your app, set your API key **before** making any calls. If setting a custom `host`, make sure to include the protocol (e.g. `https://`).
 
-Ruby
-
 ```ruby
 require 'posthog'
 
@@ -38,8 +54,6 @@ You can find your project token and instance address in the [project settings](h
 
 Initialize the client with your project token before making any calls:
 
-Ruby
-
 ```ruby
 require 'posthog'
 
@@ -73,8 +87,6 @@ Available client options:
 
 Use `before_send` to add, modify, or drop events immediately before the SDK queues or sends them:
 
-Ruby
-
 ```ruby
 posthog = PostHog::Client.new({
   api_key: '<ph_project_token>',
@@ -92,8 +104,6 @@ posthog = PostHog::Client.new({
 
 For short-lived scripts, call `flush` before the process exits. Call `shutdown` when your application is stopping to flush pending events and stop background resources.
 
-Ruby
-
 ```ruby
 posthog.capture({ distinct_id: 'user_123', event: 'script_finished' })
 posthog.flush
@@ -102,14 +112,12 @@ posthog.shutdown
 
 ## Identifying users
 
-> **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.md), [LLM traces](/docs/ai-engineering.md), or [error tracking](/docs/error-tracking.md).
+> **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](https://posthog.com/docs/session-replay.md), [LLM traces](https://posthog.com/docs/ai-engineering.md), or [error tracking](https://posthog.com/docs/error-tracking.md).
 >
-> See our guide on [identifying users](/docs/getting-started/identify-users.md) for how to set this up.
+> See our guide on [identifying users](https://posthog.com/docs/getting-started/identify-users.md) for how to set this up.
 
 Identify a user and set their person properties with `identify`:
 
-Ruby
-
 ```ruby
 posthog.identify({
   distinct_id: 'distinct_id_of_your_user',
@@ -124,8 +132,6 @@ posthog.identify({
 
 You can send custom events using `capture`:
 
-Ruby
-
 ```ruby
 posthog.capture({
     distinct_id: 'distinct_id_of_the_user',
@@ -137,9 +143,7 @@ posthog.capture({
 
 ### Setting event properties
 
-Optionally, you can include additional information with the event by including a [properties](/docs/data/events.md#event-properties) object:
-
-Ruby
+Optionally, you can include additional information with the event by including a [properties](https://posthog.com/docs/data/events.md#event-properties) object:
 
 ```ruby
 posthog.capture({
@@ -156,8 +160,6 @@ posthog.capture({
 
 If you're aiming for a backend-only implementation of PostHog and won't be capturing events from your frontend, you can send `pageviews` from your backend like so:
 
-Ruby
-
 ```ruby
 posthog.capture({
     distinct_id: 'distinct_id_of_the_user',
@@ -184,9 +186,7 @@ posthog.capture({
 
 ## Person profiles and properties
 
-The Ruby SDK captures identified events by default. These create [person profiles](/docs/data/persons.md). To set [person properties](/docs/product-analytics/person-properties.md) in these profiles, include them when capturing an event:
-
-Ruby
+The Ruby SDK captures identified events by default. These create [person profiles](https://posthog.com/docs/data/persons.md). To set [person properties](https://posthog.com/docs/product-analytics/person-properties.md) in these profiles, include them when capturing an event:
 
 ```ruby
 posthog.capture({
@@ -199,11 +199,9 @@ posthog.capture({
 })
 ```
 
-For more details on the difference between `$set` and `$set_once`, see our [person properties docs](/docs/product-analytics/person-properties.md#what-is-the-difference-between-set-and-set_once).
-
-To capture [anonymous events](/docs/data/anonymous-vs-identified-events.md) without person profiles, set the event's `$process_person_profile` property to `false`:
+For more details on the difference between `$set` and `$set_once`, see our [person properties docs](https://posthog.com/docs/product-analytics/person-properties.md#what-is-the-difference-between-set-and-set_once).
 
-Ruby
+To capture [anonymous events](https://posthog.com/docs/data/anonymous-vs-identified-events.md) without person profiles, set the event's `$process_person_profile` property to `false`:
 
 ```ruby
 posthog.capture({
@@ -221,8 +219,6 @@ Sometimes, you want to assign multiple distinct IDs to a single user. This is he
 
 In this case, you can use `alias` to assign another distinct ID to the same user.
 
-Ruby
-
 ```ruby
 posthog.alias({
   distinct_id: 'distinct_id',
@@ -230,11 +226,11 @@ posthog.alias({
 })
 ```
 
-We strongly recommend reading our docs on [alias](/docs/product-analytics/identify.md#alias-assigning-multiple-distinct-ids-to-the-same-user) to best understand how to correctly use this method.
+We strongly recommend reading our docs on [alias](https://posthog.com/docs/product-analytics/identify.md#alias-assigning-multiple-distinct-ids-to-the-same-user) to best understand how to correctly use this method.
 
 ## Feature flags
 
-PostHog's [feature flags](/docs/feature-flags.md) enable you to safely deploy and roll back new features as well as target specific users and groups with them.
+PostHog's [feature flags](https://posthog.com/docs/feature-flags.md) enable you to safely deploy and roll back new features as well as target specific users and groups with them.
 
 There are two steps to implement feature flags in Ruby:
 
@@ -244,8 +240,6 @@ Call `posthog.evaluate_flags()` once for the user, then read values from the ret
 
 #### Boolean feature flags
 
-Ruby
-
 ```ruby
 flags = posthog.evaluate_flags('distinct_id_of_your_user')
 
@@ -258,8 +252,6 @@ end
 
 #### Multivariate feature flags
 
-Ruby
-
 ```ruby
 flags = posthog.evaluate_flags('distinct_id_of_your_user')
 
@@ -278,9 +270,9 @@ end
 
 ### Step 2: Include feature flag information when capturing events
 
-If you want use your feature flag to breakdown or filter events in your [insights](/docs/product-analytics/insights.md), you'll need to include feature flag information in those events. This ensures that the feature flag value is attributed correctly to the event.
+If you want use your feature flag to breakdown or filter events in your [insights](https://posthog.com/docs/product-analytics/insights.md), you'll need to include feature flag information in those events. This ensures that the feature flag value is attributed correctly to the event.
 
-> **Note:** This step is only required for events captured using our server-side SDKs or [API](/docs/api.md).
+> **Note:** This step is only required for events captured using our server-side SDKs or [API](https://posthog.com/docs/api.md).
 
 There are two methods you can use to include feature flag information in your events:
 
@@ -288,8 +280,6 @@ There are two methods you can use to include feature flag information in your ev
 
 Pass the same `flags` object that you used for branching. This attaches the exact flag values from that evaluation and doesn't make another `/flags` request.
 
-Ruby
-
 ```ruby
 flags = posthog.evaluate_flags('distinct_id_of_your_user')
 
@@ -308,8 +298,6 @@ By default, this attaches every flag in the snapshot using `$feature/<flag-key>`
 
 To reduce event property bloat, pass a filtered snapshot:
 
-Ruby
-
 ```ruby
 # Attach only flags accessed with enabled?() or get_flag() before this call
 posthog.capture({
@@ -332,8 +320,6 @@ posthog.capture({
 
 In the event properties, include `$feature/feature_flag_name: variant_key`:
 
-Ruby
-
 ```ruby
 posthog.capture({
     distinct_id: 'distinct_id_of_your_user',
@@ -349,8 +335,6 @@ posthog.capture({
 
 By default, `evaluate_flags()` evaluates every flag for the user. If you only need a few flags, pass `flag_keys` to request only those flags:
 
-Ruby
-
 ```ruby
 flags = posthog.evaluate_flags(
     'distinct_id_of_your_user',
@@ -362,8 +346,6 @@ flags = posthog.evaluate_flags(
 
 If you want to skip the remote `/flags` request and only use locally cached definitions, pass `only_evaluate_locally: true`:
 
-Ruby
-
 ```ruby
 flags = posthog.evaluate_flags(
     'distinct_id_of_your_user',
@@ -375,8 +357,6 @@ flags = posthog.evaluate_flags(
 
 Pass `disable_geoip: true` to disable GeoIP lookup for remote flag evaluation:
 
-Ruby
-
 ```ruby
 flags = posthog.evaluate_flags(
     'distinct_id_of_your_user',
@@ -386,7 +366,7 @@ flags = posthog.evaluate_flags(
 
 ### Sending `$feature_flag_called` events
 
-Capturing `$feature_flag_called` events enables PostHog to know when a flag was accessed by a user and provide [analytics and insights](/docs/product-analytics/insights.md) on the flag. With `evaluate_flags()`, the SDK sends this event when you call `flags.enabled?()` or `flags.get_flag()` for a flag.
+Capturing `$feature_flag_called` events enables PostHog to know when a flag was accessed by a user and provide [analytics and insights](https://posthog.com/docs/product-analytics/insights.md) on the flag. With `evaluate_flags()`, the SDK sends this event when you call `flags.enabled?()` or `flags.get_flag()` for a flag.
 
 The SDK deduplicates these events per `(distinct_id, flag, value)` in a local cache. If you reinitialize the PostHog client, the cache resets and `$feature_flag_called` events may be sent again. PostHog handles duplicates, so duplicate `$feature_flag_called` events don't affect your analytics.
 
@@ -394,14 +374,12 @@ The SDK deduplicates these events per `(distinct_id, flag, value)` in a local ca
 
 ### Advanced: Overriding server properties
 
-Sometimes, you may want to evaluate feature flags using [person properties](/docs/product-analytics/person-properties.md), [groups](/docs/product-analytics/group-analytics.md), or group properties that haven't been ingested yet, or were set incorrectly earlier.
+Sometimes, you may want to evaluate feature flags using [person properties](https://posthog.com/docs/product-analytics/person-properties.md), [groups](https://posthog.com/docs/product-analytics/group-analytics.md), or group properties that haven't been ingested yet, or were set incorrectly earlier.
 
 You can provide properties to evaluate the flag with by using the `person properties`, `groups`, and `group properties` arguments. PostHog will then use these values to evaluate the flag, instead of any properties currently stored on your PostHog server.
 
 For example:
 
-Ruby
-
 ```ruby
 flags = posthog.evaluate_flags(
     'distinct_id_of_the_user',
@@ -458,8 +436,6 @@ Simply include any of these properties in the `person_properties` parameter alon
 
 You can configure the `feature_flag_request_timeout_seconds` parameter when initializing your PostHog client to set a flag request timeout. This helps prevent your code from being blocked if PostHog's servers are too slow to respond. By default, this is set to 3 seconds.
 
-Ruby
-
 ```ruby
 posthog = PostHog::Client.new({
     # rest of your configuration...
@@ -485,14 +461,12 @@ Evaluating feature flags requires making a request to PostHog for each flag. How
 
 It is best practice to use local evaluation flags when possible, since this enables you to resolve flags faster and with fewer API calls.
 
-For details on how to implement local evaluation, see our [local evaluation guide](/docs/feature-flags/local-evaluation.md).
+For details on how to implement local evaluation, see our [local evaluation guide](https://posthog.com/docs/feature-flags/local-evaluation.md).
 
 #### Evaluating feature flags locally in unicorn server
 
 If you have `preload_app true` in your unicorn config, you can use the [`after_fork`](https://www.rubydoc.info/gems/unicorn/Unicorn%2FConfigurator:after_fork) hook (which is part of the unicorn's configuration) to enable the feature flag cache to receive the updates from PostHog.
 
-Ruby
-
 ```ruby
 after_fork do |_server, _worker|
   $posthog = PostHog::Client.new({
@@ -508,8 +482,6 @@ end
 
 If you use Puma with multiple workers, you can use the `on_worker_boot` hook (which is part of Puma's configuration) to enable the feature flag cache to receive updates from PostHog.
 
-Ruby
-
 ```ruby
 on_worker_boot do
   $posthog = PostHog::Client.new({
@@ -530,8 +502,6 @@ end
 -   `on_flag_definitions_received(data)` – stores freshly fetched definitions.
 -   `shutdown` – releases locks or other resources.
 
-Ruby
-
 ```ruby
 posthog = PostHog::Client.new({
   api_key: '<ph_project_token>',
@@ -544,17 +514,13 @@ posthog = PostHog::Client.new({
 
 Use `get_remote_config_payload` to fetch the decrypted remote config payload for a flag. This requires `personal_api_key`.
 
-Ruby
-
 ```ruby
 payload = posthog.get_remote_config_payload('flag-key')
 ```
 
 ## Experiments (A/B tests)
 
-Since [experiments](/docs/experiments/start-here.md) use feature flags, the code for running an experiment is very similar to the feature flags code:
-
-Ruby
+Since [experiments](https://posthog.com/docs/experiments/start-here.md) use feature flags, the code for running an experiment is very similar to the feature flags code:
 
 ```ruby
 flags = posthog.evaluate_flags('user_distinct_id')
@@ -565,18 +531,16 @@ if variant == 'variant-name'
 end
 ```
 
-It's also possible to [run experiments without using feature flags](/docs/experiments/running-experiments-without-feature-flags.md).
+It's also possible to [run experiments without using feature flags](https://posthog.com/docs/experiments/running-experiments-without-feature-flags.md).
 
 ## Group analytics
 
-Group analytics allows you to associate an event with a group (e.g. teams, organizations, etc.). Read the [Group Analytics](/docs/user-guides/group-analytics.md) guide for more information.
+Group analytics allows you to associate an event with a group (e.g. teams, organizations, etc.). Read the [Group Analytics](https://posthog.com/docs/user-guides/group-analytics.md) guide for more information.
 
-> **Note:** This is a paid feature and is not available on the open-source or free cloud plan. Learn more on the [pricing page](/pricing.md).
+> **Note:** This is a paid feature and is not available on the open-source or free cloud plan. Learn more on the [pricing page](https://posthog.com/pricing.md).
 
 Capture an event and associate it with a group:
 
-Ruby
-
 ```ruby
 posthog.capture({
     distinct_id: 'distinct_id_of_the_user',
@@ -593,8 +557,6 @@ posthog.capture({
 
 Update properties on a group:
 
-Ruby
-
 ```ruby
 posthog.group_identify({
   group_type: 'company',
@@ -611,16 +573,14 @@ If the optional `distinct_id` is not provided in the group identify call, it def
 
 ## Exception capture
 
-You can capture exceptions using the `posthog-ruby` library. This enables you to see stack traces and debug errors in your application. Learn more in our [error tracking docs](/docs/error-tracking/installation/ruby.md).
+You can capture exceptions using the `posthog-ruby` library. This enables you to see stack traces and debug errors in your application. Learn more in our [error tracking docs](https://posthog.com/docs/error-tracking/installation/ruby.md).
 
 **Using Rails?**
 
-The [posthog-rails](/docs/libraries/ruby-on-rails.md) gem provides automatic exception capture, ActiveJob instrumentation, and user context out of the box. See our [Rails error tracking guide](/docs/error-tracking/installation/ruby-on-rails.md) for details.
+The [posthog-rails](https://posthog.com/docs/libraries/ruby-on-rails.md) gem provides automatic exception capture, ActiveJob instrumentation, and user context out of the box. See our [Rails error tracking guide](https://posthog.com/docs/error-tracking/installation/ruby-on-rails.md) for details.
 
 For non-Rails Ruby applications, you can manually capture exceptions with `capture_exception`:
 
-Ruby
-
 ```ruby
 begin
   # Code that might raise an exception
@@ -645,9 +605,7 @@ The `capture_exception` method accepts the following parameters:
 | `additional_properties` | `Hash` | Additional properties to attach to the exception event. Optional. |
 | `flags` | `PostHog::FeatureFlagEvaluations` | Optional keyword argument. Adds the same feature flag properties as `capture({ flags: flags })`. |
 
-You can also override the [fingerprint](/docs/error-tracking/fingerprints.md) to customize how exceptions are grouped into issues:
-
-Ruby
+You can also override the [fingerprint](https://posthog.com/docs/error-tracking/fingerprints.md) to customize how exceptions are grouped into issues:
 
 ```ruby
 posthog.capture_exception(
@@ -663,16 +621,12 @@ posthog.capture_exception(
 
 The Ruby SDK logs warnings by default. You can change the log level to `DEBUG` to debug the client:
 
-Ruby
-
 ```ruby
 posthog.logger.level = Logger::DEBUG
 ```
 
 You can also replace the SDK logger globally:
 
-Ruby
-
 ```ruby
 PostHog::Logging.logger = Rails.logger
 ```
@@ -681,8 +635,6 @@ PostHog::Logging.logger = Rails.logger
 
 When `test_mode: true`, events remain queued. You can inspect and clear the queue in tests:
 
-Ruby
-
 ```ruby
 posthog = PostHog::Client.new({ api_key: '<ph_project_token>', test_mode: true })
 posthog.capture({ distinct_id: 'user_123', event: 'test_event' })
@@ -695,11 +647,3 @@ posthog.clear
 ## Thank you
 
 This library is largely based on the `analytics-ruby` package.
-
-### Still have questions?
-
-Ask PostHog AI
-
-### Was this page useful?
-
-HelpfulCould be better

package/dist/global-skills/instrument-product-analytics/references/svelte.md

@@ -2,18 +2,30 @@
 
 # Svelte
 
+Canonical URL: https://posthog.com/docs/libraries/svelte
+
+> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.i.posthog.com` instead of `https://us.i.posthog.com` (ingestion host), and use `https://eu.posthog.com` instead of `https://us.posthog.com` (app host for links).
+
+## On this page
+
+- [Beta: integration via LLM](#beta-integration-via-llm)
+- [Client-side setup](#client-side-setup)
+- [Identifying users](#identifying-users)
+- [Server-side setup](#server-side-setup)
+- [Feature flags](#feature-flags)
+- [Configuring session replay for server-side rendered apps](#configuring-session-replay-for-server-side-rendered-apps)
+- [Next steps](#next-steps)
+
 PostHog makes it easy to get data about traffic and usage of your [Svelte](https://svelte.dev/) app. Integrating PostHog into your site enables analytics about user behavior, custom events capture, session recordings, feature flags, and more.
 
-This guide walks you through integrating PostHog into your SvelteKit app using the [JavaScript Web](/docs/libraries/js.md) and [Node.js](/docs/libraries/node.md) SDKs.
+This guide walks you through integrating PostHog into your SvelteKit app using the [JavaScript Web](https://posthog.com/docs/libraries/js.md) and [Node.js](https://posthog.com/docs/libraries/node.md) SDKs.
 
 ## Beta: integration via LLM
 
-Install PostHog for Svelte in seconds with our wizard by running this prompt with [LLM coding agents](/blog/envoy-wizard-llm-agent.md) like Cursor and Bolt, or by running it in your terminal.
+Install PostHog for Svelte in seconds with our wizard by running this prompt with [LLM coding agents](https://posthog.com/blog/envoy-wizard-llm-agent.md) like Cursor and Bolt, or by running it in your terminal.
 
 `npx @posthog/wizard`
 
-[Learn more](/wizard.md)
-
 Or, to integrate manually, continue with the rest of this guide.
 
 ## Client-side setup
@@ -52,7 +64,7 @@ bun add posthog-js
 > worker-src 'self' blob: data:;
 > ```
 >
-> `script-src` covers the snippet and the lazy-loaded bundles, `connect-src` covers event ingestion and feature flags, and `worker-src` covers session replay. The [toolbar needs a few more](/docs/advanced/content-security-policy.md), or use a [reverse proxy](/docs/advanced/proxy.md) so everything is first-party. Failing to do so causes silent failures where `capture` and `identify` calls never send, so the integration looks complete while zero events arrive. Remember `connect-src` falls back to `default-src`, so `default-src 'self'` blocks event delivery even when the script itself is bundled.
+> `script-src` covers the snippet and the lazy-loaded bundles, `connect-src` covers event ingestion and feature flags, and `worker-src` covers session replay. The [toolbar needs a few more](https://posthog.com/docs/advanced/content-security-policy.md), or use a [reverse proxy](https://posthog.com/docs/advanced/proxy.md) so everything is first-party. Failing to do so causes silent failures where `capture` and `identify` calls never send, so the integration looks complete while zero events arrive. Remember `connect-src` falls back to `default-src`, so `default-src 'self'` blocks event delivery even when the script itself is bundled.
 
 Then, if you haven't created a root [layout](https://kit.svelte.dev/docs/routing#layout) already, create a new file called `+layout.js` in your `src/routes` folder In this file, check the environment is the browser, and initialize PostHog if so. You can get both your API key and instance address in your [project settings](https://us.posthog.com/project/settings).
 
@@ -76,18 +88,16 @@ export const load = async () => {
 
 ## Identifying users
 
-> **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.md), [LLM traces](/docs/ai-engineering.md), and [error tracking](/docs/error-tracking.md) to the same person — and lets backend events link back too.
+> **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](https://posthog.com/docs/session-replay.md), [LLM traces](https://posthog.com/docs/ai-engineering.md), and [error tracking](https://posthog.com/docs/error-tracking.md) to the same person — and lets backend events link back too.
 >
 > Use a stable ID from your auth system when possible, not an email or display name. Send those as person properties instead. If your app has no other stable key, email works as a fallback if they are unique. Never a shared literal like `"anonymous"` or `"user"`, which pools many people onto one person and corrupts their data. When no ID is available at all, skip the identify and retain the anonymous distinct ID that's automatically assigned.
 >
 > Call `posthog.reset()` on logout, so the next person to use the browser doesn't inherit the last one's identity.
 >
-> See our guide on [identifying users](/docs/getting-started/identify-users.md) for how to set this up.
+> See our guide on [identifying users](https://posthog.com/docs/getting-started/identify-users.md) for how to set this up.
 
 If your app calls your own backend, `tracing_headers` adds `X-POSTHOG-DISTINCT-ID` and `X-POSTHOG-SESSION-ID` to matching `fetch` and `XMLHttpRequest` requests. This lets server-side SDKs link backend events, errors, and LLM traces back to frontend sessions and replays. Use hostnames only, without protocols or paths.
 
-JavaScript
-
 ```javascript
 posthog.init('<ph_project_token>', {
   api_host: 'https://us.i.posthog.com',
@@ -100,25 +110,25 @@ This works in local development too, but match on the hostname alone: use `'loca
 
 Tracing headers help you attribute events across front and backend consistently. When this isn't available, use your server-side stable IDs to deduce the matching `distinctId`, and pass it in when capturing the event.
 
-> ❗️ If you intend on using session replays with a server-side rendered Svelte app ensure that your [asset URLs are configured to be relative](/docs/session-replay/troubleshooting.md#ensure-assets-are-imported-from-the-base-URL-in-Svelte).
+> ❗️ If you intend on using session replays with a server-side rendered Svelte app ensure that your [asset URLs are configured to be relative](https://posthog.com/docs/session-replay/troubleshooting.md#ensure-assets-are-imported-from-the-base-URL-in-Svelte).
 
-Set up a reverse proxy (recommended)
+**Set up a reverse proxy (recommended)**
 
-We recommend [setting up a reverse proxy](/docs/advanced/proxy.md), so that events are less likely to be intercepted by tracking blockers.
+We recommend [setting up a reverse proxy](https://posthog.com/docs/advanced/proxy.md), so that events are less likely to be intercepted by tracking blockers.
 
-We have our [own managed reverse proxy service](/docs/advanced/proxy/managed-reverse-proxy.md), which is free for all PostHog Cloud users, routes through our infrastructure, and makes setting up your proxy easy.
+We have our [own managed reverse proxy service](https://posthog.com/docs/advanced/proxy/managed-reverse-proxy.md), which is free for all PostHog Cloud users, routes through our infrastructure, and makes setting up your proxy easy.
 
-If you don't want to use our managed service then there are several other options for creating a reverse proxy, including using [Cloudflare](/docs/advanced/proxy/cloudflare.md), [AWS Cloudfront](/docs/advanced/proxy/cloudfront.md), and [Vercel](/docs/advanced/proxy/vercel.md).
+If you don't want to use our managed service then there are several other options for creating a reverse proxy, including using [Cloudflare](https://posthog.com/docs/advanced/proxy/cloudflare.md), [AWS Cloudfront](https://posthog.com/docs/advanced/proxy/cloudfront.md), and [Vercel](https://posthog.com/docs/advanced/proxy/vercel.md).
 
-Grouping products in one project (recommended)
+**Grouping products in one project (recommended)**
 
-If you have multiple customer-facing products (e.g. a marketing website + mobile app + web app), it's best to install PostHog on them all and [group them in one project](/docs/settings/projects.md).
+If you have multiple customer-facing products (e.g. a marketing website + mobile app + web app), it's best to install PostHog on them all and [group them in one project](https://posthog.com/docs/settings/projects.md).
 
 This makes it possible to track users across their entire journey (e.g. from visiting your marketing website to signing up for your product), or how they use your product across multiple platforms.
 
-Add IPs to Firewall/WAF allowlists (recommended)
+**Add IPs to Firewall/WAF allowlists (recommended)**
 
-For certain features like [heatmaps](/docs/toolbar/heatmaps.md), your Web Application Firewall (WAF) may be blocking PostHog's requests to your site. Add these IP addresses to your WAF allowlist or rules to let PostHog access your site.
+For certain features like [heatmaps](https://posthog.com/docs/toolbar/heatmaps.md), your Web Application Firewall (WAF) may be blocking PostHog's requests to your site. Add these IP addresses to your WAF allowlist or rules to let PostHog access your site.
 
 **EU**: `3.75.65.221`, `18.197.246.42`, `3.120.223.253`
 
@@ -128,7 +138,7 @@ These are public, stable IPs used by PostHog services.
 
 PostHog captures heatmap screenshots using [Browserless](https://www.browserless.io), which has its own IP addresses. Browserless [publishes the current list here](https://docs.browserless.io/baas/troubleshooting/whitelisting-ips).
 
-An allowlist does not help when your app has a private address. For apps on an internal network, see [internal and intranet applications](/docs/session-replay/troubleshooting.md#internal-and-intranet-applications).
+An allowlist does not help when your app has a private address. For apps on an internal network, see [internal and intranet applications](https://posthog.com/docs/session-replay/troubleshooting.md#internal-and-intranet-applications).
 
 ## Server-side setup
 
@@ -231,7 +241,7 @@ export async function load() {
 }
 ```
 
-See our [JavaScript Web](/docs/libraries/js/usage.md#feature-flags) and [Node](/docs/libraries/node.md#feature-flags) docs for more details.
+See our [JavaScript Web](https://posthog.com/docs/libraries/js/usage.md#feature-flags) and [Node](https://posthog.com/docs/libraries/node.md#feature-flags) docs for more details.
 
 ## Configuring session replay for server-side rendered apps
 
@@ -239,8 +249,6 @@ By default, [Svelte uses relative asset paths](https://kit.svelte.dev/docs/confi
 
 To fix this, set the config to not use relative paths in `svelte.config.js`:
 
-JavaScript
-
 ```javascript
 kit: {
      paths: {
@@ -251,18 +259,10 @@ kit: {
 
 ## Next steps
 
-For any technical questions for how to integrate specific PostHog features into Svelte (such as analytics, feature flags, A/B testing, surveys, etc.), have a look at our [JavaScript Web](/docs/libraries/js/usage.md) and [Node](/docs/libraries/node.md) SDK docs.
+For any technical questions for how to integrate specific PostHog features into Svelte (such as analytics, feature flags, A/B testing, surveys, etc.), have a look at our [JavaScript Web](https://posthog.com/docs/libraries/js/usage.md) and [Node](https://posthog.com/docs/libraries/node.md) SDK docs.
 
 Alternatively, the following tutorials can help you get started:
 
--   [How to set up Svelte analytics, feature flags, and more](/tutorials/svelte-analytics.md)
--   [How to set up A/B tests in Svelte](/tutorials/svelte-ab-tests.md)
--   [How to set up surveys in Svelte](/tutorials/svelte-surveys.md)
-
-### Still have questions?
-
-Ask PostHog AI
-
-### Was this page useful?
-
-HelpfulCould be better
+-   [How to set up Svelte analytics, feature flags, and more](https://posthog.com/tutorials/svelte-analytics.md)
+-   [How to set up A/B tests in Svelte](https://posthog.com/tutorials/svelte-ab-tests.md)
+-   [How to set up surveys in Svelte](https://posthog.com/tutorials/svelte-surveys.md)

package/dist/global-skills/instrument-product-analytics/references/tanstack-start.md

@@ -2,35 +2,45 @@
 
 # TanStack Start
 
+Canonical URL: https://posthog.com/docs/libraries/tanstack-start
+
+> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.i.posthog.com` instead of `https://us.i.posthog.com` (ingestion host).
+
+## On this page
+
+- [Installation](#installation)
+- [Identifying users](#identifying-users)
+- [Initialize PostHog on the client](#initialize-posthog-on-the-client)
+- [Capture events on the client](#capture-events-on-the-client)
+- [Initialize PostHog on the server](#initialize-posthog-on-the-server)
+- [Capture events on the server](#capture-events-on-the-server)
+- [Next steps](#next-steps)
+
 This tutorial shows how to integrate PostHog with a [TanStack Start](https://tanstack.com/start) app for both client-side and server-side analytics.
 
 ## Installation
 
 Install the required packages:
 
-Terminal
-
 ```bash
 npm install @posthog/react posthog-node
 ```
 
--   `@posthog/react` - React package for our [JS Web SDK](/docs/libraries/js.md) for client-side usage
--   `posthog-node` - PostHog [Node.js SDK](/docs/libraries/node.md) for server-side event capture
+-   `@posthog/react` - React package for our [JS Web SDK](https://posthog.com/docs/libraries/js.md) for client-side usage
+-   `posthog-node` - PostHog [Node.js SDK](https://posthog.com/docs/libraries/node.md) for server-side event capture
 
 ## Identifying users
 
-> **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.md), [LLM traces](/docs/ai-engineering.md), and [error tracking](/docs/error-tracking.md) to the same person — and lets backend events link back too.
+> **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](https://posthog.com/docs/session-replay.md), [LLM traces](https://posthog.com/docs/ai-engineering.md), and [error tracking](https://posthog.com/docs/error-tracking.md) to the same person — and lets backend events link back too.
 >
 > Use a stable ID from your auth system when possible, not an email or display name. Send those as person properties instead. If your app has no other stable key, email works as a fallback if they are unique. Never a shared literal like `"anonymous"` or `"user"`, which pools many people onto one person and corrupts their data. When no ID is available at all, skip the identify and retain the anonymous distinct ID that's automatically assigned.
 >
 > Call `posthog.reset()` on logout, so the next person to use the browser doesn't inherit the last one's identity.
 >
-> See our guide on [identifying users](/docs/getting-started/identify-users.md) for how to set this up.
+> See our guide on [identifying users](https://posthog.com/docs/getting-started/identify-users.md) for how to set this up.
 
 If your app calls your own backend, `tracing_headers` adds `X-POSTHOG-DISTINCT-ID` and `X-POSTHOG-SESSION-ID` to matching `fetch` and `XMLHttpRequest` requests. This lets server-side SDKs link backend events, errors, and LLM traces back to frontend sessions and replays. Use hostnames only, without protocols or paths.
 
-JavaScript
-
 ```javascript
 posthog.init('<ph_project_token>', {
   api_host: 'https://us.i.posthog.com',
@@ -118,8 +128,6 @@ function CheckoutButton({ orderId, total }: { orderId: string; total: number })
 
 Call `posthog.identify()` when a user logs in to link their events to a user ID:
 
-TSX
-
 ```jsx
 import { usePostHog } from '@posthog/react'
 
@@ -208,12 +216,4 @@ The server-side `capture` call requires a `distinctId` (the user identifier), an
 
 ## Next steps
 
-Installing the JS Web SDK and Node SDK means all of their functionality is available in your TanStack Start project. To learn more about this, have a look at our [JS Web SDK docs](/docs/libraries/js/usage.md) and [Node SDK docs](/docs/libraries/node.md).
-
-### Still have questions?
-
-Ask PostHog AI
-
-### Was this page useful?
-
-HelpfulCould be better
+Installing the JS Web SDK and Node SDK means all of their functionality is available in your TanStack Start project. To learn more about this, have a look at our [JS Web SDK docs](https://posthog.com/docs/libraries/js/usage.md) and [Node SDK docs](https://posthog.com/docs/libraries/node.md).