Skip to content

Commit e3da3a5

Browse files
author
markzegarelli
authored
Add clarity to HubSpot API limit (#2436)
1 parent 83a129e commit e3da3a5

File tree

1 file changed

+1
-1
lines changed
  • src/connections/destinations/catalog/hubspot

1 file changed

+1
-1
lines changed

src/connections/destinations/catalog/hubspot/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ In this case, your HubSpot `eventId` is 'Bought Item'. If you want to use an exi
105105

106106
#### Setting Contact Properties on Track
107107

108-
Segment recommends that you send `traits` with an [Identify](/docs/connections/spec/identify/) call. You can also set HubSpot properties on a track call sent from any server-side source, as allowed by Hubspot's [events API](http://developers.hubspot.com/docs/methods/enterprise_events/http_api){:target="_blank"}. You might want to use this method if you're running out of API calls on the Identify requests.
108+
Segment recommends that you send `traits` with an [Identify](/docs/connections/spec/identify/) call. You can also set HubSpot properties on a track call sent from any server-side source, as allowed by Hubspot's [events API](http://developers.hubspot.com/docs/methods/enterprise_events/http_api){:target="_blank"}. Segment recommends this method if you're running out of HubSpot API calls on the Identify requests.
109109

110110
Include HubSpot contact properties into the `context.traits` object:
111111

0 commit comments

Comments
 (0)