vybekiit 0.7.33 → 0.7.35

package/dist/global-skills/instrument-feature-flags/references/react-native.md

@@ -2,6 +2,19 @@
 
 # React Native Feature Flags installation
 
+Canonical URL: https://posthog.com/docs/feature-flags/installation/react-native
+
+> **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
+
+- [Install the package](#install-the-package)
+- [Configure PostHog](#configure-posthog)
+- [Send events](#send-events)
+- [Use feature flags](#use-feature-flags)
+- [Running experiments](#running-experiments)
+- [Next steps](#next-steps)
+
 1.  1
 
     ## Install the package
@@ -155,16 +168,8 @@
 
     | Resource | Description |
     | --- | --- |
-    | [Creating a feature flag](/docs/feature-flags/creating-feature-flags.md) | How to create a feature flag in PostHog |
-    | [Adding feature flag code](/docs/feature-flags/adding-feature-flag-code.md) | How to check flags in your code for all platforms |
-    | [Framework-specific guides](/docs/feature-flags/tutorials.md#framework-guides) | Setup guides for React Native, Next.js, Flutter, and other frameworks |
-    | [How to do a phased rollout](/tutorials/phased-rollout.md) | Gradually roll out features to minimize risk |
-    | [More tutorials](/docs/feature-flags/tutorials.md) | Other real-world examples and use cases |
-
-### Still have questions?
-
-Ask PostHog AI
-
-### Was this page useful?
-
-HelpfulCould be better
+    | [Creating a feature flag](https://posthog.com/docs/feature-flags/creating-feature-flags.md) | How to create a feature flag in PostHog |
+    | [Adding feature flag code](https://posthog.com/docs/feature-flags/adding-feature-flag-code.md) | How to check flags in your code for all platforms |
+    | [Framework-specific guides](https://posthog.com/docs/feature-flags/tutorials.md#framework-guides) | Setup guides for React Native, Next.js, Flutter, and other frameworks |
+    | [How to do a phased rollout](https://posthog.com/tutorials/phased-rollout.md) | Gradually roll out features to minimize risk |
+    | [More tutorials](https://posthog.com/docs/feature-flags/tutorials.md) | Other real-world examples and use cases |

package/dist/global-skills/instrument-feature-flags/references/react.md

@@ -2,6 +2,21 @@
 
 # React Feature Flags installation
 
+Canonical URL: https://posthog.com/docs/feature-flags/installation/react
+
+> **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
+
+- [Install the package](#install-the-package)
+- [Add environment variables](#add-environment-variables)
+- [Initialize PostHog](#initialize-posthog)
+- [Accessing PostHog in your code](#accessing-posthog-in-your-code)
+- [Send events](#send-events)
+- [Use feature flags](#use-feature-flags)
+- [Running experiments](#running-experiments)
+- [Next steps](#next-steps)
+
 1.  1
 
     ## Install the package
@@ -82,7 +97,7 @@
 
     **defaults option**
 
-    The `defaults` option automatically configures PostHog with recommended settings for new projects. See [SDK defaults](/docs/libraries/js.md#sdk-defaults) for details.
+    The `defaults` option automatically configures PostHog with recommended settings for new projects. See [SDK defaults](https://posthog.com/docs/libraries/js.md#sdk-defaults) for details.
 
 4.  4
 
@@ -289,16 +304,8 @@
 
     | Resource | Description |
     | --- | --- |
-    | [Creating a feature flag](/docs/feature-flags/creating-feature-flags.md) | How to create a feature flag in PostHog |
-    | [Adding feature flag code](/docs/feature-flags/adding-feature-flag-code.md) | How to check flags in your code for all platforms |
-    | [Framework-specific guides](/docs/feature-flags/tutorials.md#framework-guides) | Setup guides for React Native, Next.js, Flutter, and other frameworks |
-    | [How to do a phased rollout](/tutorials/phased-rollout.md) | Gradually roll out features to minimize risk |
-    | [More tutorials](/docs/feature-flags/tutorials.md) | Other real-world examples and use cases |
-
-### Still have questions?
-
-Ask PostHog AI
-
-### Was this page useful?
-
-HelpfulCould be better
+    | [Creating a feature flag](https://posthog.com/docs/feature-flags/creating-feature-flags.md) | How to create a feature flag in PostHog |
+    | [Adding feature flag code](https://posthog.com/docs/feature-flags/adding-feature-flag-code.md) | How to check flags in your code for all platforms |
+    | [Framework-specific guides](https://posthog.com/docs/feature-flags/tutorials.md#framework-guides) | Setup guides for React Native, Next.js, Flutter, and other frameworks |
+    | [How to do a phased rollout](https://posthog.com/tutorials/phased-rollout.md) | Gradually roll out features to minimize risk |
+    | [More tutorials](https://posthog.com/docs/feature-flags/tutorials.md) | Other real-world examples and use cases |

package/dist/global-skills/instrument-feature-flags/references/ruby-on-rails.md

@@ -2,18 +2,37 @@
 
 # Ruby on Rails
 
+Canonical URL: https://posthog.com/docs/libraries/ruby-on-rails
+
+> **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)
+- [Features](#features)
+- [Installation](#installation)
+- [Identifying users](#identifying-users)
+- [Configuration](#configuration)
+- [Capturing events](#capturing-events)
+- [Request context](#request-context)
+- [Logs](#logs)
+- [Error tracking](#error-tracking)
+- [Feature flags](#feature-flags)
+- [Testing](#testing)
+- [Configuration reference](#configuration-reference)
+- [Troubleshooting](#troubleshooting)
+- [Next steps](#next-steps)
+
 PostHog makes it easy to get data about traffic and usage of your Ruby on Rails app. Integrating PostHog enables analytics, custom event capture, feature flags, and automatic exception tracking.
 
 This guide walks you through integrating PostHog into your Rails app using the [posthog-rails gem](https://github.com/PostHog/posthog-ruby/tree/main/posthog-rails).
 
 ## Beta: integration via LLM
 
-Install PostHog for Rails 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 Rails 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.
 
 ## Features
@@ -24,7 +43,7 @@ Or, to integrate manually, continue with the rest of this guide.
 -   **Smart filtering** – Excludes common Rails exceptions (404s, etc.) by default
 -   **Request context** – Adds request metadata and optional PostHog tracing header identity/session context to captured events
 -   **Rails 7.0+ error reporter** – Integrates with Rails' built-in error reporting
--   **Log forwarding** – Optionally forwards `Rails.logger` output to [PostHog Logs](/docs/logs.md) over OpenTelemetry, automatically correlated with request context (Ruby 3.3+)
+-   **Log forwarding** – Optionally forwards `Rails.logger` output to [PostHog Logs](https://posthog.com/docs/logs.md) over OpenTelemetry, automatically correlated with request context (Ruby 3.3+)
 
 ## Installation
 
@@ -39,24 +58,20 @@ gem 'posthog-rails'
 
 Then run:
 
-Terminal
-
 ```bash
 bundle install
 ```
 
 ## 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.
 
 ### Generate the initializer
 
 Run the install generator to create the PostHog initializer:
 
-Terminal
-
 ```bash
 rails generate posthog:install
 ```
@@ -130,8 +145,6 @@ You can find your project token and instance address in [your project settings](
 
 > **Tip:** Use [`Rails.application.credentials`](https://guides.rubyonrails.org/security.html#custom-credentials) to avoid hardcoding API keys. First, add your keys and then reference them in your initializer:
 >
-> Terminal
->
 > ```bash
 > rails credentials:edit
 > ```
@@ -157,8 +170,6 @@ You can find your project token and instance address in [your project settings](
 
 Track custom events anywhere in your Rails app:
 
-Ruby
-
 ```ruby
 PostHog.capture({
   distinct_id: current_user.id,
@@ -169,8 +180,6 @@ PostHog.capture({
 
 Identify a user and set their person properties:
 
-Ruby
-
 ```ruby
 PostHog.identify({
   distinct_id: current_user.id,
@@ -189,32 +198,28 @@ PostHog Rails automatically applies request-scoped context to events captured du
 
 When `use_tracing_headers` is enabled, PostHog tracing headers (`X-PostHog-Distinct-Id` and `X-PostHog-Session-Id`) are also used as default `distinct_id` and `$session_id` values. Explicit `distinct_id` and properties passed to `PostHog.capture` always take precedence.
 
-If you're using [PostHog JS](/docs/libraries/js.md) on the frontend, configure [`tracing_headers`](/docs/libraries/js/config.md#tracing-headers) for your Rails backend hostname so browser requests include the session and distinct ID headers.
+If you're using [PostHog JS](https://posthog.com/docs/libraries/js.md) on the frontend, configure [`tracing_headers`](https://posthog.com/docs/libraries/js/config.md#tracing-headers) for your Rails backend hostname so browser requests include the session and distinct ID headers.
 
 Tracing headers are client-controlled analytics context, not authentication or authorization. Pass an authenticated `distinct_id` explicitly for security-sensitive server-side decisions.
 
 Disable tracing header identity/session capture if you do not want client-supplied tracing headers used for server-side events. Request metadata is still captured:
 
-Ruby
-
 ```ruby
 PostHog::Rails.config.use_tracing_headers = false
 ```
 
 ## Logs
 
-To set up [PostHog Logs](/docs/logs.md) in your Rails app, follow the [Ruby on Rails logs installation guide](/docs/logs/installation/ruby-on-rails.md). The integration forwards `Rails.logger` output to PostHog Logs over OpenTelemetry, automatically correlated with each request's distinct ID and session ID. Requires Ruby 3.3+.
+To set up [PostHog Logs](https://posthog.com/docs/logs.md) in your Rails app, follow the [Ruby on Rails logs installation guide](https://posthog.com/docs/logs/installation/ruby-on-rails.md). The integration forwards `Rails.logger` output to PostHog Logs over OpenTelemetry, automatically correlated with each request's distinct ID and session ID. Requires Ruby 3.3+.
 
 ## Error tracking
 
-For full details on setting up error tracking with Rails, see our [Rails error tracking installation guide](/docs/error-tracking/installation/ruby-on-rails.md).
+For full details on setting up error tracking with Rails, see our [Rails error tracking installation guide](https://posthog.com/docs/error-tracking/installation/ruby-on-rails.md).
 
 ### Automatic exception tracking
 
 When `auto_capture_exceptions` is enabled, exceptions are automatically captured:
 
-Ruby
-
 ```ruby
 class PostsController < ApplicationController
   def show
@@ -230,8 +235,6 @@ end
 
 You can also manually capture exceptions:
 
-Ruby
-
 ```ruby
 PostHog.capture_exception(
   exception,
@@ -242,8 +245,6 @@ PostHog.capture_exception(
 
 If you evaluated feature flags for the request, pass the same snapshot to include matching flag properties on the exception event:
 
-Ruby
-
 ```ruby
 flags = PostHog.evaluate_flags(current_user.id)
 
@@ -259,8 +260,6 @@ PostHog.capture_exception(
 
 When `auto_instrument_active_job` is enabled, ActiveJob exceptions are automatically captured with job context:
 
-Ruby
-
 ```ruby
 class EmailJob < ApplicationJob
   def perform(user_id)
@@ -275,8 +274,6 @@ end
 
 By default, PostHog extracts a `distinct_id` from job arguments by looking for a `user_id` key in hash arguments:
 
-Ruby
-
 ```ruby
 # PostHog will automatically use options[:user_id] as the distinct_id
 ProcessOrderJob.perform_later(order.id, user_id: current_user.id)
@@ -284,8 +281,6 @@ ProcessOrderJob.perform_later(order.id, user_id: current_user.id)
 
 For more control, use the `posthog_distinct_id` class method. The proc or block receives the same arguments as `perform`:
 
-Ruby
-
 ```ruby
 class SendWelcomeEmailJob < ApplicationJob
   posthog_distinct_id ->(user, _options) { user.id }
@@ -298,8 +293,6 @@ end
 
 You can also use a block:
 
-Ruby
-
 ```ruby
 class ProcessOrderJob < ApplicationJob
   posthog_distinct_id do |_order, notify_user_id|
@@ -316,8 +309,6 @@ end
 
 PostHog integrates with Rails' built-in error reporting:
 
-Ruby
-
 ```ruby
 # These errors are automatically sent to PostHog
 Rails.error.handle do
@@ -335,8 +326,6 @@ PostHog Rails automatically captures authenticated user information from your co
 
 If your user method has a different name, configure it:
 
-Ruby
-
 ```ruby
 PostHog::Rails.config.current_user_method = :logged_in_user
 ```
@@ -355,16 +344,12 @@ It also checks hash-like users for `id`, `pk`, and `uuid` keys.
 
 You can configure a specific method:
 
-Ruby
-
 ```ruby
 PostHog::Rails.config.user_id_method = :email
 ```
 
 Or define a method on your User model:
 
-Ruby
-
 ```ruby
 class User < ApplicationRecord
   def posthog_distinct_id
@@ -393,8 +378,6 @@ The following exceptions are not reported by default (common 4xx errors):
 
 Add more with:
 
-Ruby
-
 ```ruby
 PostHog::Rails.config.excluded_exceptions = ['MyException']
 ```
@@ -403,8 +386,6 @@ PostHog::Rails.config.excluded_exceptions = ['MyException']
 
 Evaluate flags once for the current user, then read values from the returned snapshot:
 
-Ruby
-
 ```ruby
 class PostsController < ApplicationController
   def show
@@ -421,8 +402,6 @@ end
 
 For multivariate flags and experiments, use `get_flag`:
 
-Ruby
-
 ```ruby
 flags = PostHog.evaluate_flags(current_user.id)
 variant = flags.get_flag('checkout-experiment')
@@ -434,8 +413,6 @@ end
 
 When capturing an event after branching on a flag, pass the same `flags` snapshot so the event includes the exact flag values used by your code:
 
-Ruby
-
 ```ruby
 flags = PostHog.evaluate_flags(current_user.id)
 
@@ -448,13 +425,11 @@ PostHog.capture({
 
 For local evaluation, ensure you've set `personal_api_key`:
 
-Ruby
-
 ```ruby
 config.personal_api_key = Rails.application.credentials.posthog[:personal_api_key]
 ```
 
-See our [Ruby SDK docs](/docs/libraries/ruby.md#local-evaluation) for details on local evaluation with Puma and Unicorn servers.
+See our [Ruby SDK docs](https://posthog.com/docs/libraries/ruby.md#local-evaluation) for details on local evaluation with Puma and Unicorn servers.
 
 > **Note:** `PostHog.is_feature_enabled`, `PostHog.get_feature_flag`, `PostHog.get_feature_flag_result`, `PostHog.get_feature_flag_payload`, and `PostHog.capture({ ..., send_feature_flags: true })` still work during the migration period, but they're deprecated. Prefer `PostHog.evaluate_flags` for new code.
 
@@ -500,7 +475,7 @@ end
 | `feature_flag_request_timeout_seconds` | Integer | `3` | Timeout, in seconds, for feature flag requests. |
 | `before_send` | Proc | `nil` | Callback that receives the event hash before it is queued or sent. Return a modified event hash, or `nil` to drop the event. |
 
-The `PostHog.init` block supports the options above. Less common core options like `batch_size`, `disable_singleton_warning`, `skip_ssl_verification`, and `flag_definition_cache_provider` can be passed as an options hash to `PostHog.init(...)`; see the [Ruby SDK docs](/docs/libraries/ruby.md#configuration) for details.
+The `PostHog.init` block supports the options above. Less common core options like `batch_size`, `disable_singleton_warning`, `skip_ssl_verification`, and `flag_definition_cache_provider` can be passed as an options hash to `PostHog.init(...)`; see the [Ruby SDK docs](https://posthog.com/docs/libraries/ruby.md#configuration) for details.
 
 ### Rails-specific options
 
@@ -523,8 +498,6 @@ Configure these via `PostHog::Rails.configure` or `PostHog::Rails.config`:
 
 1.  Verify PostHog is initialized:
 
-    Ruby
-
     ```ruby
     Rails.console
     > PostHog.initialized?
@@ -535,8 +508,6 @@ Configure these via `PostHog::Rails.configure` or `PostHog::Rails.config`:
 
 3.  Verify middleware is installed:
 
-    Ruby
-
     ```ruby
     Rails.application.middleware
     ```
@@ -553,12 +524,4 @@ Ensure you've set `personal_api_key` in your configuration.
 
 ## Next steps
 
-For any technical questions for how to integrate specific PostHog features into Rails (such as analytics, feature flags, A/B testing, etc.), have a look at our [Ruby SDK docs](/docs/libraries/ruby.md).
-
-### Still have questions?
-
-Ask PostHog AI
-
-### Was this page useful?
-
-HelpfulCould be better
+For any technical questions for how to integrate specific PostHog features into Rails (such as analytics, feature flags, A/B testing, etc.), have a look at our [Ruby SDK docs](https://posthog.com/docs/libraries/ruby.md).

package/dist/global-skills/instrument-feature-flags/references/ruby.md

@@ -2,6 +2,22 @@
 
 # Ruby Feature Flags installation
 
+Canonical URL: https://posthog.com/docs/feature-flags/installation/ruby
+
+> **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
+
+- [Install the gem](#install-the-gem)
+- [Configure PostHog](#configure-posthog)
+- [Send events](#send-events)
+- [Evaluate boolean feature flags](#evaluate-boolean-feature-flags)
+- [Evaluate multivariate feature flags](#evaluate-multivariate-feature-flags)
+- [Include feature flag information in events](#include-feature-flag-information-in-events)
+- [Override server properties](#override-server-properties)
+- [Running experiments](#running-experiments)
+- [Next steps](#next-steps)
+
 1.  1
 
     ## Install the gem
@@ -178,16 +194,8 @@
 
     | Resource | Description |
     | --- | --- |
-    | [Creating a feature flag](/docs/feature-flags/creating-feature-flags.md) | How to create a feature flag in PostHog |
-    | [Adding feature flag code](/docs/feature-flags/adding-feature-flag-code.md) | How to check flags in your code for all platforms |
-    | [Framework-specific guides](/docs/feature-flags/tutorials.md#framework-guides) | Setup guides for React Native, Next.js, Flutter, and other frameworks |
-    | [How to do a phased rollout](/tutorials/phased-rollout.md) | Gradually roll out features to minimize risk |
-    | [More tutorials](/docs/feature-flags/tutorials.md) | Other real-world examples and use cases |
-
-### Still have questions?
-
-Ask PostHog AI
-
-### Was this page useful?
-
-HelpfulCould be better
+    | [Creating a feature flag](https://posthog.com/docs/feature-flags/creating-feature-flags.md) | How to create a feature flag in PostHog |
+    | [Adding feature flag code](https://posthog.com/docs/feature-flags/adding-feature-flag-code.md) | How to check flags in your code for all platforms |
+    | [Framework-specific guides](https://posthog.com/docs/feature-flags/tutorials.md#framework-guides) | Setup guides for React Native, Next.js, Flutter, and other frameworks |
+    | [How to do a phased rollout](https://posthog.com/tutorials/phased-rollout.md) | Gradually roll out features to minimize risk |
+    | [More tutorials](https://posthog.com/docs/feature-flags/tutorials.md) | Other real-world examples and use cases |

package/dist/global-skills/instrument-feature-flags/references/rust.md

@@ -2,6 +2,8 @@
 
 # Rust Feature Flags installation
 
+Canonical URL: https://posthog.com/docs/feature-flags/installation/rust
+
 Install the `posthog-rs` crate by adding it to your `Cargo.toml`.
 
 Cargo.toml
@@ -13,8 +15,6 @@ posthog-rs = "0.14"
 
 Next, set up the client with your PostHog project key.
 
-Rust
-
 ```rust
 let client = posthog_rs::client("<ph_project_token>").await;
 ```
@@ -25,8 +25,6 @@ Our Rust SDK supports both blocking and async clients. The async client is the d
 
 If you need to use a synchronous client instead – like we do in our [CLI](https://github.com/PostHog/posthog/tree/master/cli) –, you can opt into it by disabling the asynchronous feature on your `Cargo.toml` file.
 
-toml
-
 ```toml
 [dependencies]
 posthog-rs = { version = "0.14", default-features = false }
@@ -44,8 +42,6 @@ Call `client.evaluate_flags()` once for the user, then read values from the retu
 
 #### Boolean feature flags
 
-Rust
-
 ```rust
 use posthog_rs::EvaluateFlagsOptions;
 
@@ -63,8 +59,6 @@ if flags.is_enabled("flag-key") {
 
 #### Multivariate feature flags
 
-Rust
-
 ```rust
 use posthog_rs::{EvaluateFlagsOptions, FlagValue};
 
@@ -89,9 +83,9 @@ match flags.get_flag("flag-key") {
 
 ### 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:
 
@@ -99,8 +93,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.
 
-Rust
-
 ```rust
 use posthog_rs::{EvaluateFlagsOptions, Event};
 
@@ -122,8 +114,6 @@ By default, this attaches every flag in the snapshot using `$feature/<flag-key>`
 
 To reduce event property bloat, pass a filtered snapshot:
 
-Rust
-
 ```rust
 // Attach only flags accessed with is_enabled() or get_flag() before this call
 let mut event = Event::new("event_name", "distinct_id_of_your_user");
@@ -142,8 +132,6 @@ client.capture(event);
 
 In the event properties, include `$feature/feature_flag_name: variant_key`:
 
-Rust
-
 ```rust
 use posthog_rs::Event;
 
@@ -156,8 +144,6 @@ client.capture(event);
 
 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:
 
-Rust
-
 ```rust
 use posthog_rs::EvaluateFlagsOptions;
 
@@ -172,7 +158,7 @@ let flags = client.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.is_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.is_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.
 
@@ -182,8 +168,6 @@ The SDK deduplicates these events per `(distinct_id, flag, value)` in a local ca
 
 If you're using the blocking client (with `default-features = false`), the API is the same but without `.await`:
 
-Rust
-
 ```rust
 use posthog_rs::EvaluateFlagsOptions;
 
@@ -201,16 +185,8 @@ Now that you're evaluating flags, continue with the resources below to learn wha
 
 | Resource | Description |
 | --- | --- |
-| [Creating a feature flag](/docs/feature-flags/creating-feature-flags.md) | How to create a feature flag in PostHog |
-| [Adding feature flag code](/docs/feature-flags/adding-feature-flag-code.md) | How to check flags in your code for all platforms |
-| [Framework-specific guides](/docs/feature-flags/tutorials.md#framework-guides) | Setup guides for React Native, Next.js, Flutter, and other frameworks |
-| [How to do a phased rollout](/tutorials/phased-rollout.md) | Gradually roll out features to minimize risk |
-| [More tutorials](/docs/feature-flags/tutorials.md) | Other real-world examples and use cases |
-
-### Still have questions?
-
-Ask PostHog AI
-
-### Was this page useful?
-
-HelpfulCould be better
+| [Creating a feature flag](https://posthog.com/docs/feature-flags/creating-feature-flags.md) | How to create a feature flag in PostHog |
+| [Adding feature flag code](https://posthog.com/docs/feature-flags/adding-feature-flag-code.md) | How to check flags in your code for all platforms |
+| [Framework-specific guides](https://posthog.com/docs/feature-flags/tutorials.md#framework-guides) | Setup guides for React Native, Next.js, Flutter, and other frameworks |
+| [How to do a phased rollout](https://posthog.com/tutorials/phased-rollout.md) | Gradually roll out features to minimize risk |
+| [More tutorials](https://posthog.com/docs/feature-flags/tutorials.md) | Other real-world examples and use cases |