Marketing Cloud Next - Tips for managing Data Cloud credit consumption in Marketing Cloud Next

Below are two methods to reduce credit consumption for Batch Profile Unification via Identity Resolution rulesets:

1) Configure a filter on relevant Data Lake Objects (DLOs)
Adding a filter to your DLO, will reduce the number of rows processed by Identity Resolution. You can use a filter to only process records you would like to utilize for Marketing Cloud Next.

• For an Identity Resolution rule for Individual, consider adding a filter to the contact, lead, and/or prospect DLOs.
• If you have an Identity Resolution rule for Account, considering adding a filter to the account DLO.

2) Avoid excessive editing of the Identity Resolution ruleset or other modifications that trigger a full reprocess

In certain circumstances, identity resolution is triggered to fully reprocess a ruleset. These actions can trigger a full run of a ruleset, which can consume a significant number of credits.

• Changing a ruleset's match rules.
• Changing a ruleset's reconciliation rules.
• Mapping a new data lake object (DLO) to a data model object (DMO) that's used in a ruleset.
• Mapping a new field to a DMO that's used in a ruleset. 
• Updating your data model (which includes deleting and recreating data streams). 

As noted in this help documentation, temporarily disable "Run jobs automatically" on your identity resolution rule(s) before you make multiple changes that each trigger a full refresh. You can do this by editing the Identity Resolution rule and turning off the "Run jobs automatically" toggle. This will prevent multiple full refreshes.