Operational considerations for HubSpot Reader

The following guidance and metrics can help you deploy and operate HubSpot integrations in Striim.

Metrics monitored by the HubSpot Reader

Metric	Description
Number of DDLs	Number of data definition language operations
Number of updates	Number of update operations
Number of inserts	Number of insert operations

For more information, see the Striim monitoring documentation.

The HubSpot Reader does not currently capture DELETE operations.
The names of custom objects must end in __c.
Records for objects that do not support incremental load are synced at every polling interval, which can result in duplicate records. Enable Merge mode for the targets of objects that do not support incremental load to avoid duplicate records.
Objects whose time of last update cannot be determined by Striim are duplicated in the target at every polling interval (for example, when an object does not have a Last_Modified_Date field).
When a table has both an ID field and a Last_Modified_Date timestamp field, using the timestamp field as the incremental load marker for incremental operations is a best practice. Using the ID field can lead to data loss at high volume; resync to correct if needed.
Due to HubSpot API filter constraints, do not use CreatedAt, UpdatedAt, or Archived as a check column. Valid fields include ID, lastmodifieddate, object_lastmodifieddate, and custom date fields. Native objects such as FORM may require full resyncs.