CDPGuidesSupport

Synthetic Data

Learn about the Synthetic Data enrichment destination designed for sharing limited amounts of sensitive data with third-party destinations while protecting user privacy.

Overview

Synthetic data is artificially generated data that mimics the statistical properties of real-world data. It lets organizations share sensitive information without exposing actual user data.

The Synthetic Data enrichment destination is designed for customers who need to share limited amounts of sensitive data, including PHI, with third-party destinations while protecting user privacy. Synthetic data allows you to generate and assign properties to visitors that are statistically inferred or anonymized versions of the real data.

Why Use Synthetic Data?

  1. Enhanced Privacy: While hashing is an option, hashes can sometimes be reverse-engineered or decrypted, especially with large datasets. Synthetic data provides an additional layer of protection.
  2. Fill Data Gaps: If your organization lacks certain user information (e.g., city, state), synthetic data can generate these properties based on statistical models.
  3. Flexible Mapping: Synthetic properties are stored alongside visitor data, and you can map these synthetic fields to destinations like Facebook, Google Ads, or other vendors.

For example, instead of sending visitor.email to a destination, you can map visitor.enrichment_properties.synthetic_email.

Synthetic data is generated by analyzing geolocation data, real user data, and statistical trends for each property. These insights are then used to create anonymized data that mimics an account's real data, protecting privacy while maintaining utility.


Synthetic Properties

When enabled, the Synthetic Data enrichment destination generates the following properties for every visitor:

  • enrichment_properties.synthetic_email: A synthetic version of the visitor's email address.
  • enrichment_properties.synthetic_first_name: A synthetic first name.
  • enrichment_properties.synthetic_last_name: A synthetic last name.
  • enrichment_properties.synthetic_gender: A synthetic gender, based on statistical allocation.
  • enrichment_properties.synthetic_date_of_birth: A synthetic date of birth.
  • enrichment_properties.synthetic_phone_number: A synthetic phone number.
  • enrichment_properties.synthetic_city: A synthetic city.
  • enrichment_properties.synthetic_state: A synthetic state.
  • enrichment_properties.synthetic_zip: A synthetic zip code.
  • enrichment_properties.synthetic_country: A synthetic country.
  • enrichment_properties.synthetic_ip: A synthetic IP address.

Synthetic data is only generated after you opt-in and enable the Synthetic Data enrichment destination. Once enabled, these properties will be available for mapping to your other destinations.


How to Use Synthetic Data

  1. Enable the Synthetic Data enrichment destination in your account settings.
  2. Navigate to the Mapping Section of your target destination.
  3. Review the variable dictionary or type-ahead variable inputs to select a synthetic property.
  4. To use synthetic data for a specific destination, update your mapping settings:
    • Replace real properties (e.g., visitor.email) with synthetic properties (e.g., visitor.enrichment_properties.synthetic_email) for the desired fields.

The default mappings Ours Privacy generates when you create a destination generally use the real data properties. You will have to explicitly update the mapping to use synthetic data.


Key Considerations

Compliance

Synthetic data can support HIPAA and GDPR programs by sending synthetic values in place of real PHI or identifiable data. Review your mappings with your compliance team to confirm they fit your requirements.

Testing Synthetic Data

If you want to test how synthetic data behaves, create a duplicate destination for Facebook or Google ads and modify the mapping to use synthetic properties. This allows you to preview the data without affecting existing configurations.


FAQs

Q: Is synthetic data generated for all visitors by default?
A: No, synthetic data is only generated after you opt-in and enable the Synthetic Data enrichment destination.

Q: Where is synthetic data stored?
A: Synthetic data is stored in the visitor.enrichment_properties namespace and follows the same security and retention policies as other visitor data.

How is this guide?

On this page