Data Routing: Device Alias ID

The List services Allowlist, Denylist, or Custom List, and Identity Element Velocity (IEV), are Alloy services that automatically check evaluations based on one or more personally identifiable information (PII) elements.

Data services like Iovation provide unique device identifiers as a form of PII and can pass data to the List or IEV services to the Device Alias.

The downstream services must execute after Iovation so they can consume the returned device data. Therefore, iovation must be in a column that appears appear before the List and IEV services.

Data Routing configuration is handled at the data service node level and requires Iovation to be configured in the Workflow. 

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 From, input iovation: Device Alias/Device ID. 
4. Then select the service that the data will go to and map it to device alias.
5. Click the checkmark once the selection is complete to save.
6. The selected List service will move to the right of the iovation service node, showing the dependency.
7. Save the workflow changes to a new version and publish the version as active.

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