CCIO Record Triggers by Priority Follow
As CCIOs are generated, LeanData will process them in the Continuous Clean Batch according to the Priority that is assigned to them. By default, these are the priorities assigned to different CCIO types (lower number means a higher priority).
| CCIO Type | Default Priority | Description |
| lead insert routing | 1.0 | New Lead is created that meets New Lead trigger conditions in Lead Router |
| lead update routing | 1.0 | Existing Lead is updated that meets Updated Lead trigger conditions in Lead Router |
| lead insert tagging | 2.0 | New Lead is created and needs to be evaluated for tagging |
| lead update tagging | 2.0 | Existing Lead is updated in a way that needs to be evaluated for tagging |
| lead update tagging (untagged) | 2.0 | Same as "lead update tagging" but allows you to differentiate the priority between currently untagged vs already tagged Leads |
| lead tagging from account update | 2.0 | Existing Account is updated in a way that causes leads to need be evaluated for tagging |
| contact insert routing | 1.0 | New Contact is created that meets New Contact trigger conditions in Contact Router |
| contact update routing | 1.0 | Existing Contact is updated that meets Updated Contact trigger conditions in Contact Router |
| paedb | 3.0 | Contact Email domains are added or updated that require an update to the email domains associated with the Account |
| account insert routing | 1.0 | New Account is created that meets New Account trigger conditions in Account Router |
| account update routing | 1.0 | Existing Account is updated that meets Updated Account trigger conditions in Lead Router |
| account insert tagging | 2.0 | New Account is created and needs to be evaluated to tag any existing Leads that match into it |
| account update tagging | 2.0 | Existing Account is updated in a way where it needs to be evaluated |
| umlf | 3.0 | used to update mapped lead fields when you populate/update a field being mapped from an account |
| opportunity insert routing | 1.0 | New Opportunity is created that meets New Opportunity trigger conditions in Opportunity Router |
| opportunity update routing | 1.0 | Existing Opportunity is updated that meets Updated Opportunity trigger conditions in Opportunity Router |
| case insert routing | 1.0 | New Case is created that meets New Case trigger conditions in Case Router |
| case update routing | 1.0 | Existing Case is updated that meets Updated Case trigger conditions in Case Router |
In cases where a CCIO may have multiple types (i.e. both tagging and routing) the CCIO will take the higher priority (lower number).
Notes
[A] These priorities do not need to be whole integers and can accommodate 1 decimal place for further prioritization. CCIO types that are not specified in your map will retain their default priority.
[B] Setting a priority value of "0" will disable that CCIO type entirely with the exception of PAEDB CCIOs. To disable PAEDB CCIOs please reach out to your implementation consultant.