Overview
The Data Masking feature automatically hides PII (e.g. email, phone, etc) to help protect lead data. It’s enabled by default for all new agency users, ensuring data protection is a standard part of campaign management. Users can continue using the platform as normal, even with masked data.
If enabled, users can view leads but they will only be shown the Lead Generator and the Lead ID, no other details are revealed:
Setup
Navigate to the 'Agencies' page.
Click the 'Data Masking' button next to the desired agency.
Change the 'Data Masking' option to the desired selection.
- Enabled: All users assigned to this agency will not be able to view full lead data.
- Disabled: All users assigned to this agency will be able to view full lead data.
Exceptions
Provider Logs
Agency users with Data Masking disabled can see all integration requests and responses within Provider Logs, however PII data will still be masked.
Agency users with Data Masking enabled will see a masked version of requests and responses for only Marketo jobs.
For other integration jobs, Agency users with Data Masking enabled will not see any entries within provider logs.
Processr Logs
Agency users with Data Masking enabled can see all the messages and responses within Processr Logs, however PII data will still be masked.
Processr Job Configuration Values
Some processr jobs, such as 'Simple Conditional Validation', allow configuration against specific values that might be PII, such as postcode. In these cases, it could mean that these configured values will show in lead QA flags - even if a user has Data Masking enabled, e.g.
Enriched Fields Used In QA Jobs
Any fields with enriched data (which may or may not be PII) will be visible in QA flags if enriched fields are used in QA jobs.