Sourcepoint offers messaging capabiltiies to capture, store, and sync an end-user's marketing preferences via Preference Center messages. In this article, we will walk you through the essential steps to launch your Preference Center messaging campaign on your web property.
- Overview
- Portal configuration
- Install Preferences code on property
- Install resurface Preference Center message code on property
- Launch campaign
Note: The Preferences module is only available for properties that utilize the Unified script (i.e. are leveraging multi-campaign on properties)
Overview
Portal configuration
Use the table below to track the necessary configurations that need to be performed within the Sourcepoint portal before adding the required code onto the property and launching your Preferences campaign.
Note: There are certain optional steps/configurations that are not represented in this tracker such as property groups, dynamic language support, etc...
Step |
Resource(s) | |
1 | Create new property | |
2 | Set up integration in Preferences Integration Hub | |
3 | Category mapping in Preferences Configuration | |
4 | Create Preference Center message | |
5 | Create Preferences scenario | |
6 | Create Preferences partition set |
Install Preferences code on property
When you have completed the portal configuration for your property, click Properties on the left-hand panel and select Properties from the subsequent menu.
Click <> inline with the property name.
Use the dropdown menu to select Preferences. The implementation code snippet will automatically populate in the provided space.
Click Copy Code and add the implementation code snippet to your property.
Note: Click here for best practices on how to implement the Sourcepoint implementation code snippet to optimize message loading time.
The Sourcepoint Preferences implementation code snippet is comprised of two scripts. Review the sections below for additional information and possible configuration options to suit your organization's use cases.
<script>
window._sp_queue = [];
window._sp_ = {
config: {
accountId: 1584,
baseEndpoint: 'https://cdn.privacy-mgmt.com',
preferences: {
id: 'email@testdemo.com'
},
propertyId: 123456,
events: {
onMessageChoiceSelect: function() {
console.log('[event] onMessageChoiceSelect', arguments);
},
onMessageReady: function() {
console.log('[event] onMessageReady', arguments);
},
onMessageChoiceError: function() {
console.log('[event] onMessageChoiceError', arguments);
},
onPrivacyManagerAction: function() {
console.log('[event] onPrivacyManagerAction', arguments);
},
onPMCancel: function() {
console.log('[event] onPMCancel', arguments);
},
onMessageReceiveData: function() {
console.log('[event] onMessageReceiveData', arguments);
},
onSPPMObjectReady: function() {
console.log('[event] onSPPMObjectReady', arguments);
},
onConsentReady: function (consentUUID, euconsent) {
console.log('[event] onConsentReady', arguments);
},
onError: function() {
console.log('[event] onError', arguments);
},
}
}
}
</script>
<script src='https://cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js' async</script>
Client configuration script
The client configuration script contains your organization's specific account configuration parameters. This configuration includes the necessary and optional parameters for your property to communicate with the Sourcepoint messaging platform and consent service libraries.
Currently, there are four required parameters to successfully deliver an end-user notification:
Parameter | Data Type | Description |
accountId |
Number | The accountId value associates the property with your organization's Sourcepoint account. Your organization's accountId can be retrieved by contacting your Sourcepoint Account Manager or via the My Account page in your Sourcepoint account. |
baseEndpoint |
String |
A single server endpoint that serves the messaging experience. https://cdn.privacy-mgmt.com. |
preferences |
Object | Indicates that the messaging campaign is for Preferences. Accepts an id property which is the end-user's email address. |
property reference | -- | Use either propertyHref or propertyId depending on your use case to map the implementation to a specific property. Click here for more information on these parameters. |
In addition to the required parameters (above), your organization can further implement additional parameters and customizations in the code snippet for different use cases. Follow the resources below for additional information:
window._sp_queue = [];
window._sp_ = {
config: {
accountId: 1584,
baseEndpoint: 'https://cdn.privacy-mgmt.com',
preferences: {
id: 'email@testdemo.com'
},
propertyId: 123456,
...
URL to messaging library
The final script is a URL that points to Sourcepoint's messaging libraries. The default URL is as follows and only needs to be included once regardless of how many different types of messaging campaigns you run on the property:
Note: If your organization has edited the baseEndpoint
with a CNAME DNS record you will also need to edit the URL. Please follow the following format if necessary:
https://cname.subdomain/unified/wrapperMessagingWithoutDetection.js
In the developer console, the URL to the messaging library can return the following regardless of whether a message was shown to the user:
Console | Description |
Messaging without detection successfully executed |
The script, messaging without detection, has successfully fired. It does not indicate that a message was shown to the end-user. |
interaction complete |
The interaction with our, messaging without detection script, has concluded. It does not indicate that an end-user interacted with a message. |
Install resurface Preference Center message code on property
Many organizations will want to add a button/link onto their web property that allows an end-user to resurface the Preference Center message so they can manage their marketing preferences on an ongoing basis.
Typically, the JavaScript code on their page will attach the function to the onclick
event of a page element. Click here for more information on how to implement the JavaScript code.
Launch campaign
With the property configured in the portal and Sourcepoint's implementation code snippet added to the web property, your organization can now launch a Preferences campaign on the property.
Step | Resources |
Launch Preferences campaign |
Comments
0 comments