TCF API Validation

Last updated: February 18, 2026

Use this guide to verify that TCF API signals are available and consistent.

1. Validate __tcfapi Availability

typeof window.__tcfapi

Expected: function.

If not available:

• confirm CMP script loaded successfully
• confirm no CSP block
• confirm no duplicate or outdated CMP script

2. Validate TC String Read

window.__tcfapi('getTCData', 2, (data, ok) => {
  console.log({ ok, tcString: data && data.tcString, eventStatus: data && data.eventStatus });
});

Expected: valid tcString after user choice.

3. Validate Event Updates

window.__tcfapi('addEventListener', 2, (data, ok) => {
  if (ok) console.log('TCF event:', data.eventStatus, data.tcString);
});

Expected: event updates when consent state changes.

4. Validate Disclosed Vendors Segment (High Level)

For enterprise reviews, confirm that your decoder or verification tool indicates disclosed vendor information is present for configured vendor sets.

5. Common Errors

• cmpStatus: stub persists (CMP did not initialize fully).
• eventStatus never moves beyond loading state.
• TC string present but stale after preference change.

6. Support Escalation Data

Include:

• Settings ID
• affected URL
• browser and version
• output of checks from this page
• debug report from Cybexo Debug Tool