vybekiit 0.7.34 → 0.7.35

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

@@ -2,6 +2,33 @@
 
 # Flutter
 
+Canonical URL: https://posthog.com/docs/libraries/flutter
+
+> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` (app host for links).
+
+## On this page
+
+- [Installation](#installation)
+- [Capturing events](#capturing-events)
+- [Identifying users](#identifying-users)
+- [Get the current user's distinct ID](#get-the-current-users-distinct-id)
+- [Alias](#alias)
+- [Anonymous vs identified events](#anonymous-vs-identified-events)
+- [Super properties](#super-properties)
+- [Group analytics](#group-analytics)
+- [Feature flags](#feature-flags)
+- [Experiments (A/B tests)](#experiments-ab-tests)
+- [Error tracking](#error-tracking)
+- [Logs](#logs)
+- [Session replay](#session-replay)
+- [Surveys](#surveys)
+- [Push notifications](#push-notifications)
+- [Flush](#flush)
+- [Offline behavior](#offline-behavior)
+- [Opt out of data capture](#opt-out-of-data-capture)
+- [Amending or dropping events](#amending-or-dropping-events)
+- [Debug mode](#debug-mode)
+
 This is an optional library you can install if you're working with Flutter. 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 mobile app.
 
 PostHog supports the iOS, macOS, Android, and Web platforms.
@@ -147,8 +174,6 @@ platform :ios, '13.0'
 
 For Swift Package Manager projects without a `Podfile`, set the **Minimum Deployments** version to iOS 13.0 for the `Runner` target in Xcode (**Runner > General > Minimum Deployments**). After you change **Minimum Deployments**, regenerate the iOS project's configuration files:
 
-Terminal
-
 ```bash
 flutter build ios --config-only
 ```
@@ -159,8 +184,6 @@ If you followed the automatic SDK setup, then there's no more configuration need
 
 If you followed the manual SDK setup:
 
-Dart
-
 ```dart
 import 'package:flutter/material.dart';
 
@@ -258,12 +281,47 @@ web/index.html
 
 For more information please check: /docs/libraries/js
 
+### Reproducible Android builds and Shorebird
+
+The Flutter SDK uses the native PostHog Android SDK, which depends on the PostHog core library. The Flutter package permits a range of Android SDK versions, so Gradle can select a newer native version even when your `posthog_flutter` version hasn't changed. Your `pubspec.lock` doesn't lock these Gradle dependencies.
+
+This matters for [Shorebird](https://docs.shorebird.dev/code-push/troubleshooting/) patches, which can't update native Android code. To keep PostHog's native dependencies consistent between a release and its patches, pin both native libraries before creating the release:
+
+1.  Inspect the versions selected for your release build. From your app's `android` directory, run:
+
+    ```bash
+    ./gradlew :app:dependencyInsight --dependency com.posthog --configuration releaseRuntimeClasspath
+    ```
+
+    If you use product flavors, replace `releaseRuntimeClasspath` with your release variant's configuration, such as `productionReleaseRuntimeClasspath`. Record the selected versions of `com.posthog:posthog-android` and `com.posthog:posthog`; their version numbers differ.
+
+2.  Add strict constraints to your app's `android/app/build.gradle.kts`. Replace the placeholders with the versions selected together in the previous step:
+
+    ```kotlin
+    dependencies {
+        constraints {
+            implementation("com.posthog:posthog-android") {
+                version { strictly("<android-sdk-version>") }
+            }
+            implementation("com.posthog:posthog") {
+                version { strictly("<core-version>") }
+            }
+        }
+    }
+    ```
+
+    For a Groovy `build.gradle`, use the same dependency declarations with `version { strictly "<version>" }` inside each constraint. A plain version declaration can still be upgraded during Gradle conflict resolution; [strict constraints](https://docs.gradle.org/current/userguide/dependency_versions.html#sec:rich-version-constraints) enforce the selected versions.
+
+3.  Run the dependency report again, build your app, and verify that events arrive in PostHog. Commit the constraints and `pubspec.lock`, and use the same versions for the release and its patches.
+
+For an existing Shorebird release, use the native versions recorded for that release, not versions resolved by a fresh build today. Pinning PostHog alone doesn't freeze other plugins or your build tools. For broader dependency control, see [Gradle dependency locking](https://docs.gradle.org/current/userguide/dependency_locking.html).
+
+Pins also prevent automatic native bug fixes. When upgrading PostHog, review the pins, select compatible native versions together, and test event capture before shipping a new app-store release. Don't upgrade native dependencies in a Dart-only patch or force an old version below the Flutter package's required minimum.
+
 ## Capturing events
 
 You can send custom events using `capture`:
 
-Dart
-
 ```dart
 await Posthog().capture(
   eventName: 'user_signed_up',
@@ -274,9 +332,7 @@ await 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:
-
-Dart
+Optionally, you can include additional information with the event by including a [properties](https://posthog.com/docs/data/events.md#event-properties) object:
 
 ```dart
 await Posthog().capture(
@@ -311,8 +367,6 @@ This works with any routing package, not just the plain `Navigator` API. Add the
 
 Add the `PosthogObserver` to record screen views automatically:
 
-Dart
-
 ```dart
 import 'package:flutter/material.dart';
 import 'package:posthog_flutter/posthog_flutter.dart';
@@ -336,8 +390,6 @@ class MyApp extends StatelessWidget {
 
 Name your routes:
 
-Dart
-
 ```dart
 ...
 MaterialPageRoute(builder: (context) => const HomeScreenRoute(),
@@ -350,8 +402,6 @@ MaterialPageRoute(builder: (context) => const HomeScreenRoute(),
 
 Add the `PosthogObserver` to record screen views automatically:
 
-Dart
-
 ```dart
 import 'package:flutter/material.dart';
 import 'package:posthog_flutter/posthog_flutter.dart';
@@ -379,8 +429,6 @@ class MyApp extends StatelessWidget {
 
 Name your routes:
 
-Dart
-
 ```dart
 ...
 GoRoute(
@@ -392,17 +440,15 @@ GoRoute(
 
 ## Identifying users
 
-> We highly recommend reading our section on [Identifying users](/docs/integrate/identifying-users.md) to better understand how to correctly use this method.
+> We highly recommend reading our section on [Identifying users](https://posthog.com/docs/integrate/identifying-users.md) to better understand how to correctly use this method.
 
 Using `identify`, you can associate events with specific users. This enables you to gain full insights as to how they're using your product across different sessions, devices, and platforms.
 
 An `identify` call has the following arguments:
 
 -   **userId:** Required. A unique identifier for your user. Typically either their email or database ID.
--   **userProperties:** Optional. A dictionary with key:value pairs to set the [person properties](/docs/product-analytics/person-properties.md)
--   **userPropertiesSetOnce:** Optional. Similar to `userProperties`. [See the difference between `userProperties` and `userPropertiesSetOnce`](/docs/product-analytics/person-properties.md#what-is-the-difference-between-set-and-set_once)
-
-Dart
+-   **userProperties:** Optional. A dictionary with key:value pairs to set the [person properties](https://posthog.com/docs/product-analytics/person-properties.md)
+-   **userPropertiesSetOnce:** Optional. Similar to `userProperties`. [See the difference between `userProperties` and `userPropertiesSetOnce`](https://posthog.com/docs/product-analytics/person-properties.md#what-is-the-difference-between-set-and-set_once)
 
 ```dart
 await Posthog().identify(
@@ -428,21 +474,19 @@ 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.
 
-Dart
-
 ```dart
 await Posthog().alias(
   alias: 'distinct_id',
 );
 ```
 
-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.
 
 ## Anonymous vs identified events
 
-PostHog captures two types of events: [**anonymous** and **identified**](/docs/data/anonymous-vs-identified-events.md)
+PostHog captures two types of events: [**anonymous** and **identified**](https://posthog.com/docs/data/anonymous-vs-identified-events.md)
 
-**Identified events** enable you to attribute events to specific users, and attach [person properties](/docs/product-analytics/person-properties.md). They're best suited for logged-in users.
+**Identified events** enable you to attribute events to specific users, and attach [person properties](https://posthog.com/docs/product-analytics/person-properties.md). They're best suited for logged-in users.
 
 Scenarios where you want to capture identified events are:
 
@@ -450,7 +494,7 @@ Scenarios where you want to capture identified events are:
 -   Doing user segmented product analysis
 -   Growth and marketing teams wanting to analyze the *complete* conversion lifecycle
 
-**Anonymous events** are events without individually identifiable data. They're best suited for [web analytics](/docs/web-analytics.md) or apps where users aren't logged in.
+**Anonymous events** are events without individually identifiable data. They're best suited for [web analytics](https://posthog.com/docs/web-analytics.md) or apps where users aren't logged in.
 
 Scenarios where you want to capture anonymous events are:
 
@@ -458,15 +502,15 @@ Scenarios where you want to capture anonymous events are:
 -   Content-focused sites
 -   B2C apps where users don't sign up or log in
 
-Under the hood, the key difference between identified and anonymous events is that for identified events we create a [person profile](/docs/data/persons.md) for the user, whereas for anonymous events we do not.
+Under the hood, the key difference between identified and anonymous events is that for identified events we create a [person profile](https://posthog.com/docs/data/persons.md) for the user, whereas for anonymous events we do not.
 
 > **Important:** Due to the reduced cost of processing them, anonymous events can be up to 4x cheaper than identified ones, so we recommended you only capture identified events when needed.
 
 ### How to capture anonymous events
 
-The Flutter SDK captures anonymous events by default. However, this may change depending on your `personProfiles` [config](/docs/libraries/flutter.md#person-profiles-anonymous-vs-identified-persons) when initializing PostHog:
+The Flutter SDK captures anonymous events by default. However, this may change depending on your `personProfiles` [config](https://posthog.com/docs/libraries/flutter.md#person-profiles-anonymous-vs-identified-persons) when initializing PostHog:
 
-1.  `personProfiles: PostHogPersonProfiles.identifiedOnly` *(recommended)* *(default)* - Anonymous events are captured by default. PostHog only captures identified events for users where [person profiles](/docs/data/persons.md) have already been created.
+1.  `personProfiles: PostHogPersonProfiles.identifiedOnly` *(recommended)* *(default)* - Anonymous events are captured by default. PostHog only captures identified events for users where [person profiles](https://posthog.com/docs/data/persons.md) have already been created.
 
 2.  `personProfiles: PostHogPersonProfiles.always` - Capture identified events for all events.
 
@@ -474,8 +518,6 @@ The Flutter SDK captures anonymous events by default. However, this may change d
 
 For example:
 
-Dart
-
 ```dart
 final config = PostHogConfig('<ph_project_token>');
 config.host = 'https://us.i.posthog.com';
@@ -484,13 +526,13 @@ config.personProfiles = PostHogPersonProfiles.identifiedOnly;
 
 ### How to capture identified events
 
-If you've set the [`personProfiles` config](/docs/libraries/flutter.md#person-profiles-anonymous-vs-identified-persons) to `PostHogPersonProfiles.identifiedOnly` (the default option), anonymous events are captured by default. Then, to capture identified events, call any of the following functions:
+If you've set the [`personProfiles` config](https://posthog.com/docs/libraries/flutter.md#person-profiles-anonymous-vs-identified-persons) to `PostHogPersonProfiles.identifiedOnly` (the default option), anonymous events are captured by default. Then, to capture identified events, call any of the following functions:
 
--   [`identify()`](/docs/product-analytics/identify.md)
--   [`alias()`](/docs/product-analytics/identify.md#alias-assigning-multiple-distinct-ids-to-the-same-user)
--   [`group()`](/docs/product-analytics/group-analytics.md)
+-   [`identify()`](https://posthog.com/docs/product-analytics/identify.md)
+-   [`alias()`](https://posthog.com/docs/product-analytics/identify.md#alias-assigning-multiple-distinct-ids-to-the-same-user)
+-   [`group()`](https://posthog.com/docs/product-analytics/group-analytics.md)
 
-When you call any of these functions, it creates a [person profile](/docs/data/persons.md) for the user. Once this profile is created, all subsequent events for this user will be captured as identified events.
+When you call any of these functions, it creates a [person profile](https://posthog.com/docs/data/persons.md) for the user. Once this profile is created, all subsequent events for this user will be captured as identified events.
 
 Alternatively, you can set `personProfiles` to `PostHogPersonProfiles.always` to capture identified events by default.
 
@@ -502,8 +544,6 @@ They are set using `Posthog().register`, which takes a key and value, and they p
 
 For example, take a look at the following call:
 
-Dart
-
 ```dart
 import 'package:posthog_flutter/posthog_flutter.dart';
 
@@ -518,8 +558,6 @@ However, please note that this does not store properties against the User, only
 
 Super properties are persisted across sessions so you have to explicitly remove them if they are no longer relevant. In order to stop sending a super property with events, you can use `Posthog().unregister`, like so:
 
-Dart
-
 ```dart
 import 'package:posthog_flutter/posthog_flutter.dart';
 
@@ -532,18 +570,16 @@ If you are doing this as part of a user logging out you can instead simply use `
 
 ## Group analytics
 
-Group analytics allows you to associate the events for that person's session with a group (e.g. teams, organizations, etc.). See [Group Analytics](/docs/product-analytics/group-analytics.md) for Flutter examples and implementation details.
+Group analytics allows you to associate the events for that person's session with a group (e.g. teams, organizations, etc.). See [Group Analytics](https://posthog.com/docs/product-analytics/group-analytics.md) for Flutter examples and implementation details.
 
-> **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).
 
 ## 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.
 
 ### Boolean feature flags
 
-Dart
-
 ```dart
 final result = await Posthog().getFeatureFlagResult('flag-key');
 if (result != null && result.enabled) {
@@ -556,8 +592,6 @@ if (result != null && result.enabled) {
 
 ### Multivariate feature flags
 
-Dart
-
 ```dart
 final result = await Posthog().getFeatureFlagResult('flag-key');
 if (result != null && result.variant == 'variant-key') { // replace 'variant-key' with the key of your variant
@@ -578,8 +612,6 @@ This means that for most screens, the feature flags are available immediately
 
 To handle this, you can use the `onFeatureFlags` callback in your config to be notified when flags are loaded:
 
-Dart
-
 ```dart
 final config = PostHogConfig('<ph_project_token>');
 config.host = 'https://us.i.posthog.com';
@@ -595,8 +627,6 @@ await Posthog().setup(config);
 
 Feature flag values are cached. If something has changed with your user and you'd like to refetch their flag values, call:
 
-Dart
-
 ```dart
 await Posthog().reloadFeatureFlags();
 ```
@@ -609,8 +639,6 @@ To have your feature flags available immediately, you can initialize PostHog wit
 
 Set `config.bootstrap` before calling `setup()` to seed identity and flag values before the first `/flags` response (requires the Flutter SDK `5.31.0`+):
 
-Dart
-
 ```dart
 final config = PostHogConfig('<ph_project_token>');
 config.host = 'https://us.i.posthog.com';
@@ -634,14 +662,12 @@ The values are forwarded to the native iOS and Android SDKs:
 
 The feature-flags-loaded signal fires as soon as bootstrapped flags are applied, so startup logic can read them immediately. These SDKs don't support the `sessionID` bootstrap option. When person profiles are set to `never`, the SDK preserves a different anonymous identity instead of merging it into an identified bootstrap.
 
-On Flutter web, `bootstrap` is not applied, so configure it in your `posthog.init({...})` snippet instead. See the [SDK bootstrapping guide](/docs/libraries/bootstrapping.md) for the cross-SDK overview.
+On Flutter web, `bootstrap` is not applied, so configure it in your `posthog.init({...})` snippet instead. See the [SDK bootstrapping guide](https://posthog.com/docs/libraries/bootstrapping.md) for the cross-SDK overview.
 
 ### Setting properties for flag evaluation
 
 If a flag targets person or group properties, you can send those properties inline with the next flag evaluation request instead of waiting for a `$set` event to be ingested. This avoids the race where a flag returns a stale value right after you set a property.
 
-Dart
-
 ```dart
 // Person properties — included in the next flag evaluation request
 await Posthog().setPersonPropertiesForFlags({
@@ -653,41 +679,41 @@ await Posthog().setPersonPropertiesForFlags({
 await Posthog().setGroupPropertiesForFlags('company', {'plan': 'enterprise'});
 ```
 
-By default these reload feature flags, and the returned `Future` completes once the reload finishes, so the next `getFeatureFlag` reflects the new properties. Pass `reloadFeatureFlags: false` to set several properties before reloading. Use `resetPersonPropertiesForFlags()` and `resetGroupPropertiesForFlags()` to clear them. See [property overrides for flag evaluation](/docs/feature-flags/property-overrides.md) for details.
+By default these reload feature flags, and the returned `Future` completes once the reload finishes, so the next `getFeatureFlag` reflects the new properties. Pass `reloadFeatureFlags: false` to set several properties before reloading. Use `resetPersonPropertiesForFlags()` and `resetGroupPropertiesForFlags()` to clear them. See [property overrides for flag evaluation](https://posthog.com/docs/feature-flags/property-overrides.md) for details.
 
 ## 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. See [feature flag code examples](/docs/feature-flags/adding-feature-flag-code?tab=Flutter.md) for Flutter implementation details.
+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. See [feature flag code examples](https://posthog.com/docs/feature-flags/adding-feature-flag-code?tab=Flutter.md) for Flutter implementation details.
 
-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).
 
 ## Error tracking
 
-To set up error tracking in your project, see the [error tracking docs](/docs/error-tracking.md).
+To set up error tracking in your project, see the [error tracking docs](https://posthog.com/docs/error-tracking.md).
 
 ## Logs
 
-To set up [logs](/docs/logs.md) in your Flutter app, follow the [Flutter logs installation guide](/docs/logs/installation/flutter.md). The SDK exposes `Posthog().logger.{trace,debug,info,warn,error,fatal}` (and `Posthog().captureLog` for full control) for sending structured records to PostHog Logs, with batching, offline persistence, and a rate cap built in.
+To set up [logs](https://posthog.com/docs/logs.md) in your Flutter app, follow the [Flutter logs installation guide](https://posthog.com/docs/logs/installation/flutter.md). The SDK exposes `Posthog().logger.{trace,debug,info,warn,error,fatal}` (and `Posthog().captureLog` for full control) for sending structured records to PostHog Logs, with batching, offline persistence, and a rate cap built in.
 
 ## Session replay
 
 > **Note:** Session replay is supported on Flutter Web, Android, and iOS.
 
-To set up [session replay web](/docs/session-replay.md) or [mobile session replay](/docs/session-replay/mobile.md) in your project, all you need to do is install the Flutter SDK, follow the [additional installation instructions](/docs/session-replay/installation/flutter.md), and enable "Record user sessions" in [your project settings](https://us.posthog.com/settings/project-replay) and enable the `sessionReplay` option.
+To set up [session replay web](https://posthog.com/docs/session-replay.md) or [mobile session replay](https://posthog.com/docs/session-replay/mobile.md) in your project, all you need to do is install the Flutter SDK, follow the [additional installation instructions](https://posthog.com/docs/session-replay/installation/flutter.md), and enable "Record user sessions" in [your project settings](https://us.posthog.com/settings/project-replay) and enable the `sessionReplay` option.
 
-If you're using Flutter Web, also enable the [Canvas capture](/docs/session-replay/canvas-recording.md) in [your project settings](https://us.posthog.com/settings/project-replay). This is needed as Flutter renders your app using a browser canvas element.
+If you're using Flutter Web, also enable the [Canvas capture](https://posthog.com/docs/session-replay/canvas-recording.md) in [your project settings](https://us.posthog.com/settings/project-replay). This is needed as Flutter renders your app using a browser canvas element.
 
-On Flutter Web, masking (`maskAllTexts`, `maskAllImages`, `PostHogMaskWidget`) applies inside that canvas too — declare `session_recording.canvasCapture.maskRegionsFn` in the `posthog.init` call in your `web/index.html` to enable it (requires PostHog Flutter SDK 5.34.0+ and posthog-js 1.408.0+). See [masking on Flutter Web](/docs/session-replay/privacy.md) under the Flutter tab.
+On Flutter Web, masking (`maskAllTexts`, `maskAllImages`, `PostHogMaskWidget`) applies inside that canvas too — declare `session_recording.canvasCapture.maskRegionsFn` in the `posthog.init` call in your `web/index.html` to enable it (requires PostHog Flutter SDK 5.34.0+ and posthog-js 1.408.0+). See [masking on Flutter Web](https://posthog.com/docs/session-replay/privacy.md) under the Flutter tab.
 
 ## Surveys
 
 > **Note:** Surveys are supported in Flutter for **Web**, **iOS**, and **Android** platforms.
 
-[Surveys](/docs/surveys.md) launched with [popover presentation](/docs/surveys/creating-surveys.md#presentation) are automatically shown to users matching the [display conditions](/docs/surveys/creating-surveys.md#display-conditions) you set up.
+[Surveys](https://posthog.com/docs/surveys.md) launched with [popover presentation](https://posthog.com/docs/surveys/creating-surveys.md#presentation) are automatically shown to users matching the [display conditions](https://posthog.com/docs/surveys/creating-surveys.md#display-conditions) you set up.
 
 ## Push notifications
 
-The Flutter SDK can register a device for [Workflows](/docs/workflows.md) push notifications and capture when a user opens one. For setup, including automatic and manual registration, capturing opens, opting out, and identity verification, see [Push notifications](/docs/workflows/push-notifications.md).
+The Flutter SDK can register a device for [Workflows](https://posthog.com/docs/workflows.md) push notifications and capture when a user opens one. For setup, including automatic and manual registration, capturing opens, opting out, and identity verification, see [Push notifications](https://posthog.com/docs/workflows/push-notifications.md).
 
 ## Flush
 
@@ -695,8 +721,6 @@ You can configure how many events queue before flushing with `flushAt`. Setting
 
 You can also configure the flush interval with `flushInterval` (default 30 seconds), after which queued events are sent regardless of how many have been gathered:
 
-Dart
-
 ```dart
 final config = PostHogConfig('<ph_project_token>');
 config.flushAt = 20;
@@ -705,8 +729,6 @@ config.flushInterval = const Duration(seconds: 30);
 
 You can also manually flush the queue to start sending events immediately instead of waiting for the next batch:
 
-Dart
-
 ```dart
 await Posthog().flush();
 ```
@@ -725,24 +747,18 @@ The PostHog Flutter SDK will continue to capture events when the device is offli
 
 You can disable data collection for a user at any time using the `disable()` method:
 
-Dart
-
 ```dart
 await Posthog().disable();
 ```
 
 This prevents any future events from being sent. It doesn't remove events already captured for the user. To opt the user back in:
 
-Dart
-
 ```dart
 await Posthog().enable();
 ```
 
 To check if a user is opted out:
 
-Dart
-
 ```dart
 await Posthog().isOptOut();
 ```
@@ -755,8 +771,6 @@ Since version 5.13.0, you can provide `beforeSend` callbacks when initializing t
 
 `beforeSend` gives you one place to edit or redact information before it is sent to PostHog. For example:
 
-Dart
-
 ```dart
 final config = PostHogConfig('<ph_project_token>');
 config.host = 'https://us.i.posthog.com';
@@ -778,8 +792,6 @@ await Posthog().setup(config);
 
 Return `null` from the callback to drop the event:
 
-Dart
-
 ```dart
 config.beforeSend = [
   (event) {
@@ -798,8 +810,6 @@ You can stop specific screens from being autocaptured by filtering them in your
 
 Because it's just a function, you can filter however you like – an **ignorelist** (drop the screens you name), an **allowlist** (invert the check to capture only the screens you name), or any custom rule such as a name prefix, a regex, or a check against the event's properties.
 
-Dart
-
 ```dart
 const ignoredScreens = {'Splash', 'Debug'};
 
@@ -835,8 +845,6 @@ If you're not seeing the expected events being captured, the feature flags being
 
 You can enable debug mode during initialization by setting the `debug` option to `true` in the `PostHogConfig` object. A common pattern is to set this to `true` in development environments only using environment variables.
 
-Dart
-
 ```dart
 final config = PostHogConfig('<ph_project_token>');
 config.host = 'https://us.i.posthog.com';
@@ -848,17 +856,7 @@ This will enable verbose logs about the inner workings of the SDK.
 
 You can also enable debug by calling the `Posthog().debug()` method in your code.
 
-Dart
-
 ```dart
 await Posthog().debug(true);
 await Posthog().debug(false);
 ```
-
-### Still have questions?
-
-Ask PostHog AI
-
-### Was this page useful?
-
-HelpfulCould be better