Enforce consent
- Topics:
- Consent
CREATED FOR:
- Beginner
- User
- Developer
- Admin
Learn how to create policies to enforce customer’s consent preferences. For more information, see the documentation.
Transcript
I’m Shelby Farmer, product manager for Adobe Experience Platform. Let’s take a look at how a fictitious sportswear brand called Luma is innovating their business through trust-focused tools. Luma faced three key challenges when they adopted ADobe’s capabilities. First, they need to unify multiple toolsets within Adobe. These workflows were also incredibly manual and led to a longer time to value. Lastly, they wanted a designated role of data steward to create policies around their consumers’ consent and preferences. So how do Luma use Experience Platform to solve these challenges? Let’s start with one of their priority use cases. Luma wants to run a campaign for its sports apparel shoppers and send out a personalized marketing campaign to re-engage them. Martha, their data steward knows that Luma uses OneTrust to collect customer consent and preference data and decides to build a policy around it. Thanks to the new integration between Platform and OneTrust CMP, it is very easy for Martha to configure automatic ingestion of consent and preference data into Platform. With the consent and preference data in RTCDP, Martha can set up a consent policy and configure a role that filters profiles who have consented to have their data used for personalization. First, she defines when she wants the data to be enforced by providing a marketing action for cross-site targeting. When she is ready to filter, she’s able to define what data should be filtered out by choosing a consent attribute for the profiles which have said yes to content personalization. Note that to do all of this work around consent, Martha is leveraging Platform’s data governance, labeling and policy abilities. These tools can be used not only for internal governance use cases but also for external consumer consent management. So there you have it. Martha has now defined a policy that the marketer is using cross-site targeting in Adobe tools, then filter for only profiles that have consented to content personalization. Now that the policy’s set, let’s see it in action.
Luma’s day-to-day marketer is now getting ready to activate segments for her retail campaign. She selects which segments she wants to map to her destination.
Then sets the schedule.
And then selects which identities on the attribute to include. Once she schedules the activation, RTCDP runs a policy check and informs her that her effective addressable audience has decreased due to the consent policies in place. She’s now able to understand why the policy has been triggered and is relieved to learn that it took into account the consent and preferences of Luma’s customers.
As you can see, these streamlined workflows will bring organizations together to solve the use case in a few seconds for what used to take a few days or weeks. The policy check experience will also extend to applications and use cases that are integrated with Platform, including Adobe during the optimizing. Now that you’ve seen these consent capabilities in action, I hope you are as excited as I am about the future of trust in Adobe. -
Experience Platform
- Platform Tutorials
- Introduction to Platform
- A customer experience powered by Experience Platform
- Behind the scenes: A customer experience powered by Experience Platform
- Experience Platform overview
- Key capabilities
- Platform-based applications
- Integrations with Experience Cloud applications
- Key use cases
- Basic architecture
- User interface
- Roles and project phases
- Introduction to Real-Time CDP
- Getting started: Data Architects and Data Engineers
- Authenticate to Experience Platform APIs
- Import sample data to Experience Platform
- Administration
- AI Assistant
- Audiences and Segmentation
- Introduction to Audience Portal and Composition
- Upload audiences
- Overview of Federated Audience Composition
- Connect and configure Federated Audience Composition
- Create a Federated Audience Composition
- Audience rule builder overview
- Create audiences
- Use time constraints
- Create content-based audiences
- Create conversion audiences
- Create audiences from existing audiences
- Create sequential audiences
- Create dynamic audiences
- Create multi-entity audiences
- Create and activate account audiences (B2B)
- Demo of streaming segmentation
- Evaluate an audience rule
- Create a dataset to export data
- Segment Match connection setup
- Segment Match data governance
- Segment Match configuration flow
- Segment Match pre-share insights
- Segment Match receiving data
- Audit logs
- Data Collection
- Dashboards
- Data Governance
- Data Hygiene
- Data Ingestion
- Overview
- Batch ingestion overview
- Create and populate a dataset
- Delete datasets and batches
- Map a CSV file to XDM
- Sources overview
- Ingest data from Adobe Analytics
- Ingest data from Audience Manager
- Ingest data from cloud storage
- Ingest data from CRM
- Ingest data from databases
- Streaming ingestion overview
- Stream data with HTTP API
- Stream data using Source Connectors
- Web SDK tutorials
- Mobile SDK tutorials
- Data Lifecycle
- Data Science Workspace
- Overview
- Architecture
- Load data in JupyterLab notebooks
- Query and discover data in JupyterLab notebooks
- Exploratory Data Analysis
- Recipes, models, and services overview
- Build a model using the recipe builder template
- Analyze model performance
- Create and publish a trained model (UI)
- Schedule automated training and scoring for a service
- Enrich Real-Time Customer Profiles with machine learning insights
- Package source files into a recipe
- Import a packaged recipe (UI)
- Import a packaged recipe (API)
- Destinations
- Destinations overview
- Connecting to destinations
- Create destinations and activate data
- Activate profiles and segments to a destination
- Configure a dataset export destination
- Integrate with Google Customer Match
- Configure the Azure Blob destination
- Configure the Marketo destination
- Configure file-based cloud storage or email marketing destinations
- Configure a social destination
- Activate through LiveRamp destinations
- Adobe Target and Custom Personalization
- Activate data to non-Adobe applications webinar
- Identities
- Intelligent Services
- Monitoring
- Partner data support
- Profiles
- Understanding Real-Time Customer Profile
- Profile overview diagram
- Bring data into Profile
- Customize profile view details
- View account profiles
- Create merge policies
- Union schemas overview
- Create a computed attribute
- Pseudonymous profile expirations (TTL)
- Delete profiles
- Update a specific attribute using upsert
- Privacy and Security
- Introduction to Privacy Service
- Identity data in Privacy requests
- Privacy JavaScript library
- Privacy labels in Adobe Analytics
- Getting started with the Privacy Service API
- Privacy Service UI
- Privacy Service API
- Subscribe to Privacy Events
- Set up customer-managed keys
- 10 considerations for Responsible Customer Data Management
- Elevating the Marketer’s Role as a Data Steward
- Queries
- Overview
- Query Service UI
- Query Service API
- Explore Data
- Prepare Data
- Adobe Defined Functions
- Data usage patterns
- Run queries
- Generate datasets from query results
- Tableau
- Analyze and visualize data
- Build dashboards using BI tools
- Recharge your customer data
- Connect clients to Query Service
- Validate data in the datalake
- Schemas
- Overview
- Building blocks
- Plan your data model
- Convert your data model to XDM
- Create schemas
- Create schemas for B2B data
- Create classes
- Create field groups
- Create data types
- Configure relationships between schemas
- Use enumerated fields and suggested values
- Copy schemas between sandboxes
- Update schemas
- Create an ad hoc schema
- Sources
- Use Case Playbooks
- Experience Cloud Integrations
- Industry Trends