Managing permissions and suppressions

Adding a permission or suppression

To add a permission or suppression to your data mapping:

1. In Orbit connect, go to Data Mappings.

   

2. Click + New Data Mapping.

3. Click Create under Customer Data Table.

   

4. Give your data mapping a Name then click Create.

5. Select your data source from the Data Source dropdown.

6. In the column mapping section to the left, find your permission or suppression data.

7. Click Map Column and expand the relevant contact point folder: Email Addresses, Mobile Numbers, Landline Numbers, or Addresses.

   

8. Click the + next to Permissions or Suppressions to create a new one, depending on your data type.

   

9. Enter a descriptive Name (for example, "OK to Email" or "Do Not Mail") then click Add.

   Your new attribute appears in the dropdown when mapping future columns.

   Tip: To change the name of an existing entry, clik the pencil icon.
   
   

10. Review the Allowed Values Validation rules that appear.

    

    The system displays validation rules that determine how your source data maps to stored values.

    For Permissions, by default, the system accepts common variations of "yes" (such as 1, True, Y, and Yes, irrespective of case) and stores them as True.

    Note: For Suppressions, adjust the above defaults as required.

11. Modify the validation rules if your data uses different values then click Apply.

    Tip: To modify validation rules for an existing entry, click the Option button next to the mapped column, then click Validation Rules.
    
    

You’ve now created a new permission or suppression in your customer data model.

You can now run a system build to make your data available in audience selections and other areas of your Orbit system.

Best practices

• Use clear, consistent names across all data sources. This makes it easier for subsequent imports to update the correct records.

• Before importing data, check that your validation rules cover all possible values in your source data to prevent unexpected rejections.

• The system stores permission and suppression history automatically. Use this to verify what permissions were active when you contacted someone, supporting compliance requirements.

• Ensure you map permissions to the appropriate contact point. Email permissions belong under Email Addresses, not Mobile Numbers or other contact points.

Troubleshooting

Values not importing

Check that your source values match the validation rules. If your data uses "0" and "1" but validation rules expect "true" and "false", modify the rules accordingly.

Cannot find existing permission

Permissions and suppressions are organised by contact point type. Ensure you're looking in the correct folder (Email Addresses, Mobile Numbers, Landline Numbers, or Addresses).