ampproject / ampproject/amphtml

GetTCData will be deprecated in TCF v2.2

Open
#39,402 1 comment 0 reactions 0 assignees View on GitHub
Component: amp-consent INTENT TO DEPRECATE P1: High Priority Stale WG: analytics WG: components
Dominant language
JavaScript
Stars
14.9k
Forks
4.1k
PR merge metrics
No merged PRs in 30d

Description

### Summary

In TCF v2.2 GetTCData command will be deprecated. We need to update the framework, for example [here](https://github.com/ampproject/amphtml/blob/340454553f209850286635fd40cead3809131446/extensions/amp-consent/0.1/consent-info.js#L71)

### Motivation

TCF v2.2 will be in production around November 20th. There is [specifications](https://iabeurope.eu/wp-content/uploads/2023/07/230727-FAQ-_-TCF-v2.2-updated-27-July-2023.pdf) with number of changes.

### Impact on Existing Users

Using deprecated method that will be removed from IAB TCF library could brake scripts

### Alternative Implementation

N/A

### Additional Context

_No response_

### Notifications

/cc @ampproject/wg-approvers

Contributor guide

Open the contributing guide

Research direction

Start at extensions/amp-consent/0.1/consent-info.js around line 71 and compare the GetTCData usage with the linked TCF v2.2 specification. Find all affected framework references, update the deprecated calls, and verify that consent information still works with the current IAB TCF library.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.