@c15t/nextjs 2.2.1 → 3.0.0-alpha.1

package/docs/integrations/matomo-analytics.md

@@ -1,171 +1,316 @@
 ---
 title: Matomo Analytics
-description: Load Matomo with c15t and keep Matomo's queue aligned with measurement consent.
+description: Choose gated loading or Matomo consent signaling and configure the
+  correct tracker endpoints.
 group: integrations
-icon: matomo
 ---
-Matomo gives you privacy-focused web analytics with self-hosted and cloud deployment options. The `matomoAnalytics()` helper sets up Matomo's `_paq` queue, points it at your tracker, and can queue consent-aware commands before the vendor bundle loads.
 
-## Integrate with c15t
+## Configure Matomo
 
-**React**
+Use the site ID and base URL from your Matomo installation. This setup waits
+for measurement permission before requesting `matomo.js`.
 
-```tsx
-import { type ReactNode } from 'react';
-import { ConsentManagerProvider } from '@c15t/react';
+| Package manager | Command                     |
+| :-------------- | :-------------------------- |
+| npm             | `npm install @c15t/scripts` |
+| pnpm            | `pnpm add @c15t/scripts`    |
+| yarn            | `yarn add @c15t/scripts`    |
+| bun             | `bun add @c15t/scripts`     |
+
+```ts title="src/consent-scripts.ts"
 import { matomoAnalytics } from '@c15t/scripts/matomo-analytics';
 
-const scripts = [
+export const scripts = [
   matomoAnalytics({
-    matomoUrl: 'https://analytics.example.com',
     siteId: 1,
+    matomoUrl: 'https://analytics.example.com',
   }),
 ];
-
-export function ConsentProvider({ children }: { children: ReactNode }) {
-  return (
-    <ConsentManagerProvider
-      options={{
-        mode: 'hosted',
-        backendURL: 'https://your-instance.c15t.dev',
-        scripts,
-      }}
-    >
-      {children}
-    </ConsentManagerProvider>
-  );
-}
 ```
 
+Replace the base URL and site ID. For Matomo Cloud, use
+`cloudId: 'your-site.matomo.cloud'` instead of `matomoUrl`.
+
+## Register the scripts
+
+Complete your [framework quickstart](https://c15t.com/docs/frameworks) first. Keep its Inth
+endpoint, policy, styles and consent UI. Remove the vendor's original script,
+SDK initializer or tag-manager entry so c15t owns loading once.
+
+The `scripts` export in `src/consent-scripts.ts` is a configuration, not an
+initializer. Add it to your existing consent owner using the registration point
+below. These are partial edits to that owner, not additional providers.
+
 **Next.js**
 
+Import the configuration into the client boundary from your router guide:
+
+```ts
+import { ConsentRoot } from 'c15t/next';
+import { scripts } from './consent-scripts';
+```
+
+Keep the server-resolved `state` and shared `consentConfig` from your
+router guide. Its manifest, init and save URLs stay in effect. Add
+`scripts` as a top-level prop on the existing root:
+
 ```tsx
-'use client';
+<ConsentRoot state={state} config={consentConfig} scripts={scripts}>
+  {children}
+</ConsentRoot>
+```
 
-import { type ReactNode } from 'react';
-import { ConsentManagerProvider } from '@c15t/nextjs';
-import { matomoAnalytics } from '@c15t/scripts/matomo-analytics';
+For a Pages Router or static-export setup using `ConsentProvider`, add
+`scripts` to its existing `options` instead. Keep the router-specific setup
+from [Next.js script loading](../frameworks/next/script-loader.md).
 
-const scripts = [
-  matomoAnalytics({
-    matomoUrl: 'https://analytics.example.com',
-    siteId: 1,
-  }),
-];
+**TanStack Start**
+
+In your existing root route component, import the scripts alongside
+`ConsentRoot`. Keep the server loader from the [TanStack Start quickstart](https://c15t.com/docs/frameworks/tanstack-start/quickstart).
 
-export function ConsentProvider({ children }: { children: ReactNode }) {
+```tsx
+import { Outlet } from '@tanstack/react-router';
+import { ConsentRoot } from 'c15t/tanstack-start';
+import { scripts } from '../consent-scripts';
+
+function Root() {
+  const state = Route.useLoaderData();
   return (
-    <ConsentManagerProvider
-      options={{
-        mode: 'hosted',
-        backendURL: '/api/c15t',
-        scripts,
-      }}
-    >
-      {children}
-    </ConsentManagerProvider>
+    <ConsentRoot state={state} backendURL={backendURL} initRoute={false} scripts={scripts}>
+      <Outlet />
+      {/* Keep your consent banner, dialog and preferences link here. */}
+    </ConsentRoot>
   );
 }
 ```
 
-**JavaScript**
+This edits the existing route. `Route` and `backendURL` come from its setup;
+keep the document shell and head components if they are part of your root.
+`initRoute={false}` keeps the quickstart's direct-backend initialization.
+If your app mounts a consent server route, retain its existing `initRoute`
+instead. Do not return script callbacks from a server function or route loader.
+
+**React**
+
+Import the scripts into your existing provider component:
 
 ```ts
-import { getOrCreateConsentRuntime } from 'c15t';
-import { matomoAnalytics } from '@c15t/scripts/matomo-analytics';
+import { ConsentProvider } from 'c15t/react';
+import { scripts } from './consent-scripts';
+```
 
-getOrCreateConsentRuntime({
-  mode: 'hosted',
-  backendURL: 'https://your-instance.c15t.dev',
-  scripts: [
-    matomoAnalytics({
-      matomoUrl: 'https://analytics.example.com',
-      siteId: 1,
-    }),
-  ],
-});
+Keep the existing options and add `scripts`:
+
+```tsx
+<ConsentProvider options={{ ...consentOptions, scripts }}>
+  {children}
+</ConsentProvider>
 ```
 
-## How c15t loads it
+Here `consentOptions` is your existing configuration, including
+`mode: hosted({ url: backendURL })`. Keep the banner, dialog and preferences
+link inside the provider. See [React script loading](https://c15t.com/docs/frameworks/react/script-loader).
 
-* **Category:** `measurement` (Analytics)
-* **Loads when:** measurement consent is granted by default
-* **Consent mode option:** with `defaultConsent`, the helper switches to `alwaysLoad: true` and uses Matomo queue commands to grant/forget consent without unloading the SDK.
+**Nuxt**
 
-## Configure the integration
+Attach one loader from the root `app.vue`, after the Nuxt module has
+started its browser runtime. This keeps vendor callbacks in application code rather
+than serialized `nuxt.config.ts` runtime configuration.
 
-If you want Matomo to manage consent internally, set `defaultConsent` to one
-of these values:
+```vue title="app/app.vue"
+<script setup lang="ts">
+import { onUnmounted } from 'vue';
+import { createScriptLoader } from 'c15t/modules/script-loader';
+import { scripts } from '../src/consent-scripts';
 
-* `'required'` queues Matomo's `requireConsent` command so no tracking runs
-  until consent is granted.
-* `'given'` queues Matomo's `setConsentGiven` command so tracking starts as
-  granted by default.
+const nuxtApp = useNuxtApp();
+const kernel = useConsentKernel();
+let loader: ReturnType<typeof createScriptLoader> | undefined;
 
-When `defaultConsent` is omitted, c15t uses the standard script-loader flow:
-Matomo only loads after `measurement` consent is granted.
+const removeMountedHook = nuxtApp.hook('app:mounted', () => {
+  loader = createScriptLoader({ kernel, scripts });
+});
+onUnmounted(() => {
+  removeMountedHook();
+  loader?.dispose();
+});
+</script>
 
-```ts
-import { matomoAnalytics } from '@c15t/scripts/matomo-analytics';
+<template>
+  <ConsentRoot />
+  <NuxtPage />
+</template>
+```
+
+Merge the setup code into your root and retain its footer and preferences
+link. `useConsentKernel` is auto-imported by the c15t Nuxt module. Adjust the
+relative script import if your `app.vue` is at the project root. This loader
+waits until the module has applied browser persistence and privacy signals,
+then reads the current snapshot and observes future changes. Do not also register these scripts
+in another loader. See the [Nuxt quickstart](https://c15t.com/docs/frameworks/nuxt/quickstart).
 
-matomoAnalytics({
-  matomoUrl: 'https://analytics.example.com',
-  siteId: 1,
-  defaultConsent: 'required',
+**Vue**
+
+Use the kernel already provided by the Vue plugin. Merge this setup into
+`App.vue`, whose lifetime covers the application:
+
+```vue title="src/App.vue"
+<script setup lang="ts">
+import { onMounted, onUnmounted } from 'vue';
+import { createScriptLoader } from 'c15t/modules/script-loader';
+import { useConsentKernel } from 'c15t/vue/vue-plugin';
+import ConsentRoot from 'c15t/vue/consent-root';
+import { scripts } from './consent-scripts';
+
+const kernel = useConsentKernel();
+let loader: ReturnType<typeof createScriptLoader> | undefined;
+
+onMounted(() => {
+  loader = createScriptLoader({ kernel, scripts });
 });
+onUnmounted(() => loader?.dispose());
+</script>
+
+<template>
+  <ConsentRoot />
+  <main>Your application</main>
+</template>
 ```
 
-## Tracking events in your app
+Keep your existing page content and preferences link. The plugin still owns
+the kernel and persistence; this component owns only the vendor loader.
+Do not register the same scripts in plugin configuration as well. See the
+[Vue quickstart](https://c15t.com/docs/frameworks/vue/quickstart).
 
-Matomo's runtime API is queue-based (`window._paq`). When the script is not loaded yet, pushing to `_paq` is still safe as long as the queue exists. The helper creates `_paq` during setup.
+**Astro**
 
-From React:
+Point the existing Astro integration at a client module. Keep its `mode`,
+`ui` and framework integration from the [Astro quickstart](https://c15t.com/docs/frameworks/astro/quickstart).
+Import `fileURLToPath` in your Astro configuration:
 
-```tsx
-import { useCallback } from 'react';
-import { useConsentManager } from '@c15t/react';
+```js title="astro.config.mjs"
+import { fileURLToPath } from 'node:url';
+```
 
-function SignupExample() {
-  const { has } = useConsentManager();
+Add this option to the existing `c15t({ ... })` call. Resolve the path from
+the configuration file because Astro injects the import into a virtual module:
 
-  const trackSignup = useCallback(() => {
-    if (has('measurement')) {
-      window._paq?.push(['trackEvent', 'signup', 'completed']);
-    }
-  }, [has]);
+```js
+clientEntrypoint: fileURLToPath(new URL('./src/c15t.client.ts', import.meta.url)),
+```
 
-  return <button onClick={trackSignup}>Sign up</button>;
-}
+Export the scripts from that module:
+
+```ts title="src/c15t.client.ts"
+import type { C15tClientOptionsExtension } from '@c15t/astro';
+import { scripts } from './consent-scripts';
+
+export default { scripts } satisfies C15tClientOptionsExtension;
 ```
 
-From plain JavaScript:
+The integration passes this extension to its shared browser runtime. Vendor
+helpers contain callbacks, so do not put them in the serialized `scripts`
+option in `astro.config.mjs`. Keep one runtime across consent islands and
+`ClientRouter` navigation.
 
-```ts
-import { getOrCreateConsentRuntime } from 'c15t';
+**Svelte**
 
-const { consentStore } = getOrCreateConsentRuntime();
+Import the scripts in the component that owns your existing provider and
+pass them as a top-level prop:
 
-if (consentStore.getState().has('measurement')) {
-  window._paq?.push(['trackEvent', 'signup', 'completed']);
-}
+```svelte title="src/App.svelte"
+<script lang="ts">
+  import { ConsentManagerProvider, hosted } from '@c15t/svelte';
+  import { scripts } from './consent-scripts';
+
+  const backendURL = import.meta.env.VITE_C15T_BACKEND_URL;
+  if (!backendURL) throw new Error('Set VITE_C15T_BACKEND_URL');
+  const mode = hosted({ url: backendURL });
+</script>
+
+<ConsentManagerProvider {mode} {scripts}>
+  <!-- Keep your application, consent UI and preferences link here. -->
+</ConsentManagerProvider>
 ```
 
-## Types
+Retain the styles and consent UI from the [Svelte quickstart](https://c15t.com/docs/frameworks/svelte/quickstart).
+The provider owns the loader and disposes it on unmount.
+
+**SvelteKit**
 
-### MatomoAnalyticsOptions
+Add the scripts to the existing root layout provider. Keep the server load
+and its serializable prefetch data from the [SvelteKit quickstart](https://c15t.com/docs/frameworks/sveltekit/quickstart).
 
-|Property|Value|
-|:--|:--|
-|Type Name|\`MatomoAnalyticsOptions\`|
-|Source Path|\`./packages/scripts/src/vendors/analytics/matomo-analytics.ts\`|
+```svelte title="src/routes/+layout.svelte"
+<script lang="ts">
+  import { ConsentManagerProvider, hosted } from '@c15t/svelte';
+  import { scripts } from '../consent-scripts';
 
-\*ExtractedTypeTable: Could not extract "MatomoAnalyticsOptions" from "./packages/scripts/src/vendors/analytics/matomo-analytics.ts" using base path "/home/runner/work/c15t/c15t". Verify the path/name and that the file is included by your tsconfig.\*
+  let { children, data } = $props();
+  const mode = hosted({ url: data.backendURL });
+</script>
 
-### Script
+<ConsentManagerProvider {mode} {scripts} prefetch={data.prefetch}>
+  {@render children()}
+  <!-- Keep your consent UI and preferences link here. -->
+</ConsentManagerProvider>
+```
+
+Import vendor helpers in the layout component, not in `+layout.server.ts`.
+For static hosting, keep your browser-only `mode` setup and omit request
+prefetch; the `scripts` prop stays the same. If you pass an externally owned
+`runtime` to the provider, register scripts when creating that runtime instead.
+
+**JavaScript**
 
-|Property|Value|
-|:--|:--|
-|Type Name|\`Script\`|
-|Source Path|\`./packages/core/src/libs/script-loader/types.ts\`|
+Attach the loader to your existing kernel before calling
+`kernel.commands.init()`:
+
+```ts
+import { createScriptLoader } from 'c15t/modules/script-loader';
+import { scripts } from './consent-scripts';
+
+const loader = createScriptLoader({ kernel, scripts });
+```
 
-\*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.\*
+Call `loader.dispose()` when that application instance is destroyed.
+`kernel` is the hosted kernel from your quickstart. A provider-owned kernel
+already has a loader; do not attach a second one. See
+[JavaScript script loading](https://c15t.com/docs/frameworks/javascript/script-loader).
+
+## Choose the loading mode
+
+| `defaultConsent` | Initial load                            | Later changes                                                            |
+| ---------------- | --------------------------------------- | ------------------------------------------------------------------------ |
+| Omitted          | Waits for measurement permission        | Removes the script on revocation; no Matomo consent callback             |
+| `'required'`     | Loads immediately with `requireConsent` | Signals `setConsentGiven` and `forgetConsentGiven`; keeps the SDK loaded |
+| `'given'`        | Loads immediately with an initial grant | Signals later changes; keeps the SDK loaded                              |
+
+Set `defaultConsent: 'required'` only when you intend the SDK to load before
+permission and let Matomo control tracking. Do not select `'given'` to make an
+opt-in setup start tracking before the visitor's choice. Matomo distinguishes
+[tracking consent from cookie consent](https://developer.matomo.org/guides/tracking-consent).
+
+With the default gated mode, removing the script does not stop a tracker that
+has already executed. Add a vendor stop strategy if later denial must stop all
+automatic tracking, or deliberately use Matomo's consent-signaling mode.
+
+## Options
+
+| Option                   | Behavior                                                                           |
+| ------------------------ | ---------------------------------------------------------------------------------- |
+| `siteId`                 | Defaults to `1`. Use your actual site ID.                                          |
+| `matomoUrl / cloudId`    | Base URL or Cloud identifier used to derive `matomo.js` and `matomo.php`.          |
+| `trackerUrl / scriptUrl` | Explicit endpoint overrides. Both are required if no base or Cloud ID is supplied. |
+| `trackPageView`          | Defaults to `true`. In required-consent mode, page views are queued on grants.     |
+| `enableLinkTracking`     | Defaults to `false`.                                                               |
+| `disableCookies`         | Defaults to `false`; cookie disabling does not select a loading mode.              |
+| `defaultConsent`         | Omitted by default. `'required'` and `'given'` enable consent signaling.           |
+
+## Verify the integration
+
+Check both the script and collection endpoints, especially with Cloud or proxy
+configuration. Test the chosen mode in a fresh session, grant measurement,
+revoke it, and inspect subsequent events. Check page-view counts during
+navigation and renewed grants. See [consent verification](../guides/verify-consent.md).