Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Content]: In HubSpot Source's "Collection Properties" section, make special note of "hs_lastmodifieddate" #6557

Open
mccallion opened this issue May 16, 2024 · 1 comment
Assignees
Labels
content When the bug is about content that needs to get fixed stale triage

Comments

@mccallion
Copy link

What article on segment.com/docs is affected?

https://segment.com/docs/connections/sources/catalog/cloud-apps/hubspot/#collection-properties

What part(s) of the article would you like to see updated?

The collection properties are the fields which segment tracks to detect changes to the source records. For almost every user, they would prefer Segment to detect changes to a "last updated at" timestamp. It is unclear whether or not Segment checks an "updated at" field for the objects listed in this section.

Some sections note that "hs_*" fields are included in the collection properties. This means that "hs_lastmodifieddate" is indeed included (it's actually a timestamp, not a date). For 99% of users, this is what they want to know.

This section can be improved by including a sentence at the top to call that out. Something like: "Since Segment tracks all hs_* properties for Companies and Deals, Segment will detect all changes to these records through the hs_lastmodifieddate."

(My personal headache that I'd like to help others avoid:

When I didn't see this after reading the page for the first time, I started to plan a workaround strategy. I tested a change to an unlisted field for a Deal object, and Segment registered the change. I dug deeper to discover that hs_lastmodifieddate was indeed included.)

Thank you!!!

Additional information

No response

@mccallion mccallion added content When the bug is about content that needs to get fixed triage labels May 16, 2024
@pwseg pwseg self-assigned this Jun 29, 2024
Copy link
Contributor

This issue is stale because it has been open 60 days with no activity.

@github-actions github-actions bot added the stale label Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content When the bug is about content that needs to get fixed stale triage
Projects
None yet
Development

No branches or pull requests

2 participants