RevContent can collect privacy, consent, and consumer choice signals directly from a publisher’s digital properties through the RevContent Services (i.e. widgets) and honors provided signals in line with the IAB’s Transparency and Consent Framework ("TCF"). However, it is the publisher’s obligation to ensure that the Services can properly receive and process all applicable signals; especially in instances where such signals are required, including GDPR in Europe and CCPA in California.
In cases where the publisher is unable or unwilling to host a user consent mechanism on their site, RevContent can, upon request, provide Services limited to core widget functionality only (meaning advertisements have not been personalized through user’s UUID, IP address, or similar).
To serve personalized advertisements through RevContent Services to users from regions in which consent to such is required, publishing partners must ensure that these signals are provided to RevContent through either one of two means: 1) integrating an IAB-approved consent management platform (“CMP”) found on this list or 2) passing consent signals directly.
GDPR
For partners leveraging the preferred method of an approved CMP for GDPR consent exchange, RevContent supports both TCF v1 and TCF v2 ( __cmp and __tcfapi respectively) although it’s important to note that TCF v1 has been officially deprecated by the IAB.
Those who are unable to use a CMP can pass consent signals to RevContent directly by including the optional data attributes gdpr and gdpr_consent within the widget script, as further outlined below:
API Widgets
Add the attributes gdpr and gdpr_consent along with valid values for placeholders <GDPR> and <GDPR_CONSENT>
http://trends.revcontent.com/api/v1/?api_key=&pub_id=&widget_id=&domain=&format=json&sponsored_count=25&gdpr=<GDPR>&gdpr_consent=<GDPR_CONSENT>
Standard Widgets
Add the attributes data-gdpr and data-gdpr-consent along with valid values for placeholders <GDPR> and <GDPR_CONSENT>
<div
data-rc-widget
data-endpoint="trends.revcontent.com"
data-gdpr="<GDPR>"
data-gdpr-consent="<GDPR_CONSENT>">
</div>
<script src="https://assets.revcontent.com/master/delivery.js" defer="defer"></script>
CCPA
For partners leveraging the preferred method of an approved CMP for CCPA consent exchange, RevContent supports usage of the IAB's US Privacy User Signal API (__uspapi).
Those who are unable to use a CMP can pass consent signals to RevContent directly by including the optional data attribute us_privacy within the widget script, as further outlined below:
API Widgets
Add the attribute us_privacy along with a valid value for the placeholder <CCPA_STRING>
http://trends.revcontent.com/api/v1/?api_key=&pub_id=&widget_id=&domain=&format=json&sponsored_count=25&us_privacy=<CCPA_STRING>
Standard Widgets
Add the attribute data-us-privacy along with a valid value for the placeholder <CCPA_STRING>
<div
data-rc-widget
data-endpoint="trends.revcontent.com"
data-us-privacy="<CCPA_STRING>">
</div>
<script src="https://assets.revcontent.com/master/delivery.js" defer="defer"></script>
Upon widget load, consent provider API is called with a timeout of 200ms. When no consent string is shared for a user from a market where it’s necessary, RevContent will presume no consent has been given and only core widget functionality is applied.
GPP
Additionally, in support of the effort to consolidate consent management across multiple jurisdictions, TCF 2.2 ( __gpp) is supported by RevContent Services as part of the IAB’s Global Privacy Platform (“GPP”). Our API also supports query parameters gpp and gpp_sid or if you prefer using script attributes, you can set data-gpp and data-gpp-sid, as further defined below:
Additional Relevant Articles
CCPA Data Request & Deletion API
IAB GDPR Compliance Guide
Consent Management Provider JavaScript API v1.1
Consent Management Platform JavaScript API v2