1. CMP IAB Compliant
2. CMP non IAB Compliant

ℹ️ To help publishers comply with relevant data protection and privacy regulations, the Teads inApp SDK offers various ways to provide user consent during ad server requests.

CMP IAB Compliant

Do not require any additional configuration.

If you have a consent management platform (CMP) compliant with the IAB GDPR specifications, IAB CCPA specifications and IAB GPP specifications, good news,
Teads inApp SDK is able to retrieve the user consent signals by itself through the Android shared preferences.

CMP non IAB Compliant

Requires additional configuration.

If your CMP is not IAB compliant (or not installed), you'll need to manually provide the status and user consent at every ad request.

GDPR

Use the userConsent method from the AdPlacementSettings Builder.

TCFv1

The param subjectToGDPR should be:

• 1 if the traffic or the publisher is in the EEA (European Economic Area),
• 0 if it is not

AdPlacementSettings.Builder() 
  .userConsent(subjectToGDPR, "consent", TCFVersion.V2, cmpSdkId) // The user consent following the IAB specifications
  .build()

TCFv2

The param subjectToGDPR should be:

• 1 if the traffic or the publisher is in the EEA (European Economic Area),
• 0 if it is not

AdPlacementSettings.Builder() 
  .userConsent(subjectToGDPR, "consent", TCFVersion.V2, cmpSdkId) // The user consent following the IAB specifications
  .build()

CCPA

Use the setUsPrivacy method from the AdPlacementSettings Builder:

AdPlacementSettings.Builder() 
  .setUsPrivacy("consent") // The user consent following the IAB specifications
  .build()

GPP

Use the setGppConsent method from the AdPlacementSettings Builder:

AdPlacementSettings.Builder() 
  .setGppConsent("consent", "sectionIds") // The user consent following the IAB specifications
  .build()