Passa al contenuto principale

Aggiungere ConsentForge a Next.js

Opzione 1: Componente Script (consigliato)​

Usate il componente <Script> di Next.js con strategy="beforeInteractive" per assicurarvi che ConsentForge si carichi prima di qualsiasi altro script:

// app/layout.tsx (App Router) o pages/_document.tsx (Pages Router)
import Script from 'next/script'

export default function RootLayout({ children }) {
  return (
    <html>
      <head>
        <Script
          src="https://cdn.consentforge.com/consentforge.min.js"
          data-token={process.env.NEXT_PUBLIC_CONSENTFORGE_TOKEN}
          strategy="beforeInteractive"
        />
      </head>
      <body>{children}</body>
    </html>
  )
}

Opzione 2: _document.tsx (Pages Router)​

import { Html, Head, Main, NextScript } from 'next/document'

export default function Document() {
  return (
    <Html>
      <Head>
        <script
          src="https://cdn.consentforge.com/consentforge.min.js"
          data-token={process.env.NEXT_PUBLIC_CONSENTFORGE_TOKEN}
          defer
        />
      </Head>
      <body>
        <Main />
        <NextScript />
      </body>
    </Html>
  )
}

Bloccare script di terze parti​

Usate strategy="lazyOnload" per gli script che richiedono consenso — non si caricheranno fino a quando il consenso non viene dato e ConsentForge li rilascia:

<Script
  src="https://www.googletagmanager.com/gtag/js?id=G-XXXXX"
  data-consent-category="analytics"
  strategy="lazyOnload"
/>

Variabili di ambiente​

Aggiungete a .env.local:

NEXT_PUBLIC_CONSENTFORGE_TOKEN=cf_live_your_token_here

TypeScript: tipi window di ConsentForge​

// types/consentforge.d.ts
interface Window {
  ConsentForge: {
    openPreferenceCenter: () => void;
    getConsent: (category: string) => boolean;
    on: (event: string, callback: (data: unknown) => void) => void;
  }
}