How Campaign uses data filters to restrict access to customer data

Administrators can define data filters in Marketing Platform to restrict IBM® EMM users from accessing specific customer data. In Campaign, data filters affect flowchart output.

To restrict data access, Marketing Platform administrators define data filters and then assign users or groups of users to different data filters. For example, administrators can control access to customer data based on the geographical sales territory to which the IBM® user is assigned.

To learn how to set up data filters, see the IBM® Marketing Platform Administrator's Guide.

Data filters that are defined in Marketing Platform have the following effects in Campaign:

Data filters apply to the Select, Extract, and Audience processes in Campaign flowcharts. For example, if a database table includes 2000 records but 500 of them are restricted by a data filter, a Select All in Campaign returns only 1500 records.

Data filters do not affect design-time activities. For example, a data filter does not hide the values that are displayed when a field is profiled. Although users can see restricted data when they profile a field or build queries in a process configuration dialog, the query results do not include restricted data. Data filters are integrated into the SQL that the process box uses to query the table with which the filter is associated.

Data filters do not apply to raw SQL queries or to custom macros that use raw SQL. For example, if you use Select Customer IDs Using SQL to create a raw SQL query in the Select Process Configuration dialog, any data filters are ignored when you run the query. This behavior is intentional, to provide advanced users with the ability to perform SQL queries without restrictions.

Raw SQL queries override data filters, so users who perform SQL queries can access records regardless of data filters. If you do not want Campaign users to be able to use raw SQL, you must restrict their permissions.