Answer whether the client postal ZIP shown in Litify/Salesforce is auto-populated as its own field, and how the firm should track cases by client ZIP for lookalikes and marketing conversion demos.
LITIFY_ORG is connected.Account object in this org.Account.BillingPostalCode.BillingPostalCode = 40211.litify_pm__Matter__c.litify_pm__Client__c and can read litify_pm__Client__r.BillingPostalCode.Client_ZIP__c with formula litify_pm__Client__r.BillingPostalCode.litify_pm__Matter_Postal_Code__c, but it is not the reliable client postal-code field. It is sparsely populated: 56 of 16,517 client-linked Matters.Client_ZIP__c formula count.For immediate reporting, use Account.BillingPostalCode through the Matter client relationship: litify_pm__Matter__c.litify_pm__Client__r.BillingPostalCode.
For repeatable Salesforce reports, dashboards, Google Ads conversion demos, and audience/lookalike exports, add a Matter-level formula field such as Client_ZIP__c = litify_pm__Client__r.BillingPostalCode, then add it to the relevant Matter report type/layout/report columns. This mirrors the existing Intake field and avoids manually copying ZIP data.
The session reached a read-only answer with live validation. No Salesforce metadata changes were made because adding a field/report exposure is a durable org change and should be selected from the inline QA options.