Integration Guides
Choose the integration method that fits your stack. All methods use the same 1Consent dashboard for configuration.
Connect your AI assistant
Set up Lovable, Cursor, Claude, Codex or ChatGPT, choose app permissions, and recover missing MCP tools.
Lovable & AI assistants
Connect the production MCP with an approved account to retrieve app installation instructions and authorized design context.
Script Tag
The universal install — one <script> tag on any website, no build step.
WordPress
Install the official 1Consent plugin — no code required.
React
Use @1consent/react for typed services and consent gates in your React application.
Next.js
Use @1consent/nextjs with an App Router provider, client gates, and optional server hints.
Google Tag Manager
Gate Google and non-Google tags behind consent with Consent Mode v2 and the 1consent:consent dataLayer event.
Which one should I use?
- Script Tag is the universal method — it works on any website, with or without a framework. Start here if you're unsure.
- WordPress wraps the script tag in a plugin so there's no code to add.
- React adds typed service names and consent gates for React applications. Render timing depends on the app and its available consent and configuration.
- Next.js covers App Router setup, client components and the limits of server-side consent hints.
- Google Tag Manager is not an install method — it's a companion guide for gating tags in GTM once 1Consent is installed with any of the above.
All methods use the same 1Consent dashboard for configuration.
Connect your coding assistant
Follow Connect your AI assistant for client-specific setup in Lovable, Cursor, Claude, Codex and ChatGPT. It covers the production server URL, app selection, permissions, a first successful account read, and missing-tool recovery. The Lovable guide continues with installation in your project.
Choose the intended app and grant the minimum scopes needed for the task. Installation uses context and app-configuration reads; design and analytics reads are separate permissions. Keep OAuth credentials in the assistant connection, outside your visitor-facing app.
The assistant edits your project using the returned guidance. Theme drafts, framework assignment and private runtime previews require separately approved capabilities. A hosted MCP Live publication needs your separate review and approval of the exact proposal in the Dashboard before execution. Review the changes and verify fresh rejection, a partial grant, withdrawal and navigation against the app's actual trackers.