Harmonization and Unification17% of the exam

Identity resolution: match and reconciliation rules

How identity resolution builds unified profiles: unification types, ruleset setup and IDs, match rules and methods, reconciliation rules, unified link objects, known versus anonymous profiles, scheduled versus real-time runs, and the levers that control credit use.

Official exam objective
Define the purpose, process, and supported use cases of unification.

~8 min read · 26 practice questions ·

What the exam expects

  • Explain what unification does (and doesn't do) and pick the unification type: individuals or accounts, leads to accounts, or households.
  • Create and change rulesets safely: prerequisites, ruleset IDs, testing a second ruleset, updating versus deleting.
  • Design match rules: methods, Match on Blank, Case Sensitive, party identifiers, and avoiding over-matching.
  • Choose reconciliation rules per object and field, and handle contact points through activation instead.
  • Explain run timing, real-time matching, consolidation rate, known versus anonymous profiles and credit levers.

Key terms:

  • Ruleset: the match and reconciliation rules for one primary DMO; its output is unified DMOs.
  • Match rule: criteria that must all match; any one rule matching links two records.
  • Reconciliation rule: picks the single value shown in a unified field.
  • Unified link object: the bridge from each source record ID to its unified profile ID.
  • Consolidation rate: 1 - (unified profiles / source profiles).

Key facts

Ruleset ID
Detail
Up to 4 characters, unchangeable
Ruleset deletion
Detail
Up to 24 hours; data unrecoverable
Exact
Detail
Case-insensitive
Household rulesets
Detail
One match rule only
Last Updated
Detail
Needs Last Modified Date mapped
Contact points
Detail
Not reconciled
Processing frequency
Detail
60 minutes to 24 hours by source
Ruleset job limits
Detail
Scheduled at most once per day; 4 jobs per 24 hours; 5 rulesets per primary DMO per data space
Real time
Detail
Match on Blank ignored; no fuzzy
Consolidation rate
Detail
1 - (unified / source)
Known unified profile
Detail
Any linked source profile is known
Real-time no exact match
Detail
No profile returned; reviewed at next scheduled run
Full reprocess triggers
Detail
Match, reconciliation or filter changes; new DLO or field mapped to a ruleset DMO
Sources for this section (12)
  • Why does adding a second match rule raise the consolidation rate?
  • When can you create a household ruleset?
  • Which object relates source purchases to unified profiles for a calculated insight?
  • Why can Match on Blank cause the 50,000-match error?

The questions are free to read. Answers with their sources and self-grading are included with the pack.

Keep reading with the Data 360 Consultant pack

  • Core concepts
  • Exam traps
  • Worked scenario

The pack includes:

  • All 22 lessons of the Data 360 Consultant guide, with reading progress
  • Interactive decision walks and step-by-step sequence steppers
  • Inline practice questions and one-click topic practice (26 questions for this lesson)
  • An official source cited for every claim
  • An AI tutor that answers from the guide
  • Unlimited timed practice exams

Practice for the Data 360 Consultant exam