> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wegive.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Household

> Field mapping between WeGive households and Salesforce Household Accounts

Households sync to Salesforce Accounts using a dedicated Household record type. WeGive discovers the Household record type at connect time; if your org has none, household sync is disabled.

<Warning>
  **The household record itself is pull-only (Salesforce → WeGive) today**, despite the Sync column below and a Push toggle existing on the dashboard — this is a known issue. A new or renamed household created in WeGive never reaches Salesforce. This is separate from **member linkage** below, which genuinely does push — when a WeGive supporter is added to a household, WeGive pushes that supporter's own `ParentId` field (part of the Person Account push), it just never pushes the household Account record itself.
</Warning>

## Identity

| WeGive field | NPC field | Sync |
| - | - | - |
| `name` | `Name` | ↔ |

## Address

| WeGive field | NPC field | Sync |
| - | - | - |
| `billing_address.address_1` | `BillingStreet` | ↔ |
| `billing_address.city` | `BillingCity` | ↔ |
| `billing_address.state` | `BillingState` | ↔ |
| `billing_address.zip` | `BillingPostalCode` | ↔ |
| `billing_address.country` | `BillingCountry` | ↔ |

## Member linkage

Household members are Person Accounts whose `ParentId` points to the Household Account. On push, WeGive sets `ParentId` on each member. On pull, WeGive reads `ParentId` on each Person Account and attaches the supporter to the matching household.

## Linkage

| WeGive field | NPC field |
| - | - |
| `npc_id` | `Id` |

## Merges

When two Household Accounts are merged in Salesforce, WeGive detects the merge on the next pull and merges the corresponding WeGive households.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.