Integrating Consent with OpenX Outside of TCF

This article is for users that need to action consent manually outside of the IAB TCF framework.

OneTrust is an IAB compliant Universal Consent & Preference Management Platform (CMP). As a CMP, OneTrust collects and stores information from consenting users on behalf of a publisher and passes that information to ad exchanges and demand partners.

To be compliant with GDPR, publishers may need to make modifications to their OpenX integrations. For each of the OpenX Ad Exchange integrations below there is guidance on how to achieve this compliance.

Integrations

Prebid Adapters

Requirements:

  • TCF v2 version 2.43+

  • Enabled EU GDPR consent management module in Prebid

We recommend using the latest OpenX Prebid adapter though this is not a requirement.

The EU GDPR consent management module in Prebid gets the data on a user’s GDPR and Google additional consent preferences from OneTrust Prebid reads this data and runs content accordingly.

  1. Insert the OneTrust Cookie banner script above the Prebid.js code in the page header.

  2. In the setConfig() call, add an object called consentManagement so that Prebid adapters that support the GDPR consent management module will collect consent data and make requests accordingly.

Click here for examples.

In addition to the consent management module, Prebid has an optional GDPR enforcement module that allows you to define which activities should be enforced on a page at the Prebid.js level. Based on the consent data in the TCF string data, the GDPR enforcement module then enforces these specified activities.

Click here for a list of Prebid.js activities that are within the scope of TCF.  Within a given page publishers must define configuration rules regarding how each of the in-scope Prebid.js activities should be enforced. Click here for examples.

OpenRTB Bid Requests

For both website and mobile apps, add both of the following fields to all bid requests that are sent to OpenX.

  • bidrequest.regs.ext.gdpr

  • user.ext.consent

Click here for reference.

Google Open Bidding

No changes to this integration are necessary for compliance with IAB TCF v2 and GDPR.

OpenX Bidder Lite

Confirm that your code base is on the latest version. Replace your code base with the latest version. For more information, please visit the OpenX Community.

JavaScript Tag for Web

No changes are necessary for this integration for compliance with IAB TCF v2 and GDPR.

OpenX Mobile SDK

Upgrade to version 4.7.0+ for Android and iOS.

Ad Request Parameters

OpenX supports the following ad request parameters related to GDPR:

Parameter

Description

gdpr

  • 0 = false (request is not subject to GDPR)

  • 1 = true (request is subject to GDPR)

gdpr_consent

The consent string indicates a user’s consent status regarding all vendors that are active on a publisher’s site.

Click here to learn more.

Attention:

It is not possible to pass GDPR consent signals in MoPub JavaScript Tags.

To learn more