@c15t/react 2.2.1 → 2.3.0

package/docs/frameworks/react/concepts/consent-models.md

@@ -9,7 +9,7 @@ c15t supports four consent models that control how consent defaults, banner visi
 |--|--|--|--|
 |`opt-in`|Explicit consent required|Blocking banner|`false` (except `necessary`)|
 |`opt-out`|Processing allowed by default|Non-blocking notice|`true` (all granted)|
-|`iab`|IAB TCF 2.3 for programmatic ads|TCF banner|Managed by TCF framework|
+|`iab`|IAB TCF 2.4 for programmatic ads|TCF banner|Managed by TCF framework|
 |`null`|No regulation detected|No banner|`true` (all auto-granted)|
 
 There are two ways c15t determines which model applies:
@@ -56,7 +56,7 @@ When the policy has `consent.gpc: true`, the browser's Global Privacy Control si
 
 ### IAB
 
-IAB Transparency and Consent Framework (TCF) 2.3 mode for programmatic advertising compliance. Only activates when two conditions are met: the jurisdiction is `GDPR` or `UK_GDPR`, and `iab.enabled` is `true` in your configuration.
+IAB Transparency and Consent Framework (TCF) 2.4 mode for programmatic advertising compliance. Only activates when two conditions are met: the jurisdiction is `GDPR` or `UK_GDPR`, and `iab.enabled` is `true` in your configuration.
 
 When active, IAB mode generates TC strings, registers the `__tcfapi` CMP API, and works with the Global Vendor List (GVL) for machine-readable consent signals. If `iab.enabled` is not set, GDPR jurisdictions fall back to standard opt-in.
 

package/docs/frameworks/react/concepts/cookie-management.md

@@ -14,6 +14,10 @@ There are four sources of cookies on a typical website:
 **1. c15t itself**
 c15t stores the user's consent state in a `c15t` cookie (and mirrors it to localStorage). This cookie records which categories the user consented to, when they consented, and their subject ID. This is a strictly necessary cookie - it exists so the site remembers the user's consent choice.
 
+If reading `window.localStorage` or calling a storage method throws, c15t logs a warning and skips unavailable pending-submission queues. Runtime construction still completes, and cookie-backed choices can still be read and saved. In v2, a failed localStorage access check skips policy initialization and hides the banner. Optional categories without a saved choice remain denied.
+
+If the browser also blocks cookies, it cannot retain your choice across page loads. Do not use `enabled: false` to handle storage restrictions: that option grants every category.
+
 **2. Third-party scripts**
 When you load a tracking script (Google Analytics, Meta Pixel, etc.), that script sets its own cookies. Google Analytics creates `_ga` and `_gid` cookies. Meta creates `_fbp` and `_fbc`. These cookies are set by the script's code running in the browser - c15t prevents them by not loading the script until the user consents.
 

package/docs/frameworks/react/concepts/glossary.md

@@ -20,5 +20,5 @@ group: frameworks
 |--|--|
 |`jurisdiction`|A privacy regulation code (e.g., `GDPR`, `CCPA`, `PIPEDA`, `QC_LAW25`) detected from the user's geolocation. Maps to a consent model. See [Consent Models](/docs/frameworks/react/concepts/consent-models) for the full mapping table.|
 |GPC|Global Privacy Control — a browser signal (`Sec-GPC: 1`) indicating the user opts out of data sale/sharing. Honored when a policy sets `consent.gpc: true` (enabled by default in California presets).|
-|TCF|IAB Transparency and Consent Framework (v2.3) — a standard for programmatic advertising consent in GDPR jurisdictions. See [IAB TCF](/docs/frameworks/react/iab/overview).|
+|TCF|IAB Transparency and Consent Framework (v2.4) — a standard for programmatic advertising consent in GDPR jurisdictions. See [IAB TCF](/docs/frameworks/react/iab/overview).|
 |GVL|Global Vendor List — an IAB-maintained registry of ad-tech vendors and their declared purposes, used by the TCF consent flow.|

package/docs/frameworks/react/concepts/initialization-flow.md

