Allowlist/Denylist Services: Device Alias ID

The List service, which includes the Allowlist and Denylist, is an Alloy service that automatically approves or denies evaluations based on one or more personally identifiable information (PII) elements.

Data services like Iovation provide unique device identifiers as a form of PII. Using the List service to check for Device Alias requires specific workflow changes, detailed below.

In this example workflow, Data Routing must be configured so that Iovation runs before the List service. Iovation runs first, collects Device Alias information, and then passes that to the List service for evaluation.

The screenshot below shows the thresholds for the Allowlist Approved and Denylist Denied tags.

Data Routing configuration is handled at the data service node level. 

1. Click on the green Iovation data service node to expand the Threshold window.
2. Click on the Data Routing tab on the menu bar. 
3. Under Outgoing, click edit for uuid, an alias for Device Alias/Device ID. 
4. Click on the "--" to open the drop down, then select the service that contains the uploaded Device Alias IDs.
5. Click the checkmark once the selection is complete.
6. The selected List service will move to the right of the iovation service node, showing the dependency.

This article provides a general example and may not fit your exact use case or Workflow configuration.