You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: TCFv2/IAB Tech Lab - CMP API v2.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -727,6 +727,7 @@ The steps for integrating a CMP SDK into an app are the following:
727
727
|`IABTCF_TCString`|`String`: Full encoded TC string |
728
728
|`IABTCF_VendorConsents`|`Binary String`: The `'0'` or `'1'` at position **n** – where **n**'s indexing begins at `0` – indicates the consent status for Vendor ID **n+1**; `false` and `true` respectively. eg. `'1'` at index `0` is consent `true` for vendor ID `1`|
729
729
|`IABTCF_VendorLegitimateInterests`|`Binary String`: The `'0'` or `'1'` at position **n** – where **n**'s indexing begins at `0` – indicates the legitimate interest status for Vendor ID **n+1**; `false` and `true` respectively. eg. `'1'` at index `0` is legitimate interest established `true` for vendor ID `1`|
730
+
|`IABTCF_DisclosedVendors`|`Binary String`: The `'0'` or `'1'` at position **n** – where **n**'s indexing begins at `0` – indicates the status of disclosure in CMP for Vendor ID **n+1**; `false` and `true` respectively. eg. `'1'` at index `0` is vendor disclosed `true` for vendor ID `1`|
730
731
|`IABTCF_PurposeConsents`|`Binary String`: The `'0'` or `'1'` at position **n** – where **n**'s indexing begins at `0` – indicates the consent status for purpose ID **n+1**; `false` and `true` respectively. eg. `'1'` at index `0` is consent `true` for purpose ID `1`|
731
732
|`IABTCF_PurposeLegitimateInterests`|`Binary String`: The `'0'` or `'1'` at position **n** – where **n**'s indexing begins at `0` – indicates the legitimate interest status for purpose ID **n+1**; `false` and `true` respectively. eg. `'1'` at index `0` is legitimate interest established `true` for purpose ID `1`|
732
733
|`IABTCF_SpecialFeaturesOptIns`|`Binary String`: The `'0'` or `'1'` at position **n** – where **n**'s indexing begins at `0` – indicates the opt-in status for special feature ID **n+1**; `false` and `true` respectively. eg. `'1'` at index `0` is opt-in `true` for special feature ID `1`|
+[What if consent is governed differently in a country?](#what-if-consent-is-governed-differently-in-a-country)
29
29
+[What happened to Created and LastUpdated?](#what-happened-to-created-and-lastupdated)
30
+
+[Why was support for legitimate interest for purposes 3 to 6 deprecated?](#why-was-support-for-legitimate-interest-for-purposes-3-to-6-deprecated)
31
+
+[Why was the disclosed vendors section made mandatory in TCF 2.3?](#mandatory_in_2_3)
30
32
*[Creating a TC String](#creating-a-tc-string)
31
33
+[How should a Transparency & Consent String be stored?](#how-should-a-transparency--consent-string-be-stored)
32
34
+[What are the Purposes and Features being supported?](#what-are-the-purposes-and-features-being-supported)
@@ -330,6 +332,10 @@ The Created and LastUpdated fields previously corresponded to decisecond timesta
330
332
331
333
In order to strengthen the TCF as a standard within the industry it was decided with version 2.2 to prohibit reliance on Legitimate Interest for purpose 3 (create a personalised ads profile), purpose 4 (select personalised ads), purpose 5 (create a personalised content profile) and purpose 6 (select personalised content).
332
334
335
+
### Why was the disclosed vendor section made mandatory in TCF 2.3?<aname="mandatory_in_2_3"></a>
336
+
337
+
To solved the abiguity issue for vendors declaring only special purposes (no purposes under consent and purposes under legitimate interest or only purposes under consent, for which cases we used the LI signal as the identifier for special purpose) we have re-introduced the disclose vendor section to specificaly declare which vendors have been disclosed through the CMP. This way there is no abiguity regarding a vendor only declaring special purposes being disclosed or not. If a vendor declaring only special purposes is not listed in the disclosed vendor list that vendor cannot operate under the specisl purpose.
338
+
333
339
## Creating a TC String
334
340
335
341
The following details provide information on creating, storing, and managing a TC String.
0 commit comments