@@ -69,9 +69,9 @@ sequenceDiagram
 
 **Init** — The store fetches the resolved policy, location, and translation data. In hosted mode this calls `GET /init` on your backend; in offline mode it resolves from `offlinePolicy.policyPacks` locally. If SSR data was passed to the provider, the network fetch is skipped entirely. See [Server-Side Utilities](/docs/frameworks/react/server-side) for SSR setup.
 
-**Policy resolution** — When [policy packs](/docs/frameworks/react/concepts/policy-packs) are configured, the backend resolves the right policy for the visitor based on their geo-location (region → country → fallback → default). The resolved policy determines the consent model (`opt-in`, `opt-out`, `iab`, or `none`), which categories are in scope, and what UI to show. For `opt-out` and `none` models, all categories are auto-granted — unless the resolved policy has `consent.gpc: true` and the browser sends a Global Privacy Control signal, in which case `marketing` and `measurement` are denied. If no policy pack is configured, the legacy jurisdiction-to-model mapping is used instead. See [Consent Models](/docs/frameworks/react/concepts/consent-models) for details.
+**Policy resolution** — When [policy packs](/docs/frameworks/react/concepts/policy-packs) are configured, the backend resolves the right policy for the visitor based on their geo-location (region → country → fallback → default). The resolved policy determines the consent model (`opt-in`, `opt-out`, `iab`, or `none`), which categories are in scope, and what UI to show. For `opt-out` and `none` models, categories are auto-granted only when there is no saved choice — unless the resolved policy has `consent.gpc: true` and the browser sends a Global Privacy Control signal, in which case `marketing` and `measurement` are denied. If no policy pack is configured, the legacy jurisdiction-to-model mapping is used instead. See [Consent Models](/docs/frameworks/react/concepts/consent-models) for details.
 
-**Re-prompting** — If the resolved policy's material fingerprint differs from the fingerprint stored with the user's last consent, the banner is shown again. This happens automatically when you change consent-affecting fields (model, categories, scope mode, allowed actions). Presentation-only changes do not trigger re-prompts. See [Policy Packs — Re-Prompting](/docs/frameworks/react/concepts/policy-packs#re-prompting) for details.
+**Re-prompting** — If the resolved policy's material fingerprint differs from the fingerprint stored with the user's last consent, previous grants become invalid, while the saved choice and its denials remain. The consent UI opens again when the resolved policy has one; under a no-banner policy, invalidated grants stay denied until the user makes a new choice. This happens automatically when you change consent-affecting fields (model, categories, scope mode, allowed actions). Presentation-only changes do not trigger re-prompts. See [Policy Packs — Re-Prompting](/docs/frameworks/react/concepts/policy-packs#re-prompting) for details.
 
 **Save** — When the user interacts with the banner or dialog, their choices are persisted to localStorage/cookies and synced to the backend (along with the `policySnapshotToken` if snapshot signing is configured). Script, iframe, and network gating rules update immediately based on the new consent state. See the [Script Loader](/docs/frameworks/react/script-loader), [Iframe Blocking](/docs/frameworks/react/iframe-blocking), and [Network Blocker](/docs/frameworks/react/network-blocker) guides for gating details.
 
@@ -85,7 +85,7 @@ The banner appears when any of these conditions are true:
 2. **Policy changed** — the material policy fingerprint differs from the fingerprint stored with the user's last consent (re-prompting)
 3. **Storage is accessible** — the browser allows localStorage (not blocked in private mode)
 
-If the resolved model is `none` or `opt-out` (and `ui.mode` is `none`), consents are auto-granted and the banner never appears. See [Consent Models](/docs/frameworks/react/concepts/consent-models) and [Policy Packs](/docs/frameworks/react/concepts/policy-packs) for details.
+If the resolved model is `none` or `opt-out` (and `ui.mode` is `none`) and no saved choice exists, consents are auto-granted and the banner never appears. An existing saved choice keeps its denials, but grants invalidated by a policy change stay denied until the user makes a new choice. See [Consent Models](/docs/frameworks/react/concepts/consent-models) and [Policy Packs](/docs/frameworks/react/concepts/policy-packs) for details.
 
 ## Debugging the Lifecycle
 

package/docs/frameworks/react/concepts/policy-packs.md

@@ -32,7 +32,7 @@ const policies = [
 |Preset|Model|UI|Matches|
 |--|--|--|--|
 |`europeOptIn()`|`opt-in`|banner|EEA + UK countries + geo fallback|
-|`europeIab()`|`iab`|banner|EEA + UK countries + geo fallback (TCF 2.3)|
+|`europeIab()`|`iab`|banner|EEA + UK countries + geo fallback (TCF 2.4)|
 |`californiaOptOut()`|`opt-out`|none|US-CA region|
 |`quebecOptIn()`|`opt-in`|banner|CA-QC region|
 |`worldNoBanner()`|`none`|none|default fallback|
@@ -65,7 +65,7 @@ Each policy combination produces a different consent experience:
 |`model: 'opt-out'`, `ui.mode: 'none'`|No banner, everything loads immediately — user opts out via a "Do Not Sell" link|
 |`model: 'none'`, `ui.mode: 'none'`|No banner, all categories auto-granted silently|
 |`model: 'opt-in'`, `ui.mode: 'dialog'`|Full-screen dialog, nothing loads until the user consents|
-|`model: 'iab'`, `ui.mode: 'banner'`|IAB TCF 2.3 banner with vendor-level controls|
+|`model: 'iab'`, `ui.mode: 'banner'`|IAB TCF 2.4 banner with vendor-level controls|
 
 ## How Policy Resolution Works
 
@@ -203,6 +203,8 @@ back to the `eu` profile's `fallbackLanguage`.
 
 When you change a policy in a way that affects consent semantics — like adding a category, changing the consent model, or modifying allowed actions — c15t automatically re-prompts returning users.
 
+A material policy change invalidates previous grants but keeps the user's choice record and denials. Optional categories stay denied until the user makes a new choice. The resolved policy controls whether a banner or dialog appears; a no-banner policy does not silently grant previously rejected categories. A temporary hosted initialization failure does not count as an authoritative policy change.
+
 This works through the **material policy fingerprint**: a hash of only the consent-affecting fields (model, categories, scope, allowed actions, grouped action layout, direction, proof settings). Presentation-only changes like copy, button styling, or scroll lock do not trigger re-prompts.
 
 |Change|Re-prompts?|

package/docs/frameworks/react/hooks/use-consent-manager/overview.md

@@ -168,5 +168,5 @@ type Model = 'opt-in' | 'opt-out' | 'iab' | null;
 
 * `'opt-in'` — Explicit consent required before tracking (GDPR)
 * `'opt-out'` — Tracking allowed by default, user can opt out (CCPA)
-* `'iab'` — IAB TCF 2.3 compliance mode
+* `'iab'` — IAB TCF 2.4 compliance mode
 * `null` — No jurisdiction detected yet

package/docs/frameworks/react/iab/consent-banner.md

@@ -1,13 +1,13 @@
 ---
 title: IABConsentBanner
-description: An IAB TCF 2.3 compliant consent banner that displays partner
+description: An IAB TCF 2.4 compliant consent banner that displays partner
   count, purpose summaries, and legitimate interest notices.
 group: frameworks
 ---
 > ℹ️ **Info:**
 > c15t's IAB TCF support can be used in production. Use Inth for a hosted, IAB TCF-certified CMP setup with a managed CMP ID, or register your own CMP with IAB Europe and configure your own CMP ID.
 
-`IABConsentBanner` is a pre-built consent banner that follows the [IAB Transparency & Consent Framework (TCF) 2.3](https://iabeurope.eu/tcf-2-0/) specification. It renders when the consent model is set to `'iab'` and includes required disclosures like partner count, purpose summaries, and legitimate interest notices.
+`IABConsentBanner` is a pre-built consent banner that follows the [IAB Transparency & Consent Framework (TCF) 2.4](https://iabeurope.eu/tcf-2-0/) specification. It renders when the consent model is set to `'iab'` and includes required disclosures like partner count, purpose summaries, and legitimate interest notices.
 
 Use this component instead of `ConsentBanner` when you need IAB TCF compliance for programmatic advertising in EU jurisdictions.
 

package/docs/frameworks/react/iab/consent-dialog.md

@@ -1,13 +1,13 @@
 ---
 title: IABConsentDialog
-description: An IAB TCF 2.3 compliant preference center with tabbed purpose and
+description: An IAB TCF 2.4 compliant preference center with tabbed purpose and
   vendor management.
 group: frameworks
 ---
 > ℹ️ **Info:**
 > c15t's IAB TCF support can be used in production. Use Inth for a hosted, IAB TCF-certified CMP setup with a managed CMP ID, or register your own CMP with IAB Europe and configure your own CMP ID.
 
-`IABConsentDialog` is an IAB TCF 2.3 compliant consent dialog that provides a tabbed interface for managing purpose consent and vendor preferences. It includes purpose grouping via stacks, individual purpose/vendor toggles, special purpose and feature disclosures, and legitimate interest handling.
+`IABConsentDialog` is an IAB TCF 2.4 compliant consent dialog that provides a tabbed interface for managing purpose consent and vendor preferences. It includes purpose grouping via stacks, individual purpose/vendor toggles, special purpose and feature disclosures, and legitimate interest handling.
 
 ## Basic Usage
 
@@ -52,7 +52,8 @@ Displays all IAB purposes grouped into:
 * **Standalone purposes** — Purpose 1 (Store and/or access information on a device) is always shown standalone per IAB TCF spec
 * **Stacks** — Groups of related purposes determined by the GVL. Each stack is expandable to show individual purpose toggles
 * **Special features** — Opt-in features like precise geolocation
-* **Essential functions** — Special purposes and features that are locked (no user toggle) because they're required for basic operation
+* **Essential functions** — Special purposes, which are locked (no user toggle) because vendors need them for basic operation
+* **Features** — An informational section, shown when at least one vendor declares a feature
 
 Each purpose shows:
 
@@ -62,6 +63,14 @@ Each purpose shows:
 * Legitimate interest toggle where applicable
 * Expandable vendor list
 
+### Features section
+
+TCF Policies v5.0.b treat features as information, not choices. The Features section follows those rules:
+
+* Under the heading, the dialog shows the IAB standard text from the vendor list (`standardTexts.features`). If the vendor list does not include it, the dialog shows the `iab.preferenceCenter.features.description` translation.
+* Each feature shows its name, description, IAB illustrations under **Examples**, and the names of the vendors that use it.
+* The section has no switches, lock icons or per-vendor toggles. Features only serve the purposes the user chooses elsewhere in the dialog.
+
 ### Vendors Tab
 
 Displays all vendors from the GVL plus any custom vendors:

package/docs/frameworks/react/iab/overview.md

@@ -1,12 +1,12 @@
 ---
-title: IAB TCF 2.3
-description: Implement IAB Transparency & Consent Framework 2.3 compliance for
+title: IAB TCF 2.4
+description: Implement IAB Transparency & Consent Framework 2.4 compliance for
   programmatic advertising in EU/EEA jurisdictions.
 group: frameworks
 ---
 ## What is IAB TCF?
 
-The [IAB Transparency & Consent Framework (TCF)](https://iabeurope.eu/tcf-2-0/) is a standardized protocol for communicating user consent choices to ad tech vendors in the programmatic advertising ecosystem. TCF 2.3 is the current version and is widely adopted across the EU/EEA.
+The [IAB Transparency & Consent Framework (TCF)](https://iabeurope.eu/tcf-2-0/) is a standardized protocol for communicating user consent choices to ad tech vendors in the programmatic advertising ecosystem. TCF 2.4 is the current version and is widely adopted across the EU/EEA.
 
 When your site participates in the IAB ecosystem (ad exchanges, SSPs, DSPs, DMPs), you need to:
 
@@ -26,7 +26,7 @@ If you self-host the c15t backend or want to operate as your own CMP, register y
 
 ## How c15t Implements TCF
 
-c15t provides a complete IAB TCF 2.3 CMP (Consent Management Platform) implementation:
+c15t provides a complete IAB TCF 2.4 CMP (Consent Management Platform) implementation:
 
 1. **Global Vendor List (GVL)** — Automatically fetched from the c15t backend. Contains the official IAB vendor registry with purposes, features, and stacks.
 2. **IABConsentBanner** — A pre-built banner showing partner count, purpose summaries, and legitimate interest notices.
@@ -95,7 +95,11 @@ Purposes are grouped into **stacks** by the GVL for a simplified UI presentation
 
 ### Special Features
 
-Features like precise geolocation or device scanning that require explicit opt-in beyond standard consent.
+Features like precise geolocation, or identifying devices based on information actively requested, that require explicit opt-in beyond standard consent.
+
+### Features
+
+Features, such as linking different devices, are means of processing that vendors use only for the purposes the user chooses. They have no consent toggle. The preference center lists them in an informational section with the IAB standard text.
 
 ### Legitimate Interest
 
@@ -105,11 +109,19 @@ Some purposes can be processed under legitimate interest rather than consent. Us
 
 Each vendor in the GVL declares which purposes it uses, whether via consent or legitimate interest. The preference center lets users toggle consent per-vendor.
 
+## Consent Scope
+
+c15t stores TCF choices per site and browser, so every TC string it creates is service-specific. c15t does not sync TCF choices across devices.
+
+Do not use `/consent/check` or your own account data to skip the TCF UI on another device. Reusing choices across devices is a multi-device scope, and the TCF requires you to disclose that scope in the first layer of the UI, which the prebuilt IAB components do not do.
+
+The `isServiceSpecific` option is deprecated. TCF requires IsServiceSpecific=1 in every TC string, so c15t always encodes `true` and logs a warning if you pass `false`.
+
 ## Standard vs IAB Components
 
 |Feature|ConsentBanner / ConsentDialog|IABConsentBanner / IABConsentDialog|
 |--|--|--|
-|Consent model|opt-in / opt-out|IAB TCF 2.3|
+|Consent model|opt-in / opt-out|IAB TCF 2.4|
 |Granularity|Category-level (measurement, marketing, etc.)|Purpose-level + vendor-level|
 |Vendor management|No|Yes (full GVL integration)|
 |TC String|No|Yes|

package/docs/frameworks/react/iframe-blocking.md

@@ -73,6 +73,8 @@ For iframes outside of React (e.g., CMS content, server-rendered HTML), add `dat
 
 When consent for the specified category is granted, c15t automatically swaps `data-src` to `src`, loading the iframe. When consent is revoked, `src` is moved back to `data-src`.
 
+The `data-category` value must be one of `necessary`, `functionality`, `measurement`, `experience`, or `marketing`. An iframe with any other value, including an empty one, stays blocked, and c15t logs a warning to the console.
+
 ### Dynamic Iframes
 
 c15t uses a `MutationObserver` to watch for dynamically added iframes. Any iframe with `data-category` added to the DOM after initialization is automatically processed.

package/docs/frameworks/react/policy-packs.md

@@ -73,7 +73,7 @@ Available presets:
 |Preset|Model|Matches|
 |--|--|--|
 |`europeOptIn()`|`opt-in`|EEA + UK countries + geo fallback|
-|`europeIab()`|`iab`|EEA + UK countries + geo fallback (TCF 2.3)|
+|`europeIab()`|`iab`|EEA + UK countries + geo fallback (TCF 2.4)|
 |`californiaOptOut()`|`opt-out`|US-CA region|
 |`quebecOptIn()`|`opt-in`|CA-QC region|
 |`worldNoBanner()`|`none`|default fallback|

package/docs/integrations/front-chat.md

@@ -0,0 +1,178 @@
+---
+title: Front Chat
+description: Load Front Chat after functionality consent and initialize the
+  widget when its SDK is ready.
+group: integrations
+---
+Front Chat adds a live chat widget connected to your Front inbox. c15t waits for
+functionality consent before loading the widget's SDK and calling `FrontChat('init')`.
+
+## Official Front documentation
+
+* [Set up a Front Chat inbox and install the widget](https://help.front.com/en/articles/2049)
+* [Chat Widget SDK reference](https://dev.frontapp.com/docs/chat-sdk-reference)
+
+## Integrate with c15t
+
+Copy the `chatId` from the widget code snippet in your Front Chat channel's
+**Installation** tab. Pass that value to `frontChat()` instead of adding Front's
+script snippet separately.
+
+**React**
+
+```tsx
+import { type ReactNode } from 'react';
+import { ConsentManagerProvider } from '@c15t/react';
+import { frontChat } from '@c15t/scripts/front-chat';
+
+const scripts = [frontChat({ chatId: 'YOUR_FRONT_CHAT_ID' })];
+
+export function ConsentProvider({ children }: { children: ReactNode }) {
+  return (
+    <ConsentManagerProvider
+      options={{
+        mode: 'hosted',
+        backendURL: 'https://your-instance.c15t.dev',
+        scripts,
+      }}
+    >
+      {children}
+    </ConsentManagerProvider>
+  );
+}
+```
+
+**Next.js**
+
+```tsx
+'use client';
+
+import { type ReactNode } from 'react';
+import { ConsentManagerProvider } from '@c15t/nextjs';
+import { frontChat } from '@c15t/scripts/front-chat';
+
+const scripts = [frontChat({ chatId: 'YOUR_FRONT_CHAT_ID' })];
+
+export function ConsentProvider({ children }: { children: ReactNode }) {
+  return (
+    <ConsentManagerProvider
+      options={{
+        mode: 'hosted',
+        backendURL: '/api/c15t',
+        scripts,
+      }}
+    >
+      {children}
+    </ConsentManagerProvider>
+  );
+}
+```
+
+**JavaScript**
+
+```ts
+import { getOrCreateConsentRuntime } from 'c15t';
+import { frontChat } from '@c15t/scripts/front-chat';
+
+getOrCreateConsentRuntime({
+  mode: 'hosted',
+  backendURL: 'https://your-instance.c15t.dev',
+  scripts: [frontChat({ chatId: 'YOUR_FRONT_CHAT_ID' })],
+});
+```
+
+## How c15t loads it
+
+* **Category:** `functionality` (Functional)
+* **Loads when:** functionality consent is granted
+* **Script:** `https://chat-assets.frontapp.com/v1/chat.bundle.js`
+* **After load:** c15t calls `window.FrontChat('init', ...)` with your chat ID and launcher options
+* **On revocation:** c15t reloads the page by default and leaves Front Chat unloaded while functionality consent is denied
+
+Keep the default `reloadOnConsentRevoked: true` behavior. Removing a script tag
+does not stop a widget that has already initialized, and this integration does
+not provide automatic widget shutdown when you disable the reload.
+
+## Configure the integration
+
+`chatId` must be a non-empty string. The default launcher is enabled unless you
+set `useDefaultLauncher` to `false`:
+
+```ts
+frontChat({
+  chatId: 'YOUR_FRONT_CHAT_ID',
+  useDefaultLauncher: false,
+})
+```
+
+With the default launcher hidden, use Front's SDK to open the widget from your
+own launcher after consent is granted and the widget has initialized. See the
+[SDK reference](https://dev.frontapp.com/docs/chat-sdk-reference) for commands
+and initialization requirements.
+
+### Content Security Policy
+
+If your Content Security Policy (CSP) uses nonces, pass the server-generated nonce
+for the current response. c15t applies it to the loader script and forwards it
+to Front's initialization call:
+
+```ts
+function createChatScripts(nonce: string) {
+  return [frontChat({ chatId: 'YOUR_FRONT_CHAT_ID', nonce })];
+}
+```
+
+Front creates additional resources for the widget. Follow Front's
+[CSP setup instructions](https://help.front.com/en/articles/2049) for the
+remaining policy requirements. You can override the loader URL with `scriptSrc`
+if you serve the SDK through your own proxy; this does not proxy the widget's
+other requests.
+
+### Optional session cleanup
+
+`frontChat()` does not automatically delete an existing Front session. You can
+also request session cleanup before c15t's revocation reload using
+`shutdownFrontChat()`:
+
+```ts
+import { getOrCreateConsentRuntime } from 'c15t';
+import { frontChat, shutdownFrontChat } from '@c15t/scripts/front-chat';
+
+getOrCreateConsentRuntime({
+  mode: 'hosted',
+  backendURL: 'https://your-instance.c15t.dev',
+  scripts: [frontChat({ chatId: 'YOUR_FRONT_CHAT_ID' })],
+  callbacks: {
+    onBeforeConsentRevocationReload: ({ preferences }) => {
+      if (!preferences.functionality) {
+        shutdownFrontChat();
+      }
+    },
+  },
+});
+```
+
+The function calls Front's `shutdown` command with `clearSession: true` when
+the SDK is available. This is a best-effort request: the reload does not wait
+for Front to finish clearing its session. Keep reload on revocation enabled;
+the cleanup call does not replace it.
+
+## Types
+
+### FrontChatOptions
+
+|Property|Value|
+|:--|:--|
+|Type Name|\`FrontChatOptions\`|
+|Source Path|\`./packages/scripts/src/vendors/functional/front-chat.ts\`|
+
+\*ExtractedTypeTable: Could not extract "FrontChatOptions" from "./packages/scripts/src/vendors/functional/front-chat.ts" using base path "/home/runner/work/c15t/c15t". Verify the path/name and that the file is included by your tsconfig.\*
+
+### Script
+
+|Property|Value|
+|:--|:--|
+|Type Name|\`Script\`|
+|Source Path|\`./packages/core/src/libs/script-loader/types.ts\`|
+
+\*ExtractedTypeTable: Could not extract "Script" from "./packages/core/src/libs/script-loader/types.ts" using base path "/home/runner/work/c15t/c15t". Verify the path/name and that the file is included by your tsconfig.\*

package/docs/integrations/one-dollar-stats.md

@@ -0,0 +1,118 @@
+---
+title: OneDollarStats
+description: Load OneDollarStats after measurement consent with optional tracker
+  data attributes.
+group: integrations
+---
+[OneDollarStats](https://onedollarstats.com/) matches events to the domain registered in your dashboard, so no API key is needed. This helper loads its classic deferred script after measurement consent and forwards settings as `data-*` attributes.
+
+## Integrate with c15t
+
+**React**
+
+```tsx
+import { type ReactNode } from 'react';
+import { ConsentManagerProvider } from '@c15t/react';
+import { oneDollarStats } from '@c15t/scripts/one-dollar-stats';
+
+const scripts = [oneDollarStats()];
+
+export function ConsentProvider({ children }: { children: ReactNode }) {
+  return (
+    <ConsentManagerProvider
+      options={{
+        mode: 'hosted',
+        backendURL: 'https://your-instance.c15t.dev',
+        scripts,
+      }}
+    >
+      {children}
+    </ConsentManagerProvider>
+  );
+}
+```
+
+**Next.js**
+
+```tsx
+'use client';
+
+import { type ReactNode } from 'react';
+import { ConsentManagerProvider } from '@c15t/nextjs';
+import { oneDollarStats } from '@c15t/scripts/one-dollar-stats';
+
+const scripts = [oneDollarStats()];
+
+export function ConsentProvider({ children }: { children: ReactNode }) {
+  return (
+    <ConsentManagerProvider
+      options={{
+        mode: 'hosted',
+        backendURL: '/api/c15t',
+        scripts,
+      }}
+    >
+      {children}
+    </ConsentManagerProvider>
+  );
+}
+```
+
+**JavaScript**
+
+```ts
+import { getOrCreateConsentRuntime } from 'c15t';
+import { oneDollarStats } from '@c15t/scripts/one-dollar-stats';
+
+getOrCreateConsentRuntime({
+  mode: 'hosted',
+  backendURL: 'https://your-instance.c15t.dev',
+  scripts: [oneDollarStats()],
+});
+```
+
+## Tracker settings
+
+All settings use strings and omit the `data-` prefix. Unknown settings are forwarded for compatibility with future tracker options.
+
+```ts
+oneDollarStats({
+  hostname: 'docs.example.com',
+  devmode: 'true',
+  autocollect: 'false',
+  'hash-routing': 'true',
+  url: 'https://analytics.example.com/events',
+})
+```
+
+* `hostname` must be a bare hostname, optionally including a port. It overrides the event hostname on every host, including production.
+* Local testing needs both `hostname` and `devmode: 'true'`.
+* `autocollect: 'false'` disables automatic pageview and click collection.
+* `'hash-routing': 'false'` omits the attribute entirely: the CDN tracker enables hash routing whenever the attribute is present, regardless of its value.
+* `url` overrides the collection endpoint. Leave it unset to use the vendor default.
+
+The tracker handles browser history navigation itself; no extra router hook is required. See the [vendor installation reference](https://docs.onedollarstats.com/installation) for its settings.
+
+## Consent behaviour
+
+The script uses the `measurement` category and loads only when that consent is granted. On revocation, c15t removes its script element. Removing a script does not undo code that already executed, including the tracker's history hooks and event listeners. Use c15t's reload-on-revocation behaviour to clear the running tracker, and check measurement consent before making manual tracking calls.
+
+## Types
+
+### OneDollarStatsOptions
+
+|Property|Value|
+|:--|:--|
+|Type Name|\`OneDollarStatsOptions\`|
+|Source Path|\`./packages/scripts/src/vendors/analytics/one-dollar-stats.ts\`|
+
+\*ExtractedTypeTable: Could not extract "OneDollarStatsOptions" from "./packages/scripts/src/vendors/analytics/one-dollar-stats.ts" using base path "/home/runner/work/c15t/c15t". Verify the path/name and that the file is included by your tsconfig.\*
+
+### Script
+
+|Property|Value|
+|:--|:--|
+|Type Name|\`Script\`|
+|Source Path|\`./packages/core/src/libs/script-loader/types.ts\`|
+
+\*ExtractedTypeTable: Could not extract "Script" from "./packages/core/src/libs/script-loader/types.ts" using base path "/home/runner/work/c15t/c15t". Verify the path/name and that the file is included by your tsconfig.\*

package/docs/integrations/overview.md

@@ -94,6 +94,7 @@ Analytics integrations usually require `measurement` consent. Some vendors can r
 * [LogRocket](/docs/integrations/logrocket)
 * [Matomo Analytics](/docs/integrations/matomo-analytics)
 * [PostHog](/docs/integrations/posthog)
+* [OneDollarStats](/docs/integrations/one-dollar-stats)
 * [Promptwatch](/docs/integrations/promptwatch)
 * [Pirsch](/docs/integrations/pirsch)
 * [RudderStack](/docs/integrations/rudderstack)
@@ -107,6 +108,7 @@ Analytics integrations usually require `measurement` consent. Some vendors can r
 Functional integrations usually require `functionality` consent. They add optional user-facing capabilities, such as chat widgets, that should only run after the user allows them.
 
 * [Crisp](/docs/integrations/crisp)
+* [Front Chat](/docs/integrations/front-chat)
 * [Intercom](/docs/integrations/intercom)
 
 ## Ads & Pixels
@@ -120,6 +122,7 @@ Advertising pixels usually require `marketing` consent. Many of them need startu
 * [LinkedIn Insight Tag](/docs/integrations/linkedin-insights)
 * [Microsoft UET](/docs/integrations/microsoft-uet)
 * [X (Twitter) Pixel](/docs/integrations/x-pixel)
+* [Pinterest Tag](/docs/integrations/pinterest-tag)
 
 ## Tag Managers