Why Are There Data Discrepancies in Association Tables?

Question

Why are there data discrepancies in association tables (tables with names in [<FROM_TABLE_NAME>]_[<TO_TABLE_NAME>] format)?

Environment

Connector: HubSpot

Answer

We use the hs_lastmodifieddate field of the HubSpot API's responses to determine when an object has been updated. However, due to limitations in the HubSpot API, the hs_lastmodifieddate field doesn't always update when you create an association between two object types. As a result, we can't sync the applicable association data to your destination until another update causes the hs_lastmodifieddate field to change.

Re-syncing association tables

Association table names follow the [<FROM_TABLE_NAME>]_[<TO_TABLE_NAME>] format. To re-sync an association table, you must re-sync the <FROM_TABLE NAME> table. For more information, see our HubSpot table re-syncs documentation.

Ensure all associations are captured

You can ensure we capture all associations by doing the following:

1. Identify the two object types you want to associate. For example, object types A and B.
2. Create a calculated count property for object type A that automatically updates when you add or remove an association with object type B. For more information, see HubSpot's Create calculation properties documentation.

Once you create the calculated count property, it updates each time you create an association, resulting in an update to the hs_lastmodifieddate field of the HubSpot API's responses.

WARNING: If object type A's corresponding history table is included in your connection schema, each update to the new calculated count property will create a new row in your destination, contributing to Monthly Active Rows (MAR).