Hi @sanchid ,
Good question, form submission data in HubSpot can be tricky since each new submission overwrites property values on the contact record. The only permanent record is the form submission object, accessible through the “Get form submissions” endpoint (Accounts Dashboard | HubSpot ) This includes every submission event, even when properties are overwritten.
If your goal is to store these events historically in BigQuery, the cleanest approach is to set up an ETL or sync layer that captures these raw submission payloads and writes them to your warehouse.
Airbyte and Fivetran both support HubSpot form endpoints, but for deeper control, you can poll the endpoint periodically and push JSON payloads into your BigQuery form_submissions table, preserving timestamps and field-level metadata. You can then join those with contact or deal tables for full attribution analysis.
If you ever need those events to flow bidirectionally say, enriching HubSpot with warehouse-calculated metrics like LTV or campaign performance a managed two-way sync avoids the API pagination, schema drift, and token rotation issues described in Stacksync’s architecture guide. If consistency between HubSpot and your data warehouse is the gap, Stacksync keeps them mirrored in real time without the need for manual ETL scripts.