Why it matters
Object data can only support contact filtering when Whippy knows how the object records relate to contacts. Associations make that relationship explicit and help filters, segments, variables, and workflows find the right records.
Key Concepts
Object association: A relationship between two object types or between an object and a Whippy resource.
Whippy association: An association that links object records to a Whippy resource such as contacts.
Source property: The object property used as the starting value for the relationship.
Target property: The contact field or object property that the source property should match.
Association path: The chain of relationships Whippy follows from an object record to a contact.
Step-by-Step: Set up an object association
Open Settings.
Select Objects.
Open the object that needs to connect to contacts or another object.
Review the properties available on the object.
Add or edit an association.
Choose the source property on the object.
Choose the target resource or target object and the property it should match.
Save the association.
Return to Contacts and test a filter or segment that uses the object data.
Tips and Best Practices
Use stable identifiers such as external IDs when building associations.
Confirm the matching values use the same format in both systems.
Keep association paths as simple as possible.
Test associations with known records before using them in a live segment or automation.
Troubleshooting
Issue | Possible Cause | Fix |
Object data does not appear in contact filters | The object is not associated with contacts or the association path is incomplete | Add a Whippy association or connect the object to another object that links to contacts |
Object data links to the wrong contact | The source and target properties match the wrong identifiers | Review the association properties and compare values on known records |
An association cannot be changed | The object may be integration-owned or the user may lack permission | Check whether the object is managed by an integration and review admin permissions |