Getting Started with Privacy Manager for CCPA
Thank you for trusting LiveRamp to help you with your CCPA compliance needs! We recognize this was probably a lengthy selection process, and we value your business. We also recognize CCPA can be confusing. We’ve put together this suggested project plan to help you ensure you are gathering the right internal stakeholders and information needed for a successful and timely implementation of Privacy Manager.
Once you’ve ticked off all of the boxes applicable to your business, you will be ready to set up Privacy Manager for CCPA.
Stakeholders: Who do I need?
Before implementing the Privacy Manager, you will want to assemble your all-star Consent Management Platform team. While stakeholders you need to include may vary depending on your business needs, a typical Privacy Manager client will engage at least one team member from the below list of teams in order to ensure implementation success:
A holistic Privacy Manager implementation “owner” responsible for the success of the project
Someone from your Legal or Privacy team to advise on notice language and compliance needs
Someone from your Marketing, UX, or Digital team to advise on look and feel of the implementation
Someone from your IT, Ad Ops, or Web Developer team(s) to assist with implementation of the Privacy Manager script and conditional tag firing
Pre-Implementation Tasks: What do I need to know?
Before you implement the Privacy Manager for CCPA, there are a few items on which everyone in the list above must agree. You already believe the CCPA applies to your business, but make sure you have outlined:
Your positions on CCPA:
Do we sell data on California consumers?
Will we require a Do Not Sell button, or do we believe a hyperlink in our footer is sufficient?
Will we require a visible privacy notice, or will we manage user preferences from our Privacy Policy?
If we include a notice, what privacy language should be shown to the consumer?
What categories of data do we hold on consumers?
For what purposes is that data held?
Your vendors under CCPA:
Which vendors (SSPs, DSPs, DMPs, etc.) are firing tags on our site(s)?
To which vendors do we wish to persist Do Not Sell or opt-out signals?
Your UX & Design requirements:
Do we have a required banner/notice size?
How do we wish for the CMP to be presented on the page?
What color schema do we select?
What is the list of domains on which we will deploy the Privacy Manager?
Will we require different versions for any of our domains? How many sites should we set up, and what are the design requirements for each?
Will we use the standard Privacy Manager user experience, or do we wish to implement one of the other User Experiences by leveraging Privacy Manager UI suppression?
Implementation Steps & Timelines: What do I do now?
Once you have completed the information gathering stage as outlined above, implementation will be fairly straightforward. Here are the typical steps and timelines to going live with the CCPA Privacy Manager, but many clients may take shorter or longer to implement depending on their business processes:
Step 1: Internal alignment on above implementation tasks and requirements. (Week 1)
Step 2: Configure the initial site implementations in LiveRamp Console; see "Set Up Privacy Manager", the setup guide for help! (Week 2-3)
Step 3: Implement the Privacy Manager script on your dev environment and QA the implementation. (Week 3-6)
Step 4: Go live! (Week 6+)
In case you have any questions, you can always reach out to the support team through the messenger in Console (the orange chat icon in the bottom right of Console).