|
Permissions: |
• Vendor list - U.S. Privacy |
Global Privacy Control (GPC) is a technical specification for transmitting universal opt-out signals. The initiative is backed by a consortium of privacy-focused organizations such as the Brave browser and DuckDuckGo. For now, the signal is tailored for California’s Consumer Privacy Act (CCPA), which gives Californians the right to opt-out of the sale of their data.
In this article, we will cover how to respect the GPC signal for U.S. Privacy messaging campaigns (to which CCPA belongs), and different scenario configurations your organization can utilize in regards to the GPC signal.
Note: The group behind GPC also has hopes to develop a global standard compatible with other privacy regimes like the EU’s GDPR. Currently, Sourcepoint only supports GPC signals for U.S. Privacy messaging campaigns.
Respect GPC signal
In order to respect the GPC signal your organization will need to enable the Respect Global Privacy Control setting on your U.S. Privacy Standard vendor list. This setting will apply to all properties associated with the U.S. Privacy Standard vendor list.
Click Vendor Management on the left-hand rail and select U.S. Privacy Standard from the subsequent menu.
Select a U.S. Privacy vendor list on the following page to edit.
Click Advanced Settings.
Enable the Respect Global Privacy Control setting in the subsequent modal and click Apply changes.
Click Save on the vendor list builder page when finished to confirm the edit(s).
All properties associated with this specific U.S. Privacy vendor list (in this case CCPA) will respect an end-user's GPC signal. See below for how an end-user's GPC signal affects the US Privacy String.
The end-user's GPC signal will affect their US Privacy String. The uspString will default to 1YYN (opted-out of the sale of their personal information).
{version: 1, uspString: '1YNN', newUser: false, dateCreated: '2022-08-04T14:04:43.139Z', gpcEnabled: false}
dateCreated: "2022-08-04T14:04:43.139Z"
gpcEnabled: true
newUser: false
uspString: "1YYN" //opted-out setting for US Privacy String
version: 1
Note: Click here for more information about retrieving and reading the US Privacy String.
The end-user's GPC signal will have no impact on their US Privacy String. By default, the end-user's uspString will be 1YNN(opted-into the sale of their personal information) unless the end-user makes adjustments to their user consents in your property's U.S. Privacy privacy manager (CCPA privacy manager).
{version: 1, uspString: '1YNN', newUser: false, dateCreated: '2022-08-04T14:04:43.139Z', gpcEnabled: false}
dateCreated: "2022-08-04T14:04:43.139Z"
gpcEnabled: false
newUser: false
uspString: "1YNN" //default setting for US Privacy String
version: 1
Note: Click here for more information about retrieving and reading the US Privacy String.
GPC scenario condition
When an end-user has a GPC signal enabled, the gpcEnabled property in the getUSPData object will be set to true. If an end-user does not have a GPC signal enabled then gpcEnabled will be set to false.
{version: 1, uspString: '1YNN', newUser: false, dateCreated: '2022-08-04T14:04:43.139Z', gpcEnabled: false}
dateCreated: "2022-08-04T14:04:43.139Z"
gpcEnabled: true //end-user has GPC signal enabled
newUser: false
uspString: "1YYN"
version: 1
The boolean value of the gpcEnabled property can be used to drive targeted messages via the GPC Gate scenario condition.
Example
Your organization may want to target end-users who have a GPC signal enabled on their browser to acknowledge the signal and relay the status of their US Privacy String based on this signal.
As always, please speak with your legal team and your Sourcepoint account manager to determine the best scenario strategies for your organization.
Note: The following instructions assume that you have configured the requisite U.S. Privacy messages and privacy managers for CCPA that your organization wishes to display to an end-user for when a GPC signal is enabled and disabled. Additionally, this article assumes that the property has an existing U.S. Privacy scenario for CCPA. Click here to review generalized information on building scenarios.
To utilize a GPC gate in a U.S. Privacy scenario for CCPA on a property, select Properties on the left-hand rail and then click Properties from the subsequent menu.
Select a property from the list that is associated with the U.S. Privacy vendor list for which you are respecting the GPC signal.
Select Scenarios from the property navigation bar and click the edit icon inline with a U.S. Privacy scenario for CCPA to which you wish to add the GPC gate.
| Condition | Value | Description |
| GPC Gate | enabled | The end-user has a GPC signal enabled on their browser |
| disabled | The end-user does not have a GPC signal enabled on their browser |
Click Add when finished.
Your configured message will display dependent upon the end-user's GPC signal and any other conditions you have configured. In the example below, we are showing two different messages to end-users who are accessing our property from California depending on their GPC signal.
