Optional Client Configuration Parameters
In additional to the required client configuration parameters for a web implementation your organization can also utilize optional parameters for further customizations unique to your implementation. The optional client configuration parameters can be categorized into the following groups:

Optional overall client configuration parameters

In the table below, please find the available parameters for your implementation.
Optional configuration
Description
Data Type
authCookie
Allows your organization to configure a unique name for Sourcepoint's authId cookie. Click here for more information on authId.
String
campaignEnv
When set to stage, the implementation will default to campaigns configured in your stage campaign environment.
Note: This parameter defaults to your public campaign environment unless otherwise indicated.
String
isSPA
When set to true, will confirm the implementation for a single page application and will show a message only when window._sp_.executeMessaging();is triggered. Click here to learn more about single page application functions.
Boolean
joinHref
When set to true, will ensure that all directory regular expression functionality works in conjunction with the propertyHref parameter.
The joinHref parameter is solely used to test your implementation across different servers while still allowing for URL RegEx matching.
Boolean
targetingParams
Targeting params allow a developer to set arbitrary key/value pairs. These key/value pairs are sent to Sourcepoint servers where they can be used to take a decision within the scenario builder.
Note: targetingParams set at either within the ccpa or gdpr object will override this configuration.
targetingParams: {
key1: valueA, key2: valueB }
Object literal
1
//Example
2
window._sp_queue = [];
3
window._sp_ = {
4
config: {
5
accountId: 1584,
6
baseEndpoint: 'https://cdn.privacy-mgmt.com',
7
ccpa: { },
8
gdpr: { },
9
propertyHref: 'https://www.testdemo.com',
10
authCookie: 'test_uuid',
11
campaignEnv: 'stage',
12
isSPA: true,
13
joinHref: true,
14
targetingParams:{
15
darkmode: true
16
},
17
Copied!

Optional CCPA client configuration parameters

In the table below, please find the available parameters specific to CCPA. These parameters should be implemented within the ccpa: { } object.
Optional configuration
Description
Data Type
alwaysDisplayDNS
Setting this parameter to true enables use cases where a Sourcepoint Do Not Sell (my data) notification is hardcoded.
Boolean
targetingParams
Targeting params allow a developer to set arbitrary key/value pairs. These key/value pairs are sent to Sourcepoint servers where they can be used to take a decision within the scenario builder.
Note: targetingParams set within the ccpa object will override overall targetingParams.
targetingParams: {
key1: valueA, key2: valueB }
Object literal
1
//Example
2
window._sp_queue = [];
3
window._sp_ = {
4
config: {
5
accountId: 1584,
6
baseEndpoint: 'https://cdn.privacy-mgmt.com',
7
ccpa: {
8
alwaysDisplayDNS: false,
9
targetingParams:{
10
darkmode: true
11
}
12
},
13
gdpr: { },
14
propertyHref: 'https://www.testdemo.com',
Copied!

Optional GDPR client configuration parameters

In the table below, please find the available parameters specific to GDPR. These parameters should be implemented within the gdpr: { } object.
Optional configuration
Description
Data Type
consentLanguage
Ensure that the purposes or stack names listed in a consent message remain in the same language regardless of an end-user's browser language setting. Click here for a list of ISO 639-1 language codes.
If this parameter is absent, the stacks and purposes will appear according the user's preferred language.
String
groupPmId
Allows your organization to use the Privacy Manager ID for the property group's Privacy Manager ID.
Note: Call window._sp_.gdpr.loadPrivacyManagerModal() without passing a parameter and the Privacy Manager that displays will be that property's version of the groupPmId Privacy Manager.
Number
targetingParams
Targeting params allow a developer to set arbitrary key/value pairs. These key/value pairs are sent to Sourcepoint servers where they can be used to take a decision within the scenario builder.
Note: targetingParams set within the gdpr object will override overall targetingParams.
targetingParams: {
key1: valueA, key2: valueB }
Object literal
1
//Example
2
window._sp_queue = [];
3
window._sp_ = {
4
config: {
5
accountId: 1584,
6
baseEndpoint: 'https://cdn.privacy-mgmt.com',
7
ccpa: { },
8
gdpr: {
9
consentLanguage: "fi"
10
groupPmId: 123456,
11
targetingParams:{
12
darkmode: false
13
}
14
},
15
propertyHref: 'https://www.demotest.com',
Copied!
Last modified 5mo ago