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

Expected: function.

If not available:

confirm CMP script loaded successfully

confirm no CSP block

confirm no duplicate or outdated CMP script

Expected: valid tcString after user choice.

Expected: event updates when consent state changes.

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

cmpStatus: stub persists (CMP did not initialize fully).

eventStatus never moves beyond loading state.

TC string present but stale after preference change.

Include:

Settings ID

affected URL

browser and version

output of checks from this page