The following page provides information for publishers that implemented a TCF CMP in their game, and work with Tapjoy’s SDK. To support publishers that implement a TCF CMP, Tapjoy exposes a consent API in its SDK, which allows the publisher to share the user’s choice with the Tapjoy SDK.
If you use Google UMP (Google’s CMP), or other CMPs that support Google’s Additional Consent (Google’s solution for non-registered TCF vendors), complete the necessary configurations on the AdMob platform. If you are using other CMPs that are not Google UMP, please read the instructions of such CMPs on how to set the Google Additional Consent. Make sure that “ironSource Mobile” is included in Google’s Additional Consent. Set the consent API exposed by the Tapjoy SDK based on the consent value stored in the AC String for “ironSource Mobile”.
If you are not using Google UMP, or other CMPs that support Google’s Additional Consent , you will need to set Tapjoy as a custom vendor based on the instructions from the CMP. Set the consent API exposed by the Tapjoy SDK based on the consent value stored by the CMP for Tapjoy.