Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update quebec guidance #5216

Merged
merged 6 commits into from
Mar 22, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 13 additions & 8 deletions features/ac-quebec.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,11 +15,16 @@ sidebarType: 7

## Overview

Starting September 2023, new privacy regulations came into effect in Quebec, a province of Canada, governing about a quarter of Canada's population.
Starting September 2023, new privacy regulations came into effect in Quebec, a province of Canada, which governs about a quarter of Canada's population.

IAB Canada has offered a modified version of the Transparency and Consent Framework (TCF) as a solution to cover user consent preferences in Quebec. However, at the time of this writing (Jan 2024), guidance from regulators, TCF Canada, and major advertising entities in Canada is in flux. The Canadian vendor list does not have enough vendors for meaningful adoption of the framework by any publisher, as it does not include the primary publisher ad server nor many large DSPs, nor many of the top five CMPs [registered as CMPs with TCF Canada](https://iabcanada.com/tcf-canada/cmp-list/).
IAB Canada has offered a modified version of the Transparency and Consent Framework (TCF) as a solution to cover user consent preferences in Quebec. However, as of Feb 2024, guidance from regulators, TCF Canada, and major advertising entities in Canada is still in flux. The Canadian [vendor list](https://iabcanada.com/tcf-canada/vendor-list/) does not have enough vendors for meaningful adoption of the framework by any publisher, as it does not include the primary publisher ad server nor many large DSPs. These CMPs are [registered as CMPs with TCF Canada](https://iabcanada.com/tcf-canada/cmp-list/).

Given this context, Prebid has identified publisher concern that many will not be able to transact programmatically in Quebec until broader adoption of the IAB TCF-Canada spec is achieved. This document is intended to provide guidance on conveying user notification and consent signals as gathered by the publisher to Prebid software independent of the GPP signals in Section 5 and the lack of a working consent string framework from IAB Canada.
Here is guidance from IAB Canada dated February 2024:

{: .alert.alert-info :}
CAI released new guidance in October 2023 but unfortunately, it did not clear up the confusion around whether or not expressed consent is required for personalized advertising. Conflicting interpretations of the statute remain and as a result, we are left with organizations taking different approaches based on their analysis. TCF Canada has the flexibility built in to allow for either approach and for it to be used across our market regardless of the form of consent you are collecting.

Given this context, Prebid has identified publisher concern that many will not be able to transact programmatically in Quebec until broader adoption of the IAB TCF-Canada spec is achieved. This document is intended to provide guidance on conveying user notification and consent signals as gathered by the publisher to Prebid software independent of the GPP signals in Section 5 and the lack of a consensus consent string framework from IAB Canada.

References:

Expand All @@ -29,9 +34,9 @@ References:

## TCF Canada and GPP Support in Prebid.js

Prebid.js supports a [GPP module](/dev-docs/modules/consentManagementGpp.html), but it does not interpret the strings in Section 5 (Canada). It simply takes the GPP signal from the CMP and includes it in outgoing network requests if those vendors initiating network requests have added support for GPP in their modules. It isn't clear if TCF Purpose 2 (consent to 'basic ad serving') or a vendor list will be critical parts of a Quebec consent framework. Also, it isn't clear if publishers will be required to seek vendor-level consent as for TCF-EU.
Prebid.js supports a [GPP module](/dev-docs/modules/consentManagementGpp.html), but it does not interpret the strings in Section 5 (Canada). It simply takes the GPP signal from the CMP and includes it in outgoing network requests if those vendors initiating network requests have added support for GPP in their modules. It isn't clear if TCF Purpose 2 (consent to 'basic ad serving') or a vendor list will be critical parts of a Quebec consent framework. Also, it isn't clear if publishers will be required to seek vendor-level consent as one does for TCF-EU.

Prebid.js is planning a TCF Canada module to react to the contents of the string, but it is not yet available, and may not be available on the date the law comes into effect. Instead, publishers may access their CMP or the consent preferences that their website visitors have expressed to them directly, and control Prebid.js activity. Below is an example of how the Prebid.js [Activity Control system](/dev-docs/activity-controls.html) could be used to implement an interim solution for ad serving in Quebec:
Prebid.js is planning a TCF Canada module to react to the contents of the string, but it is not yet available as of March 2024. Instead, publishers may access their CMP or the consent preferences that their website visitors have expressed to them directly, and control Prebid.js activity. Below is an example of how the Prebid.js [Activity Control system](/dev-docs/activity-controls.html) could be used to implement an interim solution for ad serving in Quebec:

```javascript
function isQuebecPersonConsentDenied() {
Expand Down Expand Up @@ -109,19 +114,19 @@ their Prebid Server host company.
allowactivities: {
syncUser: {
rules: [{
geo: ["CAN.QC"]
gpp_sid: 5
}],
allow: false
},
transmitUfpd: {
rules: [{
geo: ["CAN.QC"]
gpp_sid: 5
}],
allow: false
},
transmitPreciseGeo: {
rules: [{
geo: ["CAN.QC"]
gpp_sid: 5
}],
allow: false
}
Expand Down
Loading