Skip to main content
If there are blocklist checks enabled in the recipe, there’ll be an ability to pick up on customers or entity attributes that have been blocked previously. Blocklist checks, and their close counterpart the duplicate check, will return a ProcessResultObject for each match to another entity, based on your configured matching rules.
Blacklist or Blocklist?
The API documents refer to “blacklists” as well as “blocklists”. We’re in the process of renaming all our blacklist references to blocklists, so recognise that these terms are interchangeable and refer to the same mechanism.Blocklist will be the preferred naming convention going forward.
Each ProcessResultObject will contain the following values: The following resultNote Key-Value-Pairs will also be set.

Effect on EntityProfileResult

When there is a blocklist match (either a true positive or all potential matches haven’t yet been marked as false positives), this will prevent any further checks from being run. In that case, there would be something like the following in the entityProfileResult checkResults section:
Blocklist Result
In there you can see that there is a blacklist FAIL result and subsequent checks are blocked by this failure.

Example

An example where there are two false positive matches, one true positive and outstanding are below:
Example Blocklist Result