txlemetry-react-native 4.55.1 → 5.0.0

package/dist/{posthog-rn.d.ts → txlemetry-rn.d.ts}

@@ -1,1096 +1,1096 @@
-import { CaptureLogOptions, CaptureLogger, JsonType, PostHogCaptureOptions, PostHogCore, PostHogCoreOptions, PostHogEventProperties, PostHogFetchOptions, PostHogFetchResponse, PostHogLogsConfig, PostHogPersistedProperty, PostHogRemoteConfig, SurveyResponse, FeatureFlagResultOptions, ErrorTracking as CoreErrorTracking } from '@txlemetry/core';
-import { Properties } from '@txlemetry/types';
-import { PostHogAutocaptureOptions, PostHogCustomAppProperties, PostHogCustomStorage, PostHogSessionReplayConfig } from './types';
-import { OptionalReactNativePlugin } from './optional/OptionalPlugin';
-import { ErrorTrackingOptions } from './error-tracking';
-export { PostHogPersistedProperty };
-export interface PostHogOptions extends PostHogCoreOptions {
-    /**
-     * Allows you to provide the storage type.
-     * 'file' will try to load the best available storage, the provided 'customStorage', 'customAsyncStorage' or in-memory storage.
-     *
-     * @default 'file'
-     */
-    persistence?: 'memory' | 'file';
-    /** Allows you to provide your own implementation of the common information about your App or a function to modify the default App properties generated */
-    customAppProperties?: PostHogCustomAppProperties | ((properties: PostHogCustomAppProperties) => PostHogCustomAppProperties);
-    /**
-     * Allows you to provide a custom asynchronous storage such as async-storage, expo-file-system or a synchronous storage such as mmkv.
-     * If not provided, PostHog will attempt to use the best available storage via optional peer dependencies (async-storage, expo-file-system).
-     * If `persistence` is set to 'memory', this option will be ignored.
-     */
-    customStorage?: PostHogCustomStorage;
-    /**
-     * A list of headers that should be sent with requests to the PostHog API.
-     */
-    requestHeaders?: {
-        [header_name: string]: string;
-    };
-    /**
-     * Captures app lifecycle events such as Application Installed, Application Updated, Application Opened, Application Became Active and Application Backgrounded.
-     * Application Installed and Application Updated events are not supported with persistence set to 'memory'.
-     *
-     * @default true
-     */
-    captureAppLifecycleEvents?: boolean;
-    /**
-     * Enable Recording of Session Replays for Android and iOS
-     * Requires Record user sessions to be enabled in the PostHog Project Settings
-     *
-     * @default false
-     */
-    enableSessionReplay?: boolean;
-    /**
-     * Configuration for Session Replay
-     */
-    sessionReplayConfig?: PostHogSessionReplayConfig;
-    /**
-     * If enabled, the session id ($session_id) will be persisted across app restarts.
-     * This is an option for back compatibility, so your current data isn't skewed with the new version of the SDK.
-     * If this is false, the session id will be always reset on app restart.
-     *
-     * @default false
-     */
-    enablePersistSessionIdAcrossRestart?: boolean;
-    /**
-     * Error Tracking Configuration
-     */
-    errorTracking?: ErrorTrackingOptions;
-    /**
-     * Automatically include common device and app properties in feature flag evaluation.
-     *
-     * When enabled, the following properties are sent with every /flags request:
-     * - $app_version: App version
-     * - $app_build: App build number
-     * - $app_namespace: App bundle identifier / namespace
-     * - $os_name: Operating system name
-     * - $os_version: Operating system version
-     * - $device_type: Device type (Mobile, Desktop)
-     * - $lib: Name of the SDK library
-     * - $lib_version: Version of the SDK library
-     *
-     * This ensures feature flags that rely on these properties work correctly
-     * without waiting for server-side processing of identify() calls.
-     *
-     * @default true
-     */
-    setDefaultPersonProperties?: boolean;
-    /**
-     * Logs feature configuration. Enables structured log capture via
-     * `posthog.captureLog(...)` or `posthog.logger.info(...)`. Records ship to
-     * PostHog's logs product (`/i/v1/logs`) in OTLP format, batched on a timer,
-     * AppState change, buffer fill, or manual `flushLogs()`.
-     *
-     * Capture is **unconditional** — calling the API ships records as long as
-     * the SDK is initialized and the user hasn't opted out. The only blockers
-     * are `optedOut`, missing/empty `body`, and missing API key.
-     *
-     * All fields below are optional; per-SDK defaults apply (mobile defaults
-     * are tuned for cellular bandwidth and battery, ~50 logs/sec ceiling).
-     *
-     * @example Minimal — just service tagging, defaults for everything else
-     * ```ts
-     * new PostHog(key, {
-     *   logs: { serviceName: 'my-app', environment: 'production' }
-     * })
-     * ```
-     *
-     * @example Tune for higher-volume logging
-     * ```ts
-     * new PostHog(key, {
-     *   logs: {
-     *     serviceName: 'my-app',
-     *     rateCap: { maxLogs: 5000, windowMs: 60000 },
-     *     maxBufferSize: 500,
-     *     beforeSend: (r) => r.body.includes('secret') ? null : r,
-     *   }
-     * })
-     * ```
-     */
-    logs?: PostHogLogsConfig;
-    /**
-     * Overrides the language used when rendering translated survey copy.
-     * When unset, the SDK falls back to the persisted person property `language`
-     * and then the device locale.
-     */
-    overrideDisplayLanguage?: string | null;
-}
-export declare class PostHog extends PostHogCore {
-    private _persistence;
-    private _eventsStorage;
-    private _logsStorage;
-    private _appProperties;
-    private _currentSessionId?;
-    private _enableSessionReplay?;
-    private _sessionReplayNativeInitialized;
-    private _nativeErrorTrackingInitialized;
-    private _sessionReplayRecordingActive?;
-    private _sessionReplayEvalChain;
-    private _sessionReplayOptions?;
-    private _sessionReplayEventTriggers;
-    private _disableSurveys;
-    private _errorTracking;
-    private _logs;
-    private _resolvedLogsConfig;
-    private _currentAppState?;
-    private _surveysReadyPromise;
-    private _surveysReady;
-    private _setDefaultPersonProperties;
-    private _overrideDisplayLanguage;
-    private _requestHeaders;
-    /**
-     * Creates a new PostHog instance for React Native. You can find all configuration options in the [React Native SDK docs](https://posthog.com/docs/libraries/react-native#configuration-options).
-     *
-     * If you prefer not to use the PostHogProvider, you can initialize PostHog in its own file and import the instance from there.
-     *
-     * {@label Initialization}
-     *
-     * @example
-     * ```ts
-     * // posthog.ts
-     * import PostHog from 'posthog-react-native'
-     *
-     * export const posthog = new PostHog('<ph_project_api_key>', {
-     *   host: '<ph_client_api_host>'
-     * })
-     *
-     * // Then you can access PostHog by importing your instance
-     * // Another file:
-     * import { posthog } from './posthog'
-     *
-     * export function MyApp1() {
-     *     useEffect(async () => {
-     *         posthog.capture('event_name')
-     *     }, [posthog])
-     *
-     *     return <View>Your app code</View>
-     * }
-     * ```
-     *
-     * @public
-     *
-     * @param apiKey - Your PostHog API key
-     * @param options - PostHog configuration options
-     */
-    constructor(apiKey: string, options?: PostHogOptions);
-    /**
-     *
-     * @internal
-     *
-     */
-    ready(): Promise<void>;
-    /**
-     * Called when remote config has been loaded (from either the remote config endpoint or the flags endpoint).
-     * Gates error tracking autocapture based on the remote config response.
-     *
-     * Session replay config (consoleLogRecordingEnabled, sampleRate, capturePerformance.network_timing) is already
-     * cached via PostHogPersistedProperty.RemoteConfig and applied at startup in startSessionReplay().
-     *
-     * @internal
-     */
-    protected onRemoteConfig(response: PostHogRemoteConfig): void;
-    /**
-     * Resolves the storage instance for a given persisted-property key.
-     * `LogsQueue` routes to `_logsStorage` (dedicated `.posthog-rn-logs.json`
-     * file); every other key routes to `_eventsStorage`. Single source of
-     * truth for routing — extending to new logs-scoped keys is a one-line
-     * edit here.
-     */
-    private _storageForKey;
-    getPersistedProperty<T>(key: PostHogPersistedProperty): T | undefined;
-    setPersistedProperty<T>(key: PostHogPersistedProperty, value: T | null): void;
-    /**
-     * Waits for any pending storage operations to complete.
-     * This ensures data has been safely written to async storage before
-     * considering events as sent, preventing duplicate events on app crash/restart.
-     */
-    protected flushStorage(): Promise<void>;
-    /**
-     * Drain both pipelines on shutdown. Run in parallel so the logs final
-     * flush + timer teardown doesn't serialize behind events (and vice-versa).
-     * `_logs.shutdown()` swallows its own errors — a transient logs failure
-     * must not break events shutdown.
-     *
-     * Logs use the smaller of `terminationFlushBudgetMs` and the caller's
-     * `shutdownTimeoutMs` so a final flush can never run past the caller's
-     * shutdown SLA, while still respecting the configured logs-specific
-     * termination budget when it's tighter.
-     *
-     * After the flushes, drain any debounced storage writes that weren't already
-     * persisted via the queue-advance path — `setPersistedProperty` calls for
-     * distinctId, sessionId, deviceId, feature flag overrides, etc. only arm a
-     * debounced write. The drain runs in `finally` so a timed-out flush still
-     * persists them, and its await is bounded by the time left in the shutdown
-     * SLA so a hung storage backend can't run past it.
-     */
-    _shutdown(shutdownTimeoutMs?: number): Promise<void>;
-    fetch(url: string, options: PostHogFetchOptions): Promise<PostHogFetchResponse>;
-    getLibraryId(): string;
-    getLibraryVersion(): string;
-    getCustomUserAgent(): string;
-    protected getCustomHeaders(): {
-        [key: string]: string;
-    };
-    getCommonEventProperties(): PostHogEventProperties;
-    getSurveyDisplayLanguageOverride(): string | null;
-    /**
-     * Registers super properties that are sent with every event.
-     *
-     * Super properties are properties associated with events that are set once and then sent with every capture call.
-     * They persist across sessions and are stored locally.
-     *
-     * {@label Capture}
-     *
-     * @example
-     * ```js
-     * // register super properties
-     * posthog.register({
-     *     'icecream pref': 'vanilla',
-     *     team_id: 22,
-     * })
-     * ```
-     *
-     * @public
-     *
-     * @param properties An associative array of properties to store about the user
-     */
-    register(properties: PostHogEventProperties): Promise<void>;
-    /**
-     * Removes a super property so it won't be sent with future events.
-     *
-     * Super Properties are persisted across sessions so you have to explicitly remove them if they are no longer relevant.
-     *
-     * {@label Capture}
-     *
-     * @example
-     * ```js
-     * // remove a super property
-     * posthog.unregister('icecream pref')
-     * ```
-     *
-     * @public
-     *
-     * @param property The name of the super property to remove
-     */
-    unregister(property: string): Promise<void>;
-    /**
-     * Resets the user's ID and anonymous ID after logout.
-     *
-     * To reset the user's ID and anonymous ID, call reset. Usually you would do this right after the user logs out.
-     * This also clears all stored super properties and more.
-     *
-     * By default (when `propertiesToKeep` is not provided), the app lifecycle properties
-     * (`InstalledAppBuild` and `InstalledAppVersion`) are automatically preserved to prevent
-     * duplicate "Application Installed" events on the next app launch.
-     *
-     * If you pass `propertiesToKeep` explicitly, only the properties you specify will be preserved.
-     * To keep the default app lifecycle behavior, include `PostHogPersistedProperty.InstalledAppBuild`
-     * and `PostHogPersistedProperty.InstalledAppVersion` in your array.
-     *
-     * Note: The event queue (`PostHogPersistedProperty.Queue`) and logs queue
-     * (`PostHogPersistedProperty.LogsQueue`) are always preserved regardless of
-     * what is passed in `propertiesToKeep`, to ensure in-flight data is not lost.
-     *
-     * The project-level remote config (`PostHogPersistedProperty.RemoteConfig`,
-     * `PostHogPersistedProperty.SessionReplay`, `PostHogPersistedProperty.Surveys`) is also
-     * always preserved — it is not user data — so session replay and surveys keep working
-     * after an identity change. The user-specific survey state (`SurveysSeen`,
-     * `SurveyLastSeenDate`) is still cleared.
-     *
-     * {@label Identification}
-     *
-     * @example
-     * ```js
-     * // reset after logout (preserves app lifecycle properties by default)
-     * posthog.reset()
-     * ```
-     *
-     * @example
-     * ```js
-     * // reset but keep feature flag overrides and app lifecycle properties
-     * posthog.reset([
-     *   PostHogPersistedProperty.OverrideFeatureFlags,
-     *   PostHogPersistedProperty.InstalledAppBuild,
-     *   PostHogPersistedProperty.InstalledAppVersion,
-     * ])
-     * ```
-     *
-     * @param propertiesToKeep - Optional array of persisted properties to preserve during reset.
-     *   When not provided, app lifecycle and device bucketing properties are automatically preserved.
-     *   When provided, only the specified properties are preserved.
-     *   The event queue and logs queue are always preserved regardless.
-     *
-     * @public
-     */
-    reset(propertiesToKeep?: PostHogPersistedProperty[]): void;
-    /**
-     * Helper to extract and set default person properties from app properties
-     *
-     * @private
-     *
-     * @param reloadFeatureFlags Whether to reload feature flags after setting the properties. Defaults to true.
-     */
-    private _setDefaultPersonPropertiesForFlags;
-    /**
-     * Manually flushes the event queue.
-     *
-     * You can set the number of events in the configuration that should queue before flushing.
-     * Setting this to 1 will send events immediately and will use more battery. This is set to 20 by default.
-     * You can also manually flush the queue. If a flush is already in progress it returns a promise for the existing flush.
-     *
-     * Note: this drains the **events** pipeline only. Logs are flushed via
-     * {@link flushLogs}, and {@link shutdown} drains both before terminating.
-     *
-     * {@label Capture}
-     *
-     * @example
-     * ```js
-     * // manually flush the queue
-     * await posthog.flush()
-     * ```
-     *
-     * @see flushLogs
-     * @public
-     *
-     * @returns Promise that resolves when the flush is complete
-     */
-    flush(): Promise<void>;
-    /**
-     * Captures a structured log record and sends it to PostHog's logs product
-     * (`/i/v1/logs`). Low-level primitive — most callers will prefer
-     * `posthog.logger.info(...)` / `.warn(...)` / `.error(...)` etc., which
-     * wrap this with a level pre-set.
-     *
-     * Records are buffered per-session, rate-limited, batched into OTLP
-     * payloads, and flushed on a timer, on AppState change, or when the
-     * buffer reaches capacity. Configure flush cadence, rate cap, and a
-     * `beforeSend` filter via the `logs` option on `new PostHog(...)`.
-     *
-     * Note — naming collision: `posthog.captureLog()` (this method) is the
-     * **logs product** API. There is also a separate, pre-existing
-     * `sessionReplayConfig.captureLog` boolean that controls whether
-     * **session replay** records the device's `console.*` output. The two
-     * are unrelated: this method emits structured records to the logs
-     * pipeline regardless of whether session replay is on.
-     *
-     * {@label Capture}
-     *
-     * @example
-     * ```ts
-     * posthog.captureLog({
-     *   body: 'checkout completed',
-     *   level: 'info',
-     *   attributes: { order_id: 'ord_789', amount_cents: 4999 },
-     * })
-     * ```
-     *
-     * @public
-     *
-     * @param options Log record. `body` is required; `level` defaults to
-     *   `'info'`. `attributes` are attached as OTLP key-value attributes
-     *   and will override auto-populated ones (distinctId, sessionId) on
-     *   key conflict.
-     */
-    captureLog(options: CaptureLogOptions): void;
-    /**
-     * Manually flushes the logs queue.
-     *
-     * Logs flush automatically on a timer, when the buffer fills, or on
-     * AppState change — most apps never need to call this. Use it when you
-     * want a synchronous-style hand-off (e.g. before navigating away from a
-     * critical screen, in a custom crash handler, or while testing locally).
-     *
-     * If a flush is already in progress, both callers join the same in-flight
-     * promise — no double-send.
-     *
-     * Note: this drains the **logs** pipeline only. Events are flushed via
-     * {@link flush}, and {@link shutdown} drains both before terminating.
-     *
-     * {@label Capture}
-     *
-     * @example
-     * ```ts
-     * await posthog.flushLogs()
-     * ```
-     *
-     * @see flush
-     * @public
-     *
-     * @returns Promise that resolves when the flush is complete.
-     */
-    flushLogs(): Promise<void>;
-    private _captureLogger?;
-    /**
-     * Convenience per-level logger. Each method is shorthand for
-     * `posthog.captureLog({ body, level, attributes })`. Lazily constructed
-     * on first access, then reused.
-     *
-     * {@label Capture}
-     *
-     * @example
-     * ```ts
-     * posthog.logger.info('checkout completed', { order_id: 'ord_789' })
-     * posthog.logger.error('payment failed', { code: 'E001' })
-     * ```
-     *
-     * @public
-     */
-    get logger(): CaptureLogger;
-    /**
-     * Opts the user in to data capture.
-     *
-     * By default, PostHog has tracking enabled unless it is forcefully disabled by default using the option { defaultOptIn: false }.
-     * Once this has been called it is persisted and will be respected until optOut is called again or the reset function is called.
-     *
-     * {@label Privacy}
-     *
-     * @example
-     * ```js
-     * // opt in to tracking
-     * posthog.optIn()
-     * ```
-     *
-     * @public
-     */
-    optIn(): Promise<void>;
-    /**
-     * Opts the user out of data capture.
-     *
-     * You can completely opt-out users from data capture. Once this has been called it is persisted and will be respected until optIn is called again or the reset function is called.
-     *
-     * {@label Privacy}
-     *
-     * @example
-     * ```js
-     * // opt out of tracking
-     * posthog.optOut()
-     * ```
-     *
-     * @public
-     */
-    optOut(): Promise<void>;
-    /**
-     * Checks if a feature flag is enabled for the current user.
-     *
-     * Defaults to undefined if not loaded yet or if there was a problem loading.
-     *
-     * {@label Feature flags}
-     *
-     * @example
-     * ```js
-     * // check if feature flag is enabled
-     * const isEnabled = posthog.isFeatureEnabled('key-for-your-boolean-flag')
-     * ```
-     *
-     * @public
-     *
-     * @param key The feature flag key
-     * @param options Optional per-call settings
-     * @returns True if enabled, false if disabled, undefined if not loaded
-     */
-    isFeatureEnabled(key: string, options?: FeatureFlagResultOptions): boolean | undefined;
-    /**
-     * Gets the value of a feature flag for the current user.
-     *
-     * Defaults to undefined if not loaded yet or if there was a problem loading.
-     * Multivariant feature flags are returned as a string.
-     *
-     * {@label Feature flags}
-     *
-     * @example
-     * ```js
-     * // get feature flag value
-     * const value = posthog.getFeatureFlag('key-for-your-boolean-flag')
-     * ```
-     *
-     * @public
-     *
-     * @param key The feature flag key
-     * @param options Optional per-call settings
-     * @returns The feature flag value or undefined if not loaded
-     */
-    getFeatureFlag(key: string, options?: FeatureFlagResultOptions): boolean | string | undefined;
-    /**
-     * Gets the payload of a feature flag for the current user.
-     *
-     * Returns JsonType or undefined if not loaded yet or if there was a problem loading.
-     *
-     * {@label Feature flags}
-     *
-     * @deprecated Use `getFeatureFlagResult()` instead, which returns the flag value and payload from a single evaluation.
-     *
-     * @example
-     * ```js
-     * // get feature flag payload
-     * const payload = posthog.getFeatureFlagResult('key-for-your-multivariate-flag')?.payload
-     * ```
-     *
-     * @public
-     *
-     * @param key The feature flag key
-     * @returns The feature flag payload or undefined if not loaded
-     */
-    getFeatureFlagPayload(key: string): JsonType | undefined;
-    /**
-     * Reloads feature flags from the server.
-     *
-     * PostHog loads feature flags when instantiated and refreshes whenever methods are called that affect the flag.
-     * If you want to manually trigger a refresh, you can call this method.
-     *
-     * {@label Feature flags}
-     *
-     * @remarks
-     * When the `disableRemoteFeatureFlags` option is set, this method is a no-op; supply
-     * flag values via `updateFlags()` instead.
-     *
-     * @example
-     * ```js
-     * // reload feature flags
-     * posthog.reloadFeatureFlags()
-     * ```
-     *
-     * @public
-     */
-    reloadFeatureFlags(): void;
-    /**
-     * Reloads feature flags from the server asynchronously.
-     *
-     * PostHog loads feature flags when instantiated and refreshes whenever methods are called that affect the flag.
-     * If you want to manually trigger a refresh and get the result, you can call this method.
-     *
-     * {@label Feature flags}
-     *
-     * @example
-     * ```js
-     * // reload feature flags and get result
-     * posthog.reloadFeatureFlagsAsync().then((refreshedFlags) => console.log(refreshedFlags))
-     * ```
-     *
-     * @public
-     *
-     * @remarks
-     * When the `disableRemoteFeatureFlags` option is set, no request is made and the
-     * promise resolves with the currently stored flags (from `bootstrap` or `updateFlags()`).
-     *
-     * @returns Promise that resolves with the refreshed flags
-     */
-    reloadFeatureFlagsAsync(): Promise<Record<string, boolean | string> | undefined>;
-    /**
-     * Replaces (or merges into) the stored feature flags and payloads with locally supplied
-     * values, exactly as if they had been returned by the flags endpoint: the values are
-     * persisted, `getFeatureFlag()`/`getFeatureFlagPayload()` read them back, and
-     * `onFeatureFlags` listeners fire. Makes no network request.
-     *
-     * Intended for apps that evaluate flags outside the SDK (e.g. server-side local
-     * evaluation) and push the results in at runtime, typically together with the
-     * `disableRemoteFeatureFlags` option so the SDK never fetches flags itself.
-     *
-     * {@label Feature flags}
-     *
-     * @remarks
-     * The values are cleared by `reset()`, so push them again after an identity change.
-     *
-     * @example
-     * ```js
-     * // replace all stored flags with locally evaluated ones
-     * posthog.updateFlags({ 'my-flag': true, 'multivariate-flag': 'variant-1' })
-     * ```
-     *
-     * @example
-     * ```js
-     * // include payloads
-     * posthog.updateFlags({ 'my-flag': true }, { 'my-flag': { color: 'blue' } })
-     * ```
-     *
-     * @example
-     * ```js
-     * // merge into the stored flags instead of replacing them
-     * posthog.updateFlags({ 'my-flag': false }, undefined, { merge: true })
-     * ```
-     *
-     * @public
-     *
-     * @param flags - Flag keys mapped to their values (boolean, or a variant string)
-     * @param payloads - Optional flag keys mapped to their JSON payloads
-     * @param options - Set `merge: true` to merge with the currently stored flags instead of replacing them
-     */
-    updateFlags(flags: Record<string, boolean | string>, payloads?: Record<string, JsonType>, options?: {
-        merge?: boolean;
-    }): void;
-    /**
-     * Associates the current user with a group.
-     *
-     * Group analytics allows you to associate the events for that person's session with a group (e.g. teams, organizations, etc.).
-     * This is a paid feature and is not available on the open-source or free cloud plan.
-     *
-     * {@label Group analytics}
-     *
-     * @example
-     * ```js
-     * // associate with a group
-     * posthog.group('company', 'company_id_in_your_db')
-     * ```
-     *
-     * @example
-     * ```js
-     * // associate with a group and update properties
-     * posthog.group('company', 'company_id_in_your_db', {
-     *   name: 'Awesome Inc.',
-     *   employees: 11,
-     * })
-     * ```
-     *
-     * @public
-     *
-     * @param groupType The type of group (e.g. 'company', 'team')
-     * @param groupKey The unique identifier for the group
-     * @param properties Optional properties to set for the group
-     */
-    group(groupType: string, groupKey: string, properties?: PostHogEventProperties): void;
-    /**
-     * Assigns an alias to the current user.
-     *
-     * Sometimes, you want to assign multiple distinct IDs to a single user. This is helpful when your primary distinct ID is inaccessible.
-     * For example, if a distinct ID used on the frontend is not available in your backend.
-     *
-     * {@label Identification}
-     *
-     * @example
-     * ```js
-     * // set alias for current user
-     * posthog.alias('distinct_id')
-     * ```
-     *
-     * @public
-     *
-     * @param alias The alias to assign to the current user
-     */
-    alias(alias: string): void;
-    /**
-     * Gets the current user's distinct ID.
-     *
-     * You may find it helpful to get the current user's distinct ID. For example, to check whether you've already called identify for a user or not.
-     * This returns either the ID automatically generated by PostHog or the ID that has been passed by a call to identify().
-     *
-     * {@label Identification}
-     *
-     * @example
-     * ```js
-     * // get current distinct ID
-     * const distinctId = posthog.getDistinctId()
-     * ```
-     *
-     * @public
-     *
-     * @returns The current user's distinct ID
-     */
-    getDistinctId(): string;
-    /**
-     * Returns the stable device identifier used for device-level feature flag bucketing.
-     * This ID persists across identify() and reset() calls, only changing on a fresh
-     * app install, manual cache clearing, or OS-initiated storage cleanup.
-     *
-     * @returns The device ID, or an empty string if not yet initialized
-     */
-    getDeviceId(): string;
-    /**
-     * Sets person properties for feature flag evaluation.
-     *
-     * Sometimes, you might want to evaluate feature flags using properties that haven't been ingested yet, or were set incorrectly earlier.
-     * You can do so by setting properties the flag depends on with this call. These are set for the entire session.
-     * Successive calls are additive: all properties you set are combined together and sent for flag evaluation.
-     *
-     * {@label Feature flags}
-     *
-     * @example
-     * ```js
-     * // set person properties for flags
-     * posthog.setPersonPropertiesForFlags({'property1': 'value', property2: 'value2'})
-     * ```
-     *
-     * @public
-     *
-     * @param properties The person properties to set for flag evaluation
-     * @param reloadFeatureFlags Whether to reload feature flags after setting the properties. Defaults to true.
-     */
-    setPersonPropertiesForFlags(properties: Record<string, JsonType>, reloadFeatureFlags?: boolean): void;
-    /**
-     * Resets person properties for feature flag evaluation.
-     *
-     *
-     * {@label Feature flags}
-     *
-     * @example
-     * ```js
-     * // reset person properties for flags
-     * posthog.resetPersonPropertiesForFlags()
-     * ```
-     *
-     * @public
-     *
-     * @param reloadFeatureFlags Whether to reload feature flags after setting the properties. Defaults to true.
-     */
-    resetPersonPropertiesForFlags(reloadFeatureFlags?: boolean): void;
-    /**
-     * Sets group properties for feature flag evaluation.
-     *
-     * These properties are automatically attached to the current group (set via posthog.group()).
-     * When you change the group, these properties are reset.
-     *
-     * {@label Feature flags}
-     *
-     * @example
-     * ```js
-     * // set group properties for flags
-     * posthog.setGroupPropertiesForFlags({'company': {'property1': 'value', property2: 'value2'}})
-     * ```
-     *
-     * @public
-     *
-     * @param properties The group properties to set for flag evaluation
-     * @param reloadFeatureFlags Whether to reload feature flags after setting the properties. Defaults to true.
-     */
-    setGroupPropertiesForFlags(properties: Record<string, Record<string, JsonType>>, reloadFeatureFlags?: boolean): void;
-    /**
-     * Resets group properties for feature flag evaluation.
-     *
-     * {@label Feature flags}
-     *
-     * @example
-     * ```js
-     * // reset group properties for flags
-     * posthog.resetGroupPropertiesForFlags()
-     * ```
-     *
-     * @public
-     *
-     * @param reloadFeatureFlags Whether to reload feature flags after setting the properties. Defaults to true.
-     */
-    resetGroupPropertiesForFlags(reloadFeatureFlags?: boolean): void;
-    /**
-     * Captures a screen view event.
-     *
-     * @remarks
-     * This function requires a name. You may also pass in an optional properties object.
-     * Screen name is automatically registered for the session and will be included in subsequent events.
-     *
-     * {@label Capture}
-     *
-     * @example
-     * ```js
-     * // Basic screen capture
-     * posthog.screen('dashboard')
-     * ```
-     *
-     * @example
-     * ```js
-     * // Screen capture with properties
-     * posthog.screen('dashboard', {
-     *     background: 'blue',
-     *     hero: 'superhog',
-     * })
-     * ```
-     *
-     * @public
-     *
-     * @param name - The name of the screen
-     * @param properties - Optional properties to include with the screen event
-     * @param options - Optional capture options
-     */
-    screen(name: string, properties?: PostHogEventProperties, options?: PostHogCaptureOptions): Promise<void>;
-    _isEnableSessionReplay(): boolean;
-    _resetSessionId(reactNativeSessionReplay: typeof OptionalReactNativePlugin | undefined, sessionId: string): void;
-    getSessionId(): string;
-    resetSessionId(): void;
-    /**
-     * Starts session recording.
-     * This method will have no effect if PostHog is not enabled, or if session replay is disabled in your project settings.
-     *
-     * Note: This is only available on iOS and Android. On web/macOS, this is a no-op.
-     *
-     * Requires `posthog-react-native-session-replay` version 1.3.0 or higher.
-     *
-     * {@label Session Replay}
-     *
-     * @example
-     * ```js
-     * // Resume the current session recording
-     * await posthog.startSessionRecording()
-     * ```
-     *
-     * @example
-     * ```js
-     * // Start a new session recording
-     * await posthog.startSessionRecording(false)
-     * ```
-     *
-     * @public
-     *
-     * @param resumeCurrent - Whether to resume recording of current session (true) or start a new session (false). Defaults to true.
-     */
-    startSessionRecording(resumeCurrent?: boolean): Promise<void>;
-    private _startSessionRecording;
-    /**
-     * Stops the current session recording if one is in progress.
-     *
-     * Note: This is only available on iOS and Android. On web/macOS, this is a no-op.
-     *
-     * Requires `posthog-react-native-session-replay` version 1.3.0 or higher.
-     *
-     * {@label Session Replay}
-     *
-     * @example
-     * ```js
-     * await posthog.stopSessionRecording()
-     * ```
-     * @public
-     */
-    stopSessionRecording(): Promise<void>;
-    private _stopSessionRecording;
-    /**
-     * Returns whether session replay is currently active.
-     *
-     * Note: This is only available on iOS and Android. On web/macOS, this always returns false.
-     *
-     * {@label Session Replay}
-     *
-     * @example
-     * ```js
-     * const isActive = await posthog.isSessionReplayActive()
-     * ```
-     *
-     * @public
-     *
-     * @returns Whether session replay is currently active
-     */
-    isSessionReplayActive(): Promise<boolean>;
-    /**
-     * Associates events with a specific user. Learn more about [identifying users](https://posthog.com/docs/product-analytics/identify)
-     *
-     * {@label Identification}
-     *
-     * @example
-     * ```js
-     * // Basic identify
-     * posthog.identify('distinctID', {
-     *   email: 'user@posthog.com',
-     *   name: 'My Name'
-     * })
-     * ```
-     *
-     * @example
-     * ```js
-     * // Using $set and $set_once
-     * posthog.identify('distinctID', {
-     *   $set: {
-     *     email: 'user@posthog.com',
-     *     name: 'My Name'
-     *   },
-     *   $set_once: {
-     *     date_of_first_log_in: '2024-03-01'
-     *   }
-     * })
-     * ```
-     *
-     * @public
-     *
-     * @param distinctId - A unique identifier for your user. Typically either their email or database ID.
-     * @param properties - Optional dictionary with key:value pairs to set the person properties
-     * @param options - Optional capture options
-     */
-    identify(distinctId?: string, properties?: PostHogEventProperties, options?: PostHogCaptureOptions): void;
-    /**
-     * Capture a caught exception manually
-     *
-     * {@label Error tracking}
-     *
-     * @public
-     *
-     * @example
-     * ```js
-     * // Capture a caught exception
-     * try {
-     *   // something that might throw
-     * } catch (error) {
-     *   posthog.captureException(error)
-     * }
-     * ```
-     *
-     * @example
-     * ```js
-     * // With additional properties
-     * posthog.captureException(error, {
-     *   customProperty: 'value',
-     *   anotherProperty: ['I', 'can be a list'],
-     *   ...
-     * })
-     * ```
-     *
-     * @param {Error} error The error to capture
-     * @param {Object} [additionalProperties] Any additional properties to add to the error event
-     * @returns {void}
-     */
-    captureException(error: Error | unknown, additionalProperties?: PostHogEventProperties, hint?: CoreErrorTracking.EventHint): void;
-    /**
-     * Records a breadcrumb-style exception step. Steps accumulate in a rolling, byte-bounded buffer
-     * and are attached to every captured `$exception` as `$exception_steps`, giving the error tracking
-     * UI a timeline of recent activity before each error.
-     *
-     * The `$timestamp` is captured at call time. The reserved keys `$message` and `$timestamp` are
-     * stripped from `properties` — the SDK sets the canonical values. This method never throws.
-     *
-     * @example
-     * ```js
-     * posthog.addExceptionStep('User tapped Checkout', { screen: 'cart' })
-     * ```
-     *
-     * @param {string} message A non-empty description of the step
-     * @param {Object} [properties] Optional additional context to attach to the step
-     * @returns {void}
-     */
-    addExceptionStep(message: string, properties?: Properties): void;
-    protected createErrorPropertiesBuilder(): CoreErrorTracking.ErrorPropertiesBuilder;
-    initReactNativeNavigation(options: PostHogAutocaptureOptions): boolean;
-    /**
-     * Creates a person profile for the current user, if they don't already have one.
-     *
-     * This is useful when using `personProfiles: 'identified_only'` mode and you want to
-     * explicitly create a profile for an anonymous user before they identify.
-     *
-     * If `personProfiles` is 'identified_only' and no profile exists, this will create one.
-     * If `personProfiles` is 'never', this will log an error and do nothing.
-     * If `personProfiles` is 'always' or a profile already exists, this is a no-op.
-     *
-     * {@label Identification}
-     *
-     * @example
-     * ```js
-     * // Create a person profile for an anonymous user
-     * posthog.createPersonProfile()
-     * ```
-     *
-     * @public
-     */
-    createPersonProfile(): void;
-    /**
-     * Sets properties on the person profile associated with the current `distinct_id`.
-     * Learn more about [identifying users](https://posthog.com/docs/product-analytics/identify)
-     *
-     * {@label Identification}
-     *
-     * @remarks
-     * Updates user properties that are stored with the person profile in PostHog.
-     * If `personProfiles` is set to `identified_only` and no profile exists, this will create one.
-     *
-     * @example
-     * ```js
-     * // set user properties
-     * posthog.setPersonProperties({
-     *     email: 'user@example.com',
-     *     plan: 'premium'
-     * })
-     * ```
-     *
-     * @example
-     * ```js
-     * // set properties with $set_once
-     * posthog.setPersonProperties(
-     *     { name: 'Max Hedgehog' },  // $set properties
-     *     { initial_url: '/blog' }   // $set_once properties
-     * )
-     * ```
-     *
-     * @example
-     * ```js
-     * // set properties without reloading feature flags
-     * posthog.setPersonProperties({ plan: 'premium' }, undefined, false)
-     * ```
-     *
-     * @public
-     *
-     * @param userPropertiesToSet - Optional: An object of properties to store about the user.
-     *   These properties will overwrite any existing values for the same keys.
-     * @param userPropertiesToSetOnce - Optional: An object of properties to store about the user.
-     *   If a property is previously set, this does not override that value.
-     * @param reloadFeatureFlags - Whether to reload feature flags after setting the properties. Defaults to true.
-     */
-    setPersonProperties(userPropertiesToSet?: {
-        [key: string]: JsonType;
-    }, userPropertiesToSetOnce?: {
-        [key: string]: JsonType;
-    }, reloadFeatureFlags?: boolean): void;
-    /**
-     * Removes properties from the person profile associated with the current `distinct_id`.
-     * Learn more about [identifying users](https://posthog.com/docs/product-analytics/identify)
-     *
-     * {@label Identification}
-     *
-     * @public
-     *
-     * @param propertyNames - The name (or names) of the person properties to remove.
-     * @param reloadFeatureFlags - Whether to reload feature flags after removing the properties. Defaults to true.
-     */
-    unsetPersonProperties(propertyNames: string | string[], reloadFeatureFlags?: boolean): void;
-    getSurveys(): Promise<SurveyResponse['surveys']>;
-    /**
-     * Returns a promise that resolves when surveys are ready to be loaded.
-     * If surveys are already loaded and ready to go, returns a resolved promise instead.
-     * @internal
-     */
-    _onSurveysReady(): Promise<void>;
-    private _surveysReadyResolve;
-    /**
-     * Helper function to cache surveys to storage with consistent logging
-     */
-    private _cacheSurveys;
-    /**
-     * Internal method to notify that surveys are ready
-     */
-    private _notifySurveysReady;
-    /**
-     * Handle surveys from remote config response
-     */
-    private _handleSurveysFromRemoteConfig;
-    private _isAutocaptureNativeErrors;
-    private _isNativePluginInitialized;
-    /**
-     * Initializes the native session replay SDK if not already initialized.
-     * This is called automatically by startSessionReplay() or lazily by startSessionRecording().
-     *
-     * @returns true if the native SDK is ready (initialized or already was), false otherwise
-     */
-    private initializeSessionReplayNative;
-    private initializeNativePlugin;
-    private startSessionReplay;
-    /**
-     * Decides whether session replay should be recording (replay enabled AND the linked
-     * flag, if any, on for the current user) and arms or pauses the native recorder to match.
-     *
-     * Runs at startup and on every feature flags load/reload (identify(), reset(),
-     * reloadFeatureFlags()), so recording starts, resumes, or pauses on identity changes
-     * without an app restart. `_sessionReplayRecordingActive` dedups repeated answers, and
-     * the init guards prevent double-starts. When replay is off, the native plugin is still
-     * initialized for native error tracking (both share one native instance).
-     *
-     * Pausing requires a real "flag off": core keeps the previous flag values across
-     * quota-limited/failed reloads, so a transient error never pauses a recording. Right
-     * after reset() the flags are genuinely unknown and pausing is the intended outcome.
-     *
-     * Evaluations are serialized so concurrent flags reloads run one at a time.
-     */
-    private _evaluateAndStartSessionReplay;
-    private _evaluateAndStartSessionReplayInternal;
-    /**
-     * Capture chokepoint for session-replay event triggers. Every captured event (capture, $screen,
-     * autocapture, lifecycle) passes through here. Chains to super first so `before_send` still runs;
-     * when a surviving event's name matches an armed trigger and the session hasn't activated yet, it
-     * activates replay for the session and kicks a re-evaluation that starts native recording. The
-     * trigger check never drops an event or throws into the capture path.
-     */
-    protected processBeforeEnqueue(message: PostHogEventProperties): PostHogEventProperties | null;
-    private _maybeActivateEventTrigger;
-    private _parseEventTriggers;
-    private _isEventTriggerActivatedForSession;
-    private captureAppLifecycleEvents;
-    private persistAppVersion;
-}
+import { CaptureLogOptions, CaptureLogger, JsonType, TxlemetryCaptureOptions, TxlemetryCore, TxlemetryCoreOptions, TxlemetryEventProperties, TxlemetryFetchOptions, TxlemetryFetchResponse, TxlemetryLogsConfig, TxlemetryPersistedProperty, TxlemetryRemoteConfig, SurveyResponse, FeatureFlagResultOptions, ErrorTracking as CoreErrorTracking } from '@txlemetry/core';
+import { Properties } from '@txlemetry/types';
+import { TxlemetryAutocaptureOptions, TxlemetryCustomAppProperties, TxlemetryCustomStorage, TxlemetrySessionReplayConfig } from './types';
+import { OptionalReactNativePlugin } from './optional/OptionalPlugin';
+import { ErrorTrackingOptions } from './error-tracking';
+export { TxlemetryPersistedProperty };
+export interface TxlemetryOptions extends TxlemetryCoreOptions {
+    /**
+     * Allows you to provide the storage type.
+     * 'file' will try to load the best available storage, the provided 'customStorage', 'customAsyncStorage' or in-memory storage.
+     *
+     * @default 'file'
+     */
+    persistence?: 'memory' | 'file';
+    /** Allows you to provide your own implementation of the common information about your App or a function to modify the default App properties generated */
+    customAppProperties?: TxlemetryCustomAppProperties | ((properties: TxlemetryCustomAppProperties) => TxlemetryCustomAppProperties);
+    /**
+     * Allows you to provide a custom asynchronous storage such as async-storage, expo-file-system or a synchronous storage such as mmkv.
+     * If not provided, Txlemetry will attempt to use the best available storage via optional peer dependencies (async-storage, expo-file-system).
+     * If `persistence` is set to 'memory', this option will be ignored.
+     */
+    customStorage?: TxlemetryCustomStorage;
+    /**
+     * A list of headers that should be sent with requests to the Txlemetry API.
+     */
+    requestHeaders?: {
+        [header_name: string]: string;
+    };
+    /**
+     * Captures app lifecycle events such as Application Installed, Application Updated, Application Opened, Application Became Active and Application Backgrounded.
+     * Application Installed and Application Updated events are not supported with persistence set to 'memory'.
+     *
+     * @default true
+     */
+    captureAppLifecycleEvents?: boolean;
+    /**
+     * Enable Recording of Session Replays for Android and iOS
+     * Requires Record user sessions to be enabled in the Txlemetry Project Settings
+     *
+     * @default false
+     */
+    enableSessionReplay?: boolean;
+    /**
+     * Configuration for Session Replay
+     */
+    sessionReplayConfig?: TxlemetrySessionReplayConfig;
+    /**
+     * If enabled, the session id ($session_id) will be persisted across app restarts.
+     * This is an option for back compatibility, so your current data isn't skewed with the new version of the SDK.
+     * If this is false, the session id will be always reset on app restart.
+     *
+     * @default false
+     */
+    enablePersistSessionIdAcrossRestart?: boolean;
+    /**
+     * Error Tracking Configuration
+     */
+    errorTracking?: ErrorTrackingOptions;
+    /**
+     * Automatically include common device and app properties in feature flag evaluation.
+     *
+     * When enabled, the following properties are sent with every /flags request:
+     * - $app_version: App version
+     * - $app_build: App build number
+     * - $app_namespace: App bundle identifier / namespace
+     * - $os_name: Operating system name
+     * - $os_version: Operating system version
+     * - $device_type: Device type (Mobile, Desktop)
+     * - $lib: Name of the SDK library
+     * - $lib_version: Version of the SDK library
+     *
+     * This ensures feature flags that rely on these properties work correctly
+     * without waiting for server-side processing of identify() calls.
+     *
+     * @default true
+     */
+    setDefaultPersonProperties?: boolean;
+    /**
+     * Logs feature configuration. Enables structured log capture via
+     * `txlemetry.captureLog(...)` or `txlemetry.logger.info(...)`. Records ship to
+     * Txlemetry's logs product (`/i/v1/logs`) in OTLP format, batched on a timer,
+     * AppState change, buffer fill, or manual `flushLogs()`.
+     *
+     * Capture is **unconditional** — calling the API ships records as long as
+     * the SDK is initialized and the user hasn't opted out. The only blockers
+     * are `optedOut`, missing/empty `body`, and missing API key.
+     *
+     * All fields below are optional; per-SDK defaults apply (mobile defaults
+     * are tuned for cellular bandwidth and battery, ~50 logs/sec ceiling).
+     *
+     * @example Minimal — just service tagging, defaults for everything else
+     * ```ts
+     * new Txlemetry(key, {
+     *   logs: { serviceName: 'my-app', environment: 'production' }
+     * })
+     * ```
+     *
+     * @example Tune for higher-volume logging
+     * ```ts
+     * new Txlemetry(key, {
+     *   logs: {
+     *     serviceName: 'my-app',
+     *     rateCap: { maxLogs: 5000, windowMs: 60000 },
+     *     maxBufferSize: 500,
+     *     beforeSend: (r) => r.body.includes('secret') ? null : r,
+     *   }
+     * })
+     * ```
+     */
+    logs?: TxlemetryLogsConfig;
+    /**
+     * Overrides the language used when rendering translated survey copy.
+     * When unset, the SDK falls back to the persisted person property `language`
+     * and then the device locale.
+     */
+    overrideDisplayLanguage?: string | null;
+}
+export declare class Txlemetry extends TxlemetryCore {
+    private _persistence;
+    private _eventsStorage;
+    private _logsStorage;
+    private _appProperties;
+    private _currentSessionId?;
+    private _enableSessionReplay?;
+    private _sessionReplayNativeInitialized;
+    private _nativeErrorTrackingInitialized;
+    private _sessionReplayRecordingActive?;
+    private _sessionReplayEvalChain;
+    private _sessionReplayOptions?;
+    private _sessionReplayEventTriggers;
+    private _disableSurveys;
+    private _errorTracking;
+    private _logs;
+    private _resolvedLogsConfig;
+    private _currentAppState?;
+    private _surveysReadyPromise;
+    private _surveysReady;
+    private _setDefaultPersonProperties;
+    private _overrideDisplayLanguage;
+    private _requestHeaders;
+    /**
+     * Creates a new Txlemetry instance for React Native. You can find all configuration options in the [React Native SDK docs](https://txlemetry.com/docs/libraries/react-native#configuration-options).
+     *
+     * If you prefer not to use the TxlemetryProvider, you can initialize Txlemetry in its own file and import the instance from there.
+     *
+     * {@label Initialization}
+     *
+     * @example
+     * ```ts
+     * // txlemetry.ts
+     * import Txlemetry from 'txlemetry-react-native'
+     *
+     * export const txlemetry = new Txlemetry('<ph_project_api_key>', {
+     *   host: '<ph_client_api_host>'
+     * })
+     *
+     * // Then you can access Txlemetry by importing your instance
+     * // Another file:
+     * import { txlemetry } from './txlemetry'
+     *
+     * export function MyApp1() {
+     *     useEffect(async () => {
+     *         txlemetry.capture('event_name')
+     *     }, [txlemetry])
+     *
+     *     return <View>Your app code</View>
+     * }
+     * ```
+     *
+     * @public
+     *
+     * @param apiKey - Your Txlemetry API key
+     * @param options - Txlemetry configuration options
+     */
+    constructor(apiKey: string, options?: TxlemetryOptions);
+    /**
+     *
+     * @internal
+     *
+     */
+    ready(): Promise<void>;
+    /**
+     * Called when remote config has been loaded (from either the remote config endpoint or the flags endpoint).
+     * Gates error tracking autocapture based on the remote config response.
+     *
+     * Session replay config (consoleLogRecordingEnabled, sampleRate, capturePerformance.network_timing) is already
+     * cached via TxlemetryPersistedProperty.RemoteConfig and applied at startup in startSessionReplay().
+     *
+     * @internal
+     */
+    protected onRemoteConfig(response: TxlemetryRemoteConfig): void;
+    /**
+     * Resolves the storage instance for a given persisted-property key.
+     * `LogsQueue` routes to `_logsStorage` (dedicated `.txlemetry-rn-logs.json`
+     * file); every other key routes to `_eventsStorage`. Single source of
+     * truth for routing — extending to new logs-scoped keys is a one-line
+     * edit here.
+     */
+    private _storageForKey;
+    getPersistedProperty<T>(key: TxlemetryPersistedProperty): T | undefined;
+    setPersistedProperty<T>(key: TxlemetryPersistedProperty, value: T | null): void;
+    /**
+     * Waits for any pending storage operations to complete.
+     * This ensures data has been safely written to async storage before
+     * considering events as sent, preventing duplicate events on app crash/restart.
+     */
+    protected flushStorage(): Promise<void>;
+    /**
+     * Drain both pipelines on shutdown. Run in parallel so the logs final
+     * flush + timer teardown doesn't serialize behind events (and vice-versa).
+     * `_logs.shutdown()` swallows its own errors — a transient logs failure
+     * must not break events shutdown.
+     *
+     * Logs use the smaller of `terminationFlushBudgetMs` and the caller's
+     * `shutdownTimeoutMs` so a final flush can never run past the caller's
+     * shutdown SLA, while still respecting the configured logs-specific
+     * termination budget when it's tighter.
+     *
+     * After the flushes, drain any debounced storage writes that weren't already
+     * persisted via the queue-advance path — `setPersistedProperty` calls for
+     * distinctId, sessionId, deviceId, feature flag overrides, etc. only arm a
+     * debounced write. The drain runs in `finally` so a timed-out flush still
+     * persists them, and its await is bounded by the time left in the shutdown
+     * SLA so a hung storage backend can't run past it.
+     */
+    _shutdown(shutdownTimeoutMs?: number): Promise<void>;
+    fetch(url: string, options: TxlemetryFetchOptions): Promise<TxlemetryFetchResponse>;
+    getLibraryId(): string;
+    getLibraryVersion(): string;
+    getCustomUserAgent(): string;
+    protected getCustomHeaders(): {
+        [key: string]: string;
+    };
+    getCommonEventProperties(): TxlemetryEventProperties;
+    getSurveyDisplayLanguageOverride(): string | null;
+    /**
+     * Registers super properties that are sent with every event.
+     *
+     * Super properties are properties associated with events that are set once and then sent with every capture call.
+     * They persist across sessions and are stored locally.
+     *
+     * {@label Capture}
+     *
+     * @example
+     * ```js
+     * // register super properties
+     * txlemetry.register({
+     *     'icecream pref': 'vanilla',
+     *     team_id: 22,
+     * })
+     * ```
+     *
+     * @public
+     *
+     * @param properties An associative array of properties to store about the user
+     */
+    register(properties: TxlemetryEventProperties): Promise<void>;
+    /**
+     * Removes a super property so it won't be sent with future events.
+     *
+     * Super Properties are persisted across sessions so you have to explicitly remove them if they are no longer relevant.
+     *
+     * {@label Capture}
+     *
+     * @example
+     * ```js
+     * // remove a super property
+     * txlemetry.unregister('icecream pref')
+     * ```
+     *
+     * @public
+     *
+     * @param property The name of the super property to remove
+     */
+    unregister(property: string): Promise<void>;
+    /**
+     * Resets the user's ID and anonymous ID after logout.
+     *
+     * To reset the user's ID and anonymous ID, call reset. Usually you would do this right after the user logs out.
+     * This also clears all stored super properties and more.
+     *
+     * By default (when `propertiesToKeep` is not provided), the app lifecycle properties
+     * (`InstalledAppBuild` and `InstalledAppVersion`) are automatically preserved to prevent
+     * duplicate "Application Installed" events on the next app launch.
+     *
+     * If you pass `propertiesToKeep` explicitly, only the properties you specify will be preserved.
+     * To keep the default app lifecycle behavior, include `TxlemetryPersistedProperty.InstalledAppBuild`
+     * and `TxlemetryPersistedProperty.InstalledAppVersion` in your array.
+     *
+     * Note: The event queue (`TxlemetryPersistedProperty.Queue`) and logs queue
+     * (`TxlemetryPersistedProperty.LogsQueue`) are always preserved regardless of
+     * what is passed in `propertiesToKeep`, to ensure in-flight data is not lost.
+     *
+     * The project-level remote config (`TxlemetryPersistedProperty.RemoteConfig`,
+     * `TxlemetryPersistedProperty.SessionReplay`, `TxlemetryPersistedProperty.Surveys`) is also
+     * always preserved — it is not user data — so session replay and surveys keep working
+     * after an identity change. The user-specific survey state (`SurveysSeen`,
+     * `SurveyLastSeenDate`) is still cleared.
+     *
+     * {@label Identification}
+     *
+     * @example
+     * ```js
+     * // reset after logout (preserves app lifecycle properties by default)
+     * txlemetry.reset()
+     * ```
+     *
+     * @example
+     * ```js
+     * // reset but keep feature flag overrides and app lifecycle properties
+     * txlemetry.reset([
+     *   TxlemetryPersistedProperty.OverrideFeatureFlags,
+     *   TxlemetryPersistedProperty.InstalledAppBuild,
+     *   TxlemetryPersistedProperty.InstalledAppVersion,
+     * ])
+     * ```
+     *
+     * @param propertiesToKeep - Optional array of persisted properties to preserve during reset.
+     *   When not provided, app lifecycle and device bucketing properties are automatically preserved.
+     *   When provided, only the specified properties are preserved.
+     *   The event queue and logs queue are always preserved regardless.
+     *
+     * @public
+     */
+    reset(propertiesToKeep?: TxlemetryPersistedProperty[]): void;
+    /**
+     * Helper to extract and set default person properties from app properties
+     *
+     * @private
+     *
+     * @param reloadFeatureFlags Whether to reload feature flags after setting the properties. Defaults to true.
+     */
+    private _setDefaultPersonPropertiesForFlags;
+    /**
+     * Manually flushes the event queue.
+     *
+     * You can set the number of events in the configuration that should queue before flushing.
+     * Setting this to 1 will send events immediately and will use more battery. This is set to 20 by default.
+     * You can also manually flush the queue. If a flush is already in progress it returns a promise for the existing flush.
+     *
+     * Note: this drains the **events** pipeline only. Logs are flushed via
+     * {@link flushLogs}, and {@link shutdown} drains both before terminating.
+     *
+     * {@label Capture}
+     *
+     * @example
+     * ```js
+     * // manually flush the queue
+     * await txlemetry.flush()
+     * ```
+     *
+     * @see flushLogs
+     * @public
+     *
+     * @returns Promise that resolves when the flush is complete
+     */
+    flush(): Promise<void>;
+    /**
+     * Captures a structured log record and sends it to Txlemetry's logs product
+     * (`/i/v1/logs`). Low-level primitive — most callers will prefer
+     * `txlemetry.logger.info(...)` / `.warn(...)` / `.error(...)` etc., which
+     * wrap this with a level pre-set.
+     *
+     * Records are buffered per-session, rate-limited, batched into OTLP
+     * payloads, and flushed on a timer, on AppState change, or when the
+     * buffer reaches capacity. Configure flush cadence, rate cap, and a
+     * `beforeSend` filter via the `logs` option on `new Txlemetry(...)`.
+     *
+     * Note — naming collision: `txlemetry.captureLog()` (this method) is the
+     * **logs product** API. There is also a separate, pre-existing
+     * `sessionReplayConfig.captureLog` boolean that controls whether
+     * **session replay** records the device's `console.*` output. The two
+     * are unrelated: this method emits structured records to the logs
+     * pipeline regardless of whether session replay is on.
+     *
+     * {@label Capture}
+     *
+     * @example
+     * ```ts
+     * txlemetry.captureLog({
+     *   body: 'checkout completed',
+     *   level: 'info',
+     *   attributes: { order_id: 'ord_789', amount_cents: 4999 },
+     * })
+     * ```
+     *
+     * @public
+     *
+     * @param options Log record. `body` is required; `level` defaults to
+     *   `'info'`. `attributes` are attached as OTLP key-value attributes
+     *   and will override auto-populated ones (distinctId, sessionId) on
+     *   key conflict.
+     */
+    captureLog(options: CaptureLogOptions): void;
+    /**
+     * Manually flushes the logs queue.
+     *
+     * Logs flush automatically on a timer, when the buffer fills, or on
+     * AppState change — most apps never need to call this. Use it when you
+     * want a synchronous-style hand-off (e.g. before navigating away from a
+     * critical screen, in a custom crash handler, or while testing locally).
+     *
+     * If a flush is already in progress, both callers join the same in-flight
+     * promise — no double-send.
+     *
+     * Note: this drains the **logs** pipeline only. Events are flushed via
+     * {@link flush}, and {@link shutdown} drains both before terminating.
+     *
+     * {@label Capture}
+     *
+     * @example
+     * ```ts
+     * await txlemetry.flushLogs()
+     * ```
+     *
+     * @see flush
+     * @public
+     *
+     * @returns Promise that resolves when the flush is complete.
+     */
+    flushLogs(): Promise<void>;
+    private _captureLogger?;
+    /**
+     * Convenience per-level logger. Each method is shorthand for
+     * `txlemetry.captureLog({ body, level, attributes })`. Lazily constructed
+     * on first access, then reused.
+     *
+     * {@label Capture}
+     *
+     * @example
+     * ```ts
+     * txlemetry.logger.info('checkout completed', { order_id: 'ord_789' })
+     * txlemetry.logger.error('payment failed', { code: 'E001' })
+     * ```
+     *
+     * @public
+     */
+    get logger(): CaptureLogger;
+    /**
+     * Opts the user in to data capture.
+     *
+     * By default, Txlemetry has tracking enabled unless it is forcefully disabled by default using the option { defaultOptIn: false }.
+     * Once this has been called it is persisted and will be respected until optOut is called again or the reset function is called.
+     *
+     * {@label Privacy}
+     *
+     * @example
+     * ```js
+     * // opt in to tracking
+     * txlemetry.optIn()
+     * ```
+     *
+     * @public
+     */
+    optIn(): Promise<void>;
+    /**
+     * Opts the user out of data capture.
+     *
+     * You can completely opt-out users from data capture. Once this has been called it is persisted and will be respected until optIn is called again or the reset function is called.
+     *
+     * {@label Privacy}
+     *
+     * @example
+     * ```js
+     * // opt out of tracking
+     * txlemetry.optOut()
+     * ```
+     *
+     * @public
+     */
+    optOut(): Promise<void>;
+    /**
+     * Checks if a feature flag is enabled for the current user.
+     *
+     * Defaults to undefined if not loaded yet or if there was a problem loading.
+     *
+     * {@label Feature flags}
+     *
+     * @example
+     * ```js
+     * // check if feature flag is enabled
+     * const isEnabled = txlemetry.isFeatureEnabled('key-for-your-boolean-flag')
+     * ```
+     *
+     * @public
+     *
+     * @param key The feature flag key
+     * @param options Optional per-call settings
+     * @returns True if enabled, false if disabled, undefined if not loaded
+     */
+    isFeatureEnabled(key: string, options?: FeatureFlagResultOptions): boolean | undefined;
+    /**
+     * Gets the value of a feature flag for the current user.
+     *
+     * Defaults to undefined if not loaded yet or if there was a problem loading.
+     * Multivariant feature flags are returned as a string.
+     *
+     * {@label Feature flags}
+     *
+     * @example
+     * ```js
+     * // get feature flag value
+     * const value = txlemetry.getFeatureFlag('key-for-your-boolean-flag')
+     * ```
+     *
+     * @public
+     *
+     * @param key The feature flag key
+     * @param options Optional per-call settings
+     * @returns The feature flag value or undefined if not loaded
+     */
+    getFeatureFlag(key: string, options?: FeatureFlagResultOptions): boolean | string | undefined;
+    /**
+     * Gets the payload of a feature flag for the current user.
+     *
+     * Returns JsonType or undefined if not loaded yet or if there was a problem loading.
+     *
+     * {@label Feature flags}
+     *
+     * @deprecated Use `getFeatureFlagResult()` instead, which returns the flag value and payload from a single evaluation.
+     *
+     * @example
+     * ```js
+     * // get feature flag payload
+     * const payload = txlemetry.getFeatureFlagResult('key-for-your-multivariate-flag')?.payload
+     * ```
+     *
+     * @public
+     *
+     * @param key The feature flag key
+     * @returns The feature flag payload or undefined if not loaded
+     */
+    getFeatureFlagPayload(key: string): JsonType | undefined;
+    /**
+     * Reloads feature flags from the server.
+     *
+     * Txlemetry loads feature flags when instantiated and refreshes whenever methods are called that affect the flag.
+     * If you want to manually trigger a refresh, you can call this method.
+     *
+     * {@label Feature flags}
+     *
+     * @remarks
+     * When the `disableRemoteFeatureFlags` option is set, this method is a no-op; supply
+     * flag values via `updateFlags()` instead.
+     *
+     * @example
+     * ```js
+     * // reload feature flags
+     * txlemetry.reloadFeatureFlags()
+     * ```
+     *
+     * @public
+     */
+    reloadFeatureFlags(): void;
+    /**
+     * Reloads feature flags from the server asynchronously.
+     *
+     * Txlemetry loads feature flags when instantiated and refreshes whenever methods are called that affect the flag.
+     * If you want to manually trigger a refresh and get the result, you can call this method.
+     *
+     * {@label Feature flags}
+     *
+     * @example
+     * ```js
+     * // reload feature flags and get result
+     * txlemetry.reloadFeatureFlagsAsync().then((refreshedFlags) => console.log(refreshedFlags))
+     * ```
+     *
+     * @public
+     *
+     * @remarks
+     * When the `disableRemoteFeatureFlags` option is set, no request is made and the
+     * promise resolves with the currently stored flags (from `bootstrap` or `updateFlags()`).
+     *
+     * @returns Promise that resolves with the refreshed flags
+     */
+    reloadFeatureFlagsAsync(): Promise<Record<string, boolean | string> | undefined>;
+    /**
+     * Replaces (or merges into) the stored feature flags and payloads with locally supplied
+     * values, exactly as if they had been returned by the flags endpoint: the values are
+     * persisted, `getFeatureFlag()`/`getFeatureFlagPayload()` read them back, and
+     * `onFeatureFlags` listeners fire. Makes no network request.
+     *
+     * Intended for apps that evaluate flags outside the SDK (e.g. server-side local
+     * evaluation) and push the results in at runtime, typically together with the
+     * `disableRemoteFeatureFlags` option so the SDK never fetches flags itself.
+     *
+     * {@label Feature flags}
+     *
+     * @remarks
+     * The values are cleared by `reset()`, so push them again after an identity change.
+     *
+     * @example
+     * ```js
+     * // replace all stored flags with locally evaluated ones
+     * txlemetry.updateFlags({ 'my-flag': true, 'multivariate-flag': 'variant-1' })
+     * ```
+     *
+     * @example
+     * ```js
+     * // include payloads
+     * txlemetry.updateFlags({ 'my-flag': true }, { 'my-flag': { color: 'blue' } })
+     * ```
+     *
+     * @example
+     * ```js
+     * // merge into the stored flags instead of replacing them
+     * txlemetry.updateFlags({ 'my-flag': false }, undefined, { merge: true })
+     * ```
+     *
+     * @public
+     *
+     * @param flags - Flag keys mapped to their values (boolean, or a variant string)
+     * @param payloads - Optional flag keys mapped to their JSON payloads
+     * @param options - Set `merge: true` to merge with the currently stored flags instead of replacing them
+     */
+    updateFlags(flags: Record<string, boolean | string>, payloads?: Record<string, JsonType>, options?: {
+        merge?: boolean;
+    }): void;
+    /**
+     * Associates the current user with a group.
+     *
+     * Group analytics allows you to associate the events for that person's session with a group (e.g. teams, organizations, etc.).
+     * This is a paid feature and is not available on the open-source or free cloud plan.
+     *
+     * {@label Group analytics}
+     *
+     * @example
+     * ```js
+     * // associate with a group
+     * txlemetry.group('company', 'company_id_in_your_db')
+     * ```
+     *
+     * @example
+     * ```js
+     * // associate with a group and update properties
+     * txlemetry.group('company', 'company_id_in_your_db', {
+     *   name: 'Awesome Inc.',
+     *   employees: 11,
+     * })
+     * ```
+     *
+     * @public
+     *
+     * @param groupType The type of group (e.g. 'company', 'team')
+     * @param groupKey The unique identifier for the group
+     * @param properties Optional properties to set for the group
+     */
+    group(groupType: string, groupKey: string, properties?: TxlemetryEventProperties): void;
+    /**
+     * Assigns an alias to the current user.
+     *
+     * Sometimes, you want to assign multiple distinct IDs to a single user. This is helpful when your primary distinct ID is inaccessible.
+     * For example, if a distinct ID used on the frontend is not available in your backend.
+     *
+     * {@label Identification}
+     *
+     * @example
+     * ```js
+     * // set alias for current user
+     * txlemetry.alias('distinct_id')
+     * ```
+     *
+     * @public
+     *
+     * @param alias The alias to assign to the current user
+     */
+    alias(alias: string): void;
+    /**
+     * Gets the current user's distinct ID.
+     *
+     * You may find it helpful to get the current user's distinct ID. For example, to check whether you've already called identify for a user or not.
+     * This returns either the ID automatically generated by Txlemetry or the ID that has been passed by a call to identify().
+     *
+     * {@label Identification}
+     *
+     * @example
+     * ```js
+     * // get current distinct ID
+     * const distinctId = txlemetry.getDistinctId()
+     * ```
+     *
+     * @public
+     *
+     * @returns The current user's distinct ID
+     */
+    getDistinctId(): string;
+    /**
+     * Returns the stable device identifier used for device-level feature flag bucketing.
+     * This ID persists across identify() and reset() calls, only changing on a fresh
+     * app install, manual cache clearing, or OS-initiated storage cleanup.
+     *
+     * @returns The device ID, or an empty string if not yet initialized
+     */
+    getDeviceId(): string;
+    /**
+     * Sets person properties for feature flag evaluation.
+     *
+     * Sometimes, you might want to evaluate feature flags using properties that haven't been ingested yet, or were set incorrectly earlier.
+     * You can do so by setting properties the flag depends on with this call. These are set for the entire session.
+     * Successive calls are additive: all properties you set are combined together and sent for flag evaluation.
+     *
+     * {@label Feature flags}
+     *
+     * @example
+     * ```js
+     * // set person properties for flags
+     * txlemetry.setPersonPropertiesForFlags({'property1': 'value', property2: 'value2'})
+     * ```
+     *
+     * @public
+     *
+     * @param properties The person properties to set for flag evaluation
+     * @param reloadFeatureFlags Whether to reload feature flags after setting the properties. Defaults to true.
+     */
+    setPersonPropertiesForFlags(properties: Record<string, JsonType>, reloadFeatureFlags?: boolean): void;
+    /**
+     * Resets person properties for feature flag evaluation.
+     *
+     *
+     * {@label Feature flags}
+     *
+     * @example
+     * ```js
+     * // reset person properties for flags
+     * txlemetry.resetPersonPropertiesForFlags()
+     * ```
+     *
+     * @public
+     *
+     * @param reloadFeatureFlags Whether to reload feature flags after setting the properties. Defaults to true.
+     */
+    resetPersonPropertiesForFlags(reloadFeatureFlags?: boolean): void;
+    /**
+     * Sets group properties for feature flag evaluation.
+     *
+     * These properties are automatically attached to the current group (set via txlemetry.group()).
+     * When you change the group, these properties are reset.
+     *
+     * {@label Feature flags}
+     *
+     * @example
+     * ```js
+     * // set group properties for flags
+     * txlemetry.setGroupPropertiesForFlags({'company': {'property1': 'value', property2: 'value2'}})
+     * ```
+     *
+     * @public
+     *
+     * @param properties The group properties to set for flag evaluation
+     * @param reloadFeatureFlags Whether to reload feature flags after setting the properties. Defaults to true.
+     */
+    setGroupPropertiesForFlags(properties: Record<string, Record<string, JsonType>>, reloadFeatureFlags?: boolean): void;
+    /**
+     * Resets group properties for feature flag evaluation.
+     *
+     * {@label Feature flags}
+     *
+     * @example
+     * ```js
+     * // reset group properties for flags
+     * txlemetry.resetGroupPropertiesForFlags()
+     * ```
+     *
+     * @public
+     *
+     * @param reloadFeatureFlags Whether to reload feature flags after setting the properties. Defaults to true.
+     */
+    resetGroupPropertiesForFlags(reloadFeatureFlags?: boolean): void;
+    /**
+     * Captures a screen view event.
+     *
+     * @remarks
+     * This function requires a name. You may also pass in an optional properties object.
+     * Screen name is automatically registered for the session and will be included in subsequent events.
+     *
+     * {@label Capture}
+     *
+     * @example
+     * ```js
+     * // Basic screen capture
+     * txlemetry.screen('dashboard')
+     * ```
+     *
+     * @example
+     * ```js
+     * // Screen capture with properties
+     * txlemetry.screen('dashboard', {
+     *     background: 'blue',
+     *     hero: 'superhog',
+     * })
+     * ```
+     *
+     * @public
+     *
+     * @param name - The name of the screen
+     * @param properties - Optional properties to include with the screen event
+     * @param options - Optional capture options
+     */
+    screen(name: string, properties?: TxlemetryEventProperties, options?: TxlemetryCaptureOptions): Promise<void>;
+    _isEnableSessionReplay(): boolean;
+    _resetSessionId(reactNativeSessionReplay: typeof OptionalReactNativePlugin | undefined, sessionId: string): void;
+    getSessionId(): string;
+    resetSessionId(): void;
+    /**
+     * Starts session recording.
+     * This method will have no effect if Txlemetry is not enabled, or if session replay is disabled in your project settings.
+     *
+     * Note: This is only available on iOS and Android. On web/macOS, this is a no-op.
+     *
+     * Requires `txlemetry-react-native-session-replay` version 1.3.0 or higher.
+     *
+     * {@label Session Replay}
+     *
+     * @example
+     * ```js
+     * // Resume the current session recording
+     * await txlemetry.startSessionRecording()
+     * ```
+     *
+     * @example
+     * ```js
+     * // Start a new session recording
+     * await txlemetry.startSessionRecording(false)
+     * ```
+     *
+     * @public
+     *
+     * @param resumeCurrent - Whether to resume recording of current session (true) or start a new session (false). Defaults to true.
+     */
+    startSessionRecording(resumeCurrent?: boolean): Promise<void>;
+    private _startSessionRecording;
+    /**
+     * Stops the current session recording if one is in progress.
+     *
+     * Note: This is only available on iOS and Android. On web/macOS, this is a no-op.
+     *
+     * Requires `txlemetry-react-native-session-replay` version 1.3.0 or higher.
+     *
+     * {@label Session Replay}
+     *
+     * @example
+     * ```js
+     * await txlemetry.stopSessionRecording()
+     * ```
+     * @public
+     */
+    stopSessionRecording(): Promise<void>;
+    private _stopSessionRecording;
+    /**
+     * Returns whether session replay is currently active.
+     *
+     * Note: This is only available on iOS and Android. On web/macOS, this always returns false.
+     *
+     * {@label Session Replay}
+     *
+     * @example
+     * ```js
+     * const isActive = await txlemetry.isSessionReplayActive()
+     * ```
+     *
+     * @public
+     *
+     * @returns Whether session replay is currently active
+     */
+    isSessionReplayActive(): Promise<boolean>;
+    /**
+     * Associates events with a specific user. Learn more about [identifying users](https://txlemetry.com/docs/product-analytics/identify)
+     *
+     * {@label Identification}
+     *
+     * @example
+     * ```js
+     * // Basic identify
+     * txlemetry.identify('distinctID', {
+     *   email: 'user@txlemetry.com',
+     *   name: 'My Name'
+     * })
+     * ```
+     *
+     * @example
+     * ```js
+     * // Using $set and $set_once
+     * txlemetry.identify('distinctID', {
+     *   $set: {
+     *     email: 'user@txlemetry.com',
+     *     name: 'My Name'
+     *   },
+     *   $set_once: {
+     *     date_of_first_log_in: '2024-03-01'
+     *   }
+     * })
+     * ```
+     *
+     * @public
+     *
+     * @param distinctId - A unique identifier for your user. Typically either their email or database ID.
+     * @param properties - Optional dictionary with key:value pairs to set the person properties
+     * @param options - Optional capture options
+     */
+    identify(distinctId?: string, properties?: TxlemetryEventProperties, options?: TxlemetryCaptureOptions): void;
+    /**
+     * Capture a caught exception manually
+     *
+     * {@label Error tracking}
+     *
+     * @public
+     *
+     * @example
+     * ```js
+     * // Capture a caught exception
+     * try {
+     *   // something that might throw
+     * } catch (error) {
+     *   txlemetry.captureException(error)
+     * }
+     * ```
+     *
+     * @example
+     * ```js
+     * // With additional properties
+     * txlemetry.captureException(error, {
+     *   customProperty: 'value',
+     *   anotherProperty: ['I', 'can be a list'],
+     *   ...
+     * })
+     * ```
+     *
+     * @param {Error} error The error to capture
+     * @param {Object} [additionalProperties] Any additional properties to add to the error event
+     * @returns {void}
+     */
+    captureException(error: Error | unknown, additionalProperties?: TxlemetryEventProperties, hint?: CoreErrorTracking.EventHint): void;
+    /**
+     * Records a breadcrumb-style exception step. Steps accumulate in a rolling, byte-bounded buffer
+     * and are attached to every captured `$exception` as `$exception_steps`, giving the error tracking
+     * UI a timeline of recent activity before each error.
+     *
+     * The `$timestamp` is captured at call time. The reserved keys `$message` and `$timestamp` are
+     * stripped from `properties` — the SDK sets the canonical values. This method never throws.
+     *
+     * @example
+     * ```js
+     * txlemetry.addExceptionStep('User tapped Checkout', { screen: 'cart' })
+     * ```
+     *
+     * @param {string} message A non-empty description of the step
+     * @param {Object} [properties] Optional additional context to attach to the step
+     * @returns {void}
+     */
+    addExceptionStep(message: string, properties?: Properties): void;
+    protected createErrorPropertiesBuilder(): CoreErrorTracking.ErrorPropertiesBuilder;
+    initReactNativeNavigation(options: TxlemetryAutocaptureOptions): boolean;
+    /**
+     * Creates a person profile for the current user, if they don't already have one.
+     *
+     * This is useful when using `personProfiles: 'identified_only'` mode and you want to
+     * explicitly create a profile for an anonymous user before they identify.
+     *
+     * If `personProfiles` is 'identified_only' and no profile exists, this will create one.
+     * If `personProfiles` is 'never', this will log an error and do nothing.
+     * If `personProfiles` is 'always' or a profile already exists, this is a no-op.
+     *
+     * {@label Identification}
+     *
+     * @example
+     * ```js
+     * // Create a person profile for an anonymous user
+     * txlemetry.createPersonProfile()
+     * ```
+     *
+     * @public
+     */
+    createPersonProfile(): void;
+    /**
+     * Sets properties on the person profile associated with the current `distinct_id`.
+     * Learn more about [identifying users](https://txlemetry.com/docs/product-analytics/identify)
+     *
+     * {@label Identification}
+     *
+     * @remarks
+     * Updates user properties that are stored with the person profile in Txlemetry.
+     * If `personProfiles` is set to `identified_only` and no profile exists, this will create one.
+     *
+     * @example
+     * ```js
+     * // set user properties
+     * txlemetry.setPersonProperties({
+     *     email: 'user@example.com',
+     *     plan: 'premium'
+     * })
+     * ```
+     *
+     * @example
+     * ```js
+     * // set properties with $set_once
+     * txlemetry.setPersonProperties(
+     *     { name: 'Max Hedgehog' },  // $set properties
+     *     { initial_url: '/blog' }   // $set_once properties
+     * )
+     * ```
+     *
+     * @example
+     * ```js
+     * // set properties without reloading feature flags
+     * txlemetry.setPersonProperties({ plan: 'premium' }, undefined, false)
+     * ```
+     *
+     * @public
+     *
+     * @param userPropertiesToSet - Optional: An object of properties to store about the user.
+     *   These properties will overwrite any existing values for the same keys.
+     * @param userPropertiesToSetOnce - Optional: An object of properties to store about the user.
+     *   If a property is previously set, this does not override that value.
+     * @param reloadFeatureFlags - Whether to reload feature flags after setting the properties. Defaults to true.
+     */
+    setPersonProperties(userPropertiesToSet?: {
+        [key: string]: JsonType;
+    }, userPropertiesToSetOnce?: {
+        [key: string]: JsonType;
+    }, reloadFeatureFlags?: boolean): void;
+    /**
+     * Removes properties from the person profile associated with the current `distinct_id`.
+     * Learn more about [identifying users](https://txlemetry.com/docs/product-analytics/identify)
+     *
+     * {@label Identification}
+     *
+     * @public
+     *
+     * @param propertyNames - The name (or names) of the person properties to remove.
+     * @param reloadFeatureFlags - Whether to reload feature flags after removing the properties. Defaults to true.
+     */
+    unsetPersonProperties(propertyNames: string | string[], reloadFeatureFlags?: boolean): void;
+    getSurveys(): Promise<SurveyResponse['surveys']>;
+    /**
+     * Returns a promise that resolves when surveys are ready to be loaded.
+     * If surveys are already loaded and ready to go, returns a resolved promise instead.
+     * @internal
+     */
+    _onSurveysReady(): Promise<void>;
+    private _surveysReadyResolve;
+    /**
+     * Helper function to cache surveys to storage with consistent logging
+     */
+    private _cacheSurveys;
+    /**
+     * Internal method to notify that surveys are ready
+     */
+    private _notifySurveysReady;
+    /**
+     * Handle surveys from remote config response
+     */
+    private _handleSurveysFromRemoteConfig;
+    private _isAutocaptureNativeErrors;
+    private _isNativePluginInitialized;
+    /**
+     * Initializes the native session replay SDK if not already initialized.
+     * This is called automatically by startSessionReplay() or lazily by startSessionRecording().
+     *
+     * @returns true if the native SDK is ready (initialized or already was), false otherwise
+     */
+    private initializeSessionReplayNative;
+    private initializeNativePlugin;
+    private startSessionReplay;
+    /**
+     * Decides whether session replay should be recording (replay enabled AND the linked
+     * flag, if any, on for the current user) and arms or pauses the native recorder to match.
+     *
+     * Runs at startup and on every feature flags load/reload (identify(), reset(),
+     * reloadFeatureFlags()), so recording starts, resumes, or pauses on identity changes
+     * without an app restart. `_sessionReplayRecordingActive` dedups repeated answers, and
+     * the init guards prevent double-starts. When replay is off, the native plugin is still
+     * initialized for native error tracking (both share one native instance).
+     *
+     * Pausing requires a real "flag off": core keeps the previous flag values across
+     * quota-limited/failed reloads, so a transient error never pauses a recording. Right
+     * after reset() the flags are genuinely unknown and pausing is the intended outcome.
+     *
+     * Evaluations are serialized so concurrent flags reloads run one at a time.
+     */
+    private _evaluateAndStartSessionReplay;
+    private _evaluateAndStartSessionReplayInternal;
+    /**
+     * Capture chokepoint for session-replay event triggers. Every captured event (capture, $screen,
+     * autocapture, lifecycle) passes through here. Chains to super first so `before_send` still runs;
+     * when a surviving event's name matches an armed trigger and the session hasn't activated yet, it
+     * activates replay for the session and kicks a re-evaluation that starts native recording. The
+     * trigger check never drops an event or throws into the capture path.
+     */
+    protected processBeforeEnqueue(message: TxlemetryEventProperties): TxlemetryEventProperties | null;
+    private _maybeActivateEventTrigger;
+    private _parseEventTriggers;
+    private _isEventTriggerActivatedForSession;
+    private captureAppLifecycleEvents;
+    private persistAppVersion;
+}