Skip to content

IAB TCF 2.3 Implementation

Last updated: March 18, 20267 min readAdvancedBrandDeveloper

The IAB TCF 2.3 is a standardized framework for communicating consent choices to ad tech vendors. Arqam360 supports TCF 2.3 to help you comply with programmatic advertising requirements.

What is TCF 2.3?

The Transparency and Consent Framework v2.2 is an industry standard by IAB Europe. It provides a common language for communicating consent to advertising vendors, ensuring they receive and respect user choices.

TCF Purposes

  • Purpose 1: Store/access information on a device
  • Purpose 2: Select basic ads
  • Purpose 3: Create a personalized ads profile
  • Purpose 4: Select personalized ads
  • Purpose 5: Create a personalized content profile
  • Purpose 6: Select personalized content
  • Purpose 7: Measure ad performance
  • Purpose 8: Measure content performance
  • Purpose 9: Apply market research to generate audience insights
  • Purpose 10: Develop and improve products
1

Enable TCF in configuration

Add tcfEnabled: true to your widget configuration.

2

Map categories to purposes

Arqam360 maps your consent categories to TCF purposes automatically.

3

Test the __tcfapi

Verify window.__tcfapi is available and returning correct TC strings.

javascript
<script src="https://cdn.arqam360.com/widget-v2.js"
  data-key="YOUR_API_KEY"
  data-tcf-enabled="true"></script>

Testing TCF

Open your browser console and run: window.__tcfapi('getTCData', 2, function(data) { console.log(data); }). You should see the TC string and consent data.

Arqam360 implements IAB TCF 2.3 — a real TC string with Core and DisclosedVendors segments, tcfPolicyVersion 5, persisted to the euconsent-v2 cookie — but is not a registered CMP with IAB Europe. Registration costs EUR 1,575/year and issues the numeric CMP ID that vendors use to attribute a consent string; until we hold one the widget reports CMP ID 0 rather than claiming another CMP's identity. It is also the prerequisite for Google's CMP certification. Talk to us if this blocks an ad-tech integration you need.

Was this article helpful?