User Matching

Please make sure that you activate the PreBid GDPR-Module (in case you are serving European traffic), the CMP-Module, and a properly configured user-matching configuration like the example below:

pbjs.setConfig({
    userSync: {
        filterSettings: {
            iframe: {
                bidders: ['connectad'],
                filter: 'include'
            }
        }
    }
});

Used-Matching Vendors

ConnectAd supports a range of different user-matching vendors. We recommend integrating at least one of them to ensure an optimized user-matching process and to be ready for a cookie-less future.

britepoolId
criteo
id5Id
identityLink
liveIntentId
netId
parrableId
pubCommonId
unifiedId

❗️
Missing User-Matching and/or missing consent data might lead to a total revenue loss!

IAB TCF

ConnectAd supports TCF 2.0 of the Transparency & Consent Framework and is registered as vendor 138 in the IAB Global Vendor List.

To process publisher bid requests, we require the following settings. Please consider that we do not process requests with missing/improper consent, and we do strictly respect no consent strings.

Purpose/feature	Legal Bases Required
Purpose 1 Store and/or access information on a device	Consent
Purpose 2 Select basic ads	Legitimate Interest, Consent (flexible)
Purpose 3 Create a personalised ads profile	Consent
Purpose 4 Select personalised ads	Consent
Purpose 7 Measure ad performance	Legitimate Interest, Consent (flexible)
Purpose 10 Develop and improve products	Legitimate Interest, Consent (flexible)
Special Feature 1 Use precise geolocation data	Consent
Special Purpose 1 Ensure security, prevent fraud, and debug	Legitimate Interest
Special Purpose 2 Technically deliver ads or content	Legitimate Interest
Feature 3 Receive and use automatically-sent device characteristics for identification

California Consumer Privacy Act (CCPA)

ConnectAd supports the processing and submission of CCPA strings in all its products: PreBid Client, PreBid Server, OpenRTB, ConnectTag.