Sourcepoint offers messaging capabilities for multiple regulatory and non-regulatory frameworks. These messages are surfaced to your end-users in accordance with the campaigns (and scenarios) that you enable for the property.
In this article, we will walk you through the essential steps to launch your U.S. Privacy (Legacy) messaging campaign on your mobile property (either iOS or Android).
- Overview
- Portal configuration
- Configure Sourcepoint mobile SDK
- Configure resurface privacy manager link/button
- Launch campaign
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 U.S. Privacy (Legacy) 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 | Create U.S. Privacy (Legacy) vendor list | |
3 | Edit U.S. Privacy (Legacy) vendor list | |
4 | Create U.S. Privacy (Legacy) privacy manager | |
Create U.S. Privacy (Legacy) first layer message | ||
6 | Create U.S. Privacy (Legacy) scenario | |
7 | Create U.S. Privacy (Legacy) partition set |
Configure Sourcepoint mobile SDK
All of the configuration details are included in the README.md
files in each respective SDK. Please review this file for all the necessary and optional configurations needed to set up the SDK in your app property.
Configure resurface privacy manager link/button
Many organizations will want to add a button/link onto their web property that allows an end-user to resurface the privacy manager so they can manager their consent preferences on an ongoing basis. Additional information can be found in the iOS and Android SDKs, respectively:
You can load the privacy manager any time, programmatically, by calling:
.loadCCPAPrivacyManager(withId: String, tab: SPPrivacyManagerTab = .Default)
You can load the privacy manager any time, programmatically, by calling:
Kotlin
spConsentLib.loadPrivacyManager(
"<PM_ID>",
PMTab.PURPOSES,
CampaignType.CCPA,
MOBILE
)
Java
spConsentLib.loadPrivacyManager(
"<PM_ID>",
PMTab.PURPOSES,
CampaignType.CCPA,
MOBILE
));
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 U.S. Privacy (Legacy) campaign on the property and test the end-user flow.
Step | Resource(s) |
Launch U.S. Privacy (Legacy) campaign | |
Test end-user consent |
Comments
0 comments