Reltio Connect

Hi Team,

We are currently evaluating our Householding (HHLD) implementation and would like to understand whether any Loqate-provided attributes can reliably identify if an address belongs to a single-unit building or a multi-unit building (e.g., apartment complexes, office buildings with suites, condominiums, etc.).

Business Scenario

Our current householding logic primarily groups records based on address-related attributes. We have identified a potential issue where multiple individuals residing at the same physical address may be incorrectly grouped into the same household when the address represents a multi-unit building.

Examples:

• Multi-unit building: 123 Main St, Apt 101 and 123 Main St, Apt 202 should not necessarily be grouped into the same household.
• Single-unit building: Multiple individuals sharing the same residential address may legitimately belong to the same household.

To improve householding accuracy, we would like to determine whether Loqate provides any attribute, indicator, or metadata that can help distinguish:

1. Single-unit buildings
2. Multi-unit buildings
3. Buildings that contain multiple residential or commercial units

Hi Ankit,
Great question - this is a common householding challenge and Loqate does provide attributes that can help.

The key field to use is SubBuilding - this is Loqate's output attribute that captures apartment, suite, unit, floor, and similar sub-building identifiers. When SubBuilding is populated, records with different SubBuilding values should be treated as separate households, even if they share the same street address.

A few important nuances though:

• If SubBuilding is empty, do not assume the address is a single-unit dwelling. It may simply mean the unit information wasn't present in the input record. In that case, falling back to street-level householding is possible, but should be treated carefully - flagging those records for data quality review is safer than auto-grouping.
• Beyond SubBuilding, Loqate also returns related attributes like SubBuildingBlock and SubBuildingDoor which can provide additional granularity. You can find the full list of Loqate output attributes mapped by Reltio here: Mapping Output Attributes – Reltio Docs
• AVC (Address Verification Code) can also be surfaced and used as a signal for match confidence, but it is configuration-dependent and not part of the standard business address model out of the box.

Important caveat before implementing: The availability of SubBuilding and AVC in your environment depends on your tenant's data model and cleanse configuration. I'd recommend first confirming these fields are being mapped and persisted in your Address entity before incorporating them into your household match rules.

Hope this helps point you in the right direction!

Hi Abhilasha,

Thanks for the reply.

Could you help me for the scenarios where we are not getting sub building from Reltio cleanser, because there are chances that building can be multi level. How to tackle those scenarios?

Regards,

Ankit