The pattern: license Lightning Data, identify enrichment scope, build rules per object, configure matching and overwrite policy, schedule conservatively, monitor quota usage, audit quarterly. The cost is real (license plus operational discipline); the data quality benefit is real and visible to sales teams.
- License Lightning Data
Lightning Data is a separate Salesforce add-on. Confirm license coverage before configuring rules; rules without license return errors.
- Identify enrichment scope per object
Which fields should enrich on Account, Lead, Contact. The list drives the rule mapping and the subscription tier needed.
- Create the Data Integration Rule per object
Setup, Data Integration Rules, New. Pick the Lightning Data package, the target object, and the activation status (typically Inactive first for testing).
- Configure field mappings and overwrite policy
Per field: which provider field maps to which Salesforce field, Fill Blanks Only vs Overwrite. Be conservative on Overwrite for admin-curated fields.
- Set the refresh schedule conservatively
Weekly is the typical balance between currency and quota. Daily for very-fast-changing fields; monthly for slow-changing.
- Activate and monitor the first week
Watch the quota dashboard and a sample of enriched records. Confirm enrichment matches expectation; tune mapping if values are wrong.
- Schedule the quarterly rule audit
Audit mappings against current provider documentation, sample enriched records, retire stale mappings. The cadence prevents drift.
The provider data set the rule consumes (D&B Hoovers, D&B Lite, partner packages).
Per provider field to Salesforce field assignment.
Per field: Fill Blanks Only or Overwrite.
Daily, weekly, monthly cadence plus on-create triggers.
The Lightning Data dashboard tracking enrichment volume against subscription quota.
- Lightning Data is a paid add-on. Rules without license return errors; confirm coverage before configuring.
- Overwrite policy replaces admin-curated values. Use Fill Blanks Only by default; Overwrite only for fields where the provider is authoritative.
- Match confidence depends on source data quality. Vague company names and missing websites produce low-confidence matches and reduced enrichment.
- High-frequency refresh exhausts subscription quota quickly. Weekly is the typical balance; daily on large record sets is expensive.
- Provider schemas evolve. Quarterly mapping audits catch drift before enriched data goes wrong.