Are any special fields created when using Data Integrity?
The following special fields are available in Demandbase once you activate Data Integrity:
| Field | Field Type | Description |
| Data Integrity Status | String |
Indicates whether the record has been processed by Data Integrity. Important: It doesn't matter if the record is matched or unmatched, or if it is part of a recurring or non-recurring process. A processed record is considered a Managed record. |
| Last Updated by Demandbase | Date/Time | Date/time when record was last updated |
| Match Score | Integer | Match score value for an account. |
| Matched Status | String | Indicates whether the record has been successfully or unsuccessfully matched by Data Integrity. |
To see the fields in your CRM or MAS, take the following steps:
- Create the fields in your CRM or MAS. We recommend you use the same (or similar) field names.
-
In Demandbase, map the Demandbase fields to the corresponding CRM or MAS fields. See Step 3: Enrich Field in Create Data Integrity Process.
Important: Updates to these fields do not consume credits.
In Step 2: Segment of the integration setup, why don't any records match the selector criteria?
Return to Step 1: Configure > Record Segmentation. In the date picker for “[Member Type] created after”, you must select a date prior to today. The date picker defaults to today's date so make sure to update it.
Where can I view detailed error information?
The Managed Records table includes an Error Detail column for deeper insights.
How are credits managed?
Data Integrity credits are based on the number of unique records managed within a contract year. Each record uses one credit the first time it is processed. If a record is included in multiple processes, it is only charged once during the contract period.
Credits are only charged for net-new records. Previously enriched records are not charged again, regardless of their status in future runs.
When you reach your credit limit, your Demandbase Account Team contacts you.
What happens to previously enriched records if no new data is found?
If a record was enriched in a past run and no new data is found during a future run:
- Enrichment Status stays as Enriched.
- Enrichment Date does not change. It shows the last date that data was actually updated.
- Last Processed Date updates to the new run date, confirming the record was checked even if no updates were made.
Why do ‘Credits Consumed’ and ‘Records Managed’ counts differ?
This is expected behavior due to two key reasons:
- Credits are tied to individual records, not processes.
- Credits are cumulative and not refunded.
Scenario A: Fewer Credits Consumed than Records Managed
Example: 4,000 credits consumed for 10,000 records managed
You only pay once per record. If 6,000 records were already paid for, you’re only charged for the remaining 4,000 new records.
Scenario B: More Credits Consumed than Records Managed
Example: 20,000 credits consumed, but only 5,000 records managed
Credits are cumulative and not reversed. If you originally managed 20,000 records but later updated the selector criteria to narrow it down to 5,000, the Managed Members count updates to reflect the current number, but the Credits Consumed remains at 20,000.
Why do ‘Member Count’ and ‘Records Managed’ differ?
This is common in scheduled processes that have Enrich net new [Member Type] on creation (NRT) enabled.
- Records Managed: Shows only the records processed during a specific scheduled run. It does not include records enriched via NRT.
- Managed Members: Shows all records currently managed by the process. It includes both scheduled run records and records enriched via NRT.