@c15t/iab: IAB TCF 2.3 Addon

IAB TCF 2.3 addon for c15t with TC String generation, GVL support, TCF APIs, and programmatic advertising consent workflows.

Key Features

• IAB TCF 2.3 support for programmatic advertising consent
• TC String generation and storage
• Global Vendor List (GVL) support
• Purpose, special purpose, feature, special feature, and vendor controls
• Headless APIs for custom IAB consent experiences
• React UI integration through @c15t/react/iab

Prerequisites

• Node.js 18.17.0 or later
• c15t 2.x
• 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

Manual Installation

pnpm add @c15t/iab

For React UI components, use the @c15t/react IAB subpath and stylesheet:

import { IABConsentBanner, IABConsentDialog } from '@c15t/react/iab'

@import "@c15t/react/iab/styles.css";

Usage

1. Configure c15t with the IAB consent model for jurisdictions that require TCF workflows
2. Use the React IAB components for a prebuilt TCF banner and preference center
3. Use headless APIs when you need a custom IAB consent experience
4. For full implementation details, see the IAB TCF 2.3 docs

Documentation

For further information, guides, and examples visit the reference documentation.

Related Packages

• @c15t/react: React IAB consent banner, dialog, and hooks through @c15t/react/iab
• @c15t/backend: Backend configuration for IAB TCF, GVL, CMP registration, and custom vendors
• c15t: Core consent engine

Support

• Join our Discord community
• Open an issue on our GitHub repository
• Visit inth.com and use the chat widget
• Contact our support team via email [email protected]

Contributing

• We're open to all community contributions.
• Read our Contribution Guidelines
• Review our Code of Conduct
• Fork the repository
• Create a new branch for your feature
• Submit a pull request
• All contributions, big or small, are welcome and appreciated.

Security

If you believe you have found a security vulnerability in c15t, we encourage you to responsibly disclose this and NOT open a public issue. We will investigate all legitimate reports.

Our preference is that you make use of GitHub's private vulnerability reporting feature to disclose potential security vulnerabilities in our open-source software. To do this, please visit https://github.com/c15t/c15t/security and click the "Report a vulnerability" button.

Security Policy

• Please do not share security vulnerabilities in public forums, issues, or pull requests
• Provide detailed information about the potential vulnerability
• Allow reasonable time for us to address the issue before any public disclosure
• We are committed to addressing security concerns promptly and transparently

License

Apache License 2.0

Built by Inth