• Vendor list - CCPA
• Campaign entities

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 CCPA messaging campaigns, 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 CCPA messaging campaigns. 

Respect GPC signal (CCPA)

In order to respect the GPC signal your organization will need to enable the Respect Global Privacy Control setting on your CCPA vendor list. This setting will apply to all properties associated with the CCPA vendor list. 

Click Vendor Management on the left-hand rail and select CCPA Standard from the subsequent menu. 


Select a CCPA 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 CCPA vendor list will respect an end-user's GPC signal. See below for how an end-user's GPC signal affects the US Privacy String.

End-user with GPC enabled End-user with GPC disabled

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.

GPC scenario condition (CCPA)

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.


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 CCPA messages and privacy managers 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 CCPA scenario. Click here to review generalized information on building scenarios.

To utilize a GPC gate in a CCPA message scenario 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 a CCPA 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 CCPA scenario to which you wish to add the GPC gate.


From a scenario step, click Add Condition


Use the Conditions dropdown menu to select GPC Gate. Select whether the condition's value should be set to enabled or disabled

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.


Add any other necessary conditions, delays, etc... and finally navigate to the Select Message dropdown menu to choose the message that will be displayed when an end-user satisfies the GPC Gate scenario (along with any other conditions you have configured).

Click Update 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. 



Was this article helpful?
0 out of 0 found this helpful