Use of identity resolution impacts the consumption of credits used for billing in these usage types.
Use Digital Wallet to check which consumption cards are active in your org, find out how many credits are available on each card, and determine how many credits have been consumed in each usage type.
Some usage types aren't metered for certain licenses or editions, such as a Data 360 Profiles license. Check your licenses and review license documentation for more information.
Data 360 Usage
When you use identity resolution, your org consumes credits from either the Data Services consumption card or the Flex Credits consumption card.
- If your contract included Data Service Credits, those are consumed for all Data 360 usage.
- If you run out of Data Service Credits, your org is billed at your Data Service Credit overage rate for the remainder of your term unless more credits are added.
- If you have Flex Credits for Data 360, those credits are consumed instead.
Data Services and Flex Credits organize data services within different usage type groupings. For more information, see Data Services Billable Usage Types for Data 360 and Flex Credits Billable Usage Types for Data 360. To check multipliers for each usage type, see the Multipliers for Data Services Rate Card or the Agentforce & Data 360 Flex Credits Rate Card. The cost of each credit is determined by your contract.
| Digital Wallet Card | Usage Type | Usage Type Description | Notes |
|---|---|---|---|
| Data Services | Batch Profile Unification |
Usage is calculated based on the number of source profiles processed by an identity resolution ruleset. After the first time a ruleset runs, only new or modified source profiles are counted. A source profile is an individual and their related records, such as contact points and party identifiers, which are included in the identity ruleset. For example, modified means deleted profiles, or profiles marked as suppressed via Consent API preferences. |
In certain circumstances, identity resolution is triggered to fully reprocess a ruleset. These actions can trigger a full run of a ruleset.
Records excluded by ruleset preprocessing filter conditions are not counted as processed records. |
| Data Services | Data Queries |
Usage is calculated based on the number of records processed. The count of records processed depends on the structure of a query as well as other related factors such as the total number of records in the objects being queried. |
Data queries are used to create the processing history table. |
| Data Services | Sub-second Real-Time Events |
Usage is calculated based on the sum of the number of profile events, engagement events, and API calls processed in the sub-second real-time layer, including accelerated data ingest, web and mobile SDKs traffic, server to server API traffic, and real-time ingestion API. Profile events, engagement events, and API calls are processed in the real-time layer if they are associated with a real-time data graph. For example, if 3 profile events, 10 engagement events, and 20 API calls are processed during a particular billing period, the total processed is 33. |
This category applies only to real-time identity resolution. |
| Flex Credits | Data 360 Unification |
Usage is calculated based on the number of source profiles processed by an identity resolution ruleset. After the first time a ruleset runs, only new or modified source profiles are counted. A source profile is an individual and their related records, such as contact points and party identifiers, which are included in the identity ruleset. For example, modified means deleted profiles, or profiles marked as suppressed via Consent API preferences. |
This category isn't used when your org has active Data Services credits. In certain circumstances, identity resolution is triggered to fully reprocess a ruleset. These actions can trigger a full run of a ruleset.
Records excluded by ruleset preprocessing filter conditions are not counted as processed records. |
| Flex Credits | Data 360 Queries |
Usage is calculated based on the number of records processed. The count of records processed depends on the structure of a query as well as other related factors such as the total number of records in the objects being queried. When an object is queried in the context of a data space, the number of rows processed is based on the total number of processed rows in the source object, not the number of rows pertaining to the particular data space |
This category isn't used when your org has active Data Services credits. Data queries are used to create the processing history table. |
| Flex Credits | Data 360 Real-Time Pipeline |
Usage is calculated based on the sum of the number of profile events, engagement events, and API calls processed in the sub-second real-time layer, including accelerated data ingest, web and mobile SDKs traffic, server to server API traffic, and real-time ingestion API. Profile events, engagement events, and API calls are processed in the real-time layer if they are associated with a real-time data graph. For example, if 3 profile events, 10 engagement events, and 20 API calls are processed during a particular billing period, the total processed is 33. |
This category isn't used when your org has active Data Services credits. This category applies only to real-time identity resolution. |
For more information on how Data 360 usage is billed, refer to your contract or contact your account executive.
Data 360 Storage Usage
| Digital Wallet Card | Usage Type | Usage Type Description | Notes |
|---|---|---|---|
| Data Storage | Storage Beyond Allocation | Usage is calculated based on the amount of storage used above the amount allocated. | Identity resolution stores the output of ruleset runs in Data 360 data model objects. |
Reduce Identity Resolution Costs
You can lower credit consumption rates for identity resolution in several ways
- Implement stricter data governance policies in source systems to improve the quality of data.
- Use data transforms to pre-process profile data, such as by filtering out records with email addresses that occur more than 1000 times or standin phone numbers such as 888-111-1111.
- Disable
Run jobs automaticallybefore you make multiple changes that each trigger a full refresh, such as adding new data sources, updating your data model, match rules, or reconciliation rules. Resume automatic ruleset runs after your changes are complete. - Test new rulesets first in a sandbox org with a small set of representative data. If you don’t have a sandbox but have multiple data spaces, consider testing in a data space with a small amount of data.
- Maintain just one active ruleset per primary data model object per data space. Create additional rulesets only when you want to test a new configuration against your existing ruleset.
- Use preprocessing filters to filter out records you don't want to send to the unification pipeline.