All Logs

Match Privacy Requests to Customer Profiles

Require visitors to provide an email for specific privacy choices to ensure accurate record-keeping and DSAR matching.
May 22, 2026
Feature

We've introduced Customer Identification, a powerful feature for Enterprise merchants to better bridge the gap between anonymous privacy requests and known customer data.

  • Streamline DSARs: Easily match Data Subject Access Requests to specific customer records, reducing manual lookup time.
  • Granular Controls: Choose exactly which actions require identification and which remain one-click to balance user experience with data accuracy.
  • Identify Guest Visitors: Require signed-out visitors to provide an email address before submitting specific privacy choices like withdrawing consent.
  • Compliance by Design: The "Do not sell or share" option remains one-click by default, ensuring you stay compliant with "no-friction" opt-out requirements.

Manage these settings and require emails for selected privacy choices from Privacy Center > General Settings > Customer Identification.

Screenshot of the Customer Identification settings interface featuring a toggle to require email for selected privacy choices, with checkboxes for Withdraw consent and Limit use of sensitive personal information.

Other Updates

Update
Handle More U.S. Privacy Requests With a New Case Dashboard
Read more
Feature
Choose Which Tracker Types Appear on Your Preferences Page
Read more
Update
Let Shoppers Add an Optional Note to Their Withdrawal
Read more
Update
Customize the Reply-To Footer Field in Emails
Read more