SDK DocumentationRecipesAnnouncementsSupport Forum
AndroidiOSAnnouncementsSupport Forum


Taboola Android SDK and the CCPA

On January 1st, 2020, the CCPA (California Consumer Privacy Act) will come into effect. The CCPA introduces a six months compliance grace period for publishers, making forcible from July 1st, 2020. Taboola takes considerable efforts to ensure that its SDK complies with the CCPA privacy practices, CCPA data protection instructions, and the industry's best practices to support it.

Working with the IAB CCPA Framework

Taboola added support for the IAB CCPA Framework ("IABUSPrivacy_String") in Android SDK version 2.4.0. Please make sure you are using this SDK version or above.

Passing CCPA status directly to Taboola SDK

It is possible to forward the CCPA "Do Not Sell" (dns) status to Taboola SDK on each time the widget/feed is initialized using a dedicated flag - cdns The value (in string format) should be passed on each SDK session.

  • true - CCPA applies, and the end-user didn't provide agreement to use the personal data per CCPA regulations (Do not sell is true)
  • false - CCPA applies, and the end-user provide agreement to use the personal data per CCPA regulations (Do not sell is false)
  • none - CCPA does not apply (the default status)

By default, the value of this flag is set to none - the end-user is not CCPA subject, allowing Taboola to use the user's data. It is recommended to place these lines alongside the other settings, such as publisher name, etc

//Setting taboolaWidget object
HashMap<String, String> extraProperties = new HashMap<>();
<!-- in the body tag add user_opt_out to the JS tag -->
<div id="container-id"></div>
<script type="text/javascript">
   window._taboola = window._taboola || [];
   _taboola.push({mode: "mode-name",
   	container: "container-id",
   	placement: "Placement Name",
        cdns: "false", 
   	target_type: 'mix'});
   _taboola["mobile"] = window._taboola["mobile"] || [];