Concepts

IAB TCF

IAB TCF is for publishers and teams whose advertising, measurement, or monetization partners require the IAB Europe Transparency and Consent Framework.

For eligible Consent projects, Inth can provide the managed CMP layer for IAB TCF while your application keeps the c15t-rendered consent experience. That gives teams a hosted path instead of registering, operating, and maintaining their own CMP implementation directly.

The TCF requires CMPs to register with IAB Europe. Inth is registered as CMP ID 490, under its legal name, Consent Management Inc. TC strings saved through Inth carry CMP ID 490. The registration covers the web. It does not cover in-app or CTV.

What Inth provides

Inth manages the hosted platform layer around an IAB TCF consent project:

  • billing-controlled IAB TCF access
  • hosted policy resolution for TCF regions
  • vendor-list configuration in the consent project
  • Consent Sessions for region-aware runtime behavior
  • consent saves and durable consent records
  • trusted-origin checks for connected applications
  • operational support for unusual usage or consent-record behavior

Use Inth docs for the hosted CMP layer, project setup, plan requirements, trusted origins, policy packs, Consent Sessions, and consent records.

What your app provides

Your app still renders the banner, dialog, widgets, and surrounding consent UX with c15t.

Use c15t docs for frontend package setup, framework-specific components, styling, script loading, iframe blocking, internationalization, and the browser behavior of IAB TCF components.

When to enable IAB TCF

Enable IAB TCF when your consent program needs TCF signals for advertising, publishing, measurement, or vendor-level consent in covered regions.

Do not enable IAB TCF just because a site uses analytics. Standard consent policies are usually simpler when your partners do not require the IAB vendor framework.

Setup overview

  1. Create a Consent project.
  2. Use Consent Pro or Enterprise, which includes IAB TCF access.
  3. Configure trusted origins for the application.
  4. Configure IAB vendors and any required non-IAB disclosures.
  5. Use a policy pack that includes IAB TCF behavior for the regions that need it.
  6. Connect your c15t app to the hosted project.
  7. Save a test consent choice and confirm the consent record appears in Inth.

There is no separate project activation switch. With IAB access included in your plan and an IAB policy saved, the hosted /init response includes the Global Vendor List and managed CMP ID for visitors who match that policy. This also works from registered local-development origins, before the first consent save.

Pricing

IAB TCF is included with Consent Pro and Enterprise. It is not billed as a separate per-project add-on. See Pricing for the current public billing model.

Compliance boundary

Inth helps provide managed CMP infrastructure and recordkeeping for IAB TCF projects. Your organization still owns its privacy program, vendor selection, legal basis choices, disclosures, policy copy, and legal review.

Depending on your role, you may also have separate responsibilities as a publisher, vendor, advertiser, or other participant in the advertising ecosystem.

External references