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

Release 25.09.01 #7466

Merged
merged 33 commits into from
Feb 27, 2025
Merged
Changes from 1 commit
Commits
Show all changes
33 commits
Select commit Hold shift + click to select a range
16eb993
Rate limit Klaviyo
Panandhan22 Apr 30, 2024
46de261
Added Warning to Step 4
MStephen024 Jun 30, 2024
61baf7d
rm approximately 50 note callouts
forstisabella Jan 17, 2025
b2b6abc
appx 50 more
forstisabella Jan 17, 2025
89ecdcb
more of these
forstisabella Feb 7, 2025
0914e31
last group
forstisabella Feb 7, 2025
2bddfa1
Merge branch 'develop' into rm-note-callouts
forstisabella Feb 7, 2025
4fa277a
Update src/connections/destinations/catalog/actions-hubspot-cloud/ind…
forstisabella Feb 7, 2025
d5ddd4b
Apply suggestions from code review
forstisabella Feb 13, 2025
2bad1fa
Apply suggestions from code review
forstisabella Feb 20, 2025
21284ae
Update id-sync.md
forstisabella Feb 24, 2025
3033894
note about `segment_group_id`
spencerattick Feb 24, 2025
fa39a98
Update index.md
segment-voliveira Feb 25, 2025
ba7230d
Apply suggestions from code review
forstisabella Feb 25, 2025
076f7b2
Update src/connections/destinations/catalog/actions-hubspot-cloud/ind…
forstisabella Feb 25, 2025
bc9779d
Merge pull request #7461 from segmentio/spencerattick-patch-5
forstisabella Feb 25, 2025
b5e76f3
Merge pull request #7462 from segmentio/segment-voliveira-patch-1
pwseg Feb 25, 2025
8aa057b
fix broken link
forstisabella Feb 25, 2025
5cfa0e6
Update id-sync.md
forstisabella Feb 26, 2025
66f3229
Merge pull request #7463 from segmentio/fix-7440
forstisabella Feb 26, 2025
0debbb0
fixes
stayseesong Feb 26, 2025
fa68031
catalog
forstisabella Feb 27, 2025
ceaed16
change to info
pwseg Feb 27, 2025
04963f8
minor rewording
pwseg Feb 27, 2025
563d029
Merge pull request #6780 from segmentio/MStephen024-patch-2
pwseg Feb 27, 2025
242947e
Merge pull request #7433 from segmentio/rm-note-callouts
forstisabella Feb 27, 2025
db0b907
Merge pull request #7460 from segmentio/PD-2617
forstisabella Feb 27, 2025
dda6936
Merge branch 'develop' into Panandhan22-patch-5
pwseg Feb 27, 2025
391434c
sentence case
pwseg Feb 27, 2025
d6217e0
Merge pull request #6463 from segmentio/Panandhan22-patch-5
pwseg Feb 27, 2025
996f754
Merge pull request #7464 from segmentio/DOC-1058
stayseesong Feb 27, 2025
dc752e9
Merge pull request #7465 from segmentio/catalog
forstisabella Feb 27, 2025
142bb61
Merge pull request #7467 from segmentio/master
forstisabella Feb 27, 2025
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
note about segment_group_id
spencerattick authored Feb 24, 2025

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
commit 30338940492a94c2583411a7e4d80abfc2556fb5
Original file line number Diff line number Diff line change
@@ -122,6 +122,9 @@ Yes. HubSpot will automatically redirect API requests directly to an EU data cen
### How do I attribute a custom behavioral event with a user token instead of Email?
Event payloads should contain an email with either a valid format, empty string, or a `null` value. As a result, the user token takes precedence and is validated in a `Send custom behavioral event` mapping. Segment can't deliver the event to your destination if the email is invalid.

### How can I update companies in HubSpot if they never were associated with a Segment `group_id`?
Records that were created from a pipeline outside of Segment won't be associated with a special field called `segment_group_id`. Segment uses `segment_group_id` to create companies in HubSpot that way we can easily use the same `segment_group_id` field to update those companies in the future if need be. If companies weren't created by Segment, you will need to use a different field to update existing companies through Segment. The identifier HubSpot sets per company (regardless of where it was created) is `hs_object_id` which you can use if you have it. You can provide the key/value pair in the Company Search fields section of the Upsert Company mapping. If you don't have that value, you can use a different field that can uniquely identify the company in HubSpot.

### How can I disable or delete a destination from Segment?
Follow the instructions in the docs to [disable](/docs/connections/destinations/actions/#disable-a-destination-action) or [delete](/docs/connections/destinations/actions/#delete-a-destination-action) a destination action from Segment.