You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: src/_includes/content/destination-maintenance.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -11,5 +11,5 @@
11
11
{% endif %}
12
12
13
13
<divclass="premonition warning"><divclass="fa fa-check-square"></div><divclass="content"><pclass="header">{{page.title | replace: 'Destination', ''}} (Classic) is in Maintenance mode</p>
14
-
<pmarkdown=1>The {{name}} (Classic) Destination has entered maintenance mode. Future updates are limited to security updates and bug fixes. {{blurb}}</p>
14
+
<pmarkdown=1>The {{name}} Destination has entered maintenance mode. Future updates are limited to security updates and bug fixes. {{blurb}}</p>
Copy file name to clipboardexpand all lines: src/connections/destinations/catalog/hubspot/index.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -223,7 +223,7 @@ When using any of Segment's server-side sources, a connector infers `traits.life
223
223
224
224
### Loading Forms SDK
225
225
226
-
Segment gives you the option to load the [HubSpot Forms SDK](https://developers.hubspot.com/docs/methods/forms/advanced_form_options){:target="_blank"} alongside their tracking library. Enable the **Load Forms SDK** setting when you your HubSpot integration.
226
+
Segment gives you the option to load the [HubSpot Forms SDK](https://developers.hubspot.com/docs/methods/forms/advanced_form_options){:target="_blank"} alongside HubSpot's tracking library. Enable the **Load Forms SDK** setting for your HubSpot integration.
227
227
228
228
> info ""
229
229
> The Forms SDK expects to load synchronously but analytics.js loads asynchronously. To interact with the API, run code inside an [analytics.ready](/docs/connections/sources/catalog/libraries/website/javascript/#ready) callback. For example:
##### If you choose not to encode your payload, send it like this instead:
59
+
60
+
```
61
+
https://api.segment.io/v1/pixel/track?userId=user_123&event=Email Opened&properties.subject=The Electric Daily&[email protected]&writeKey=<YOUR_WRITE_KEY>
62
+
```
63
+
58
64
##### Add an image tag to your email newsletter with `src` pointing to a Pixel API route:
Copy file name to clipboardexpand all lines: src/engage/journeys/event-triggered-journeys-steps.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ plan: engage-foundations
8
8
Steps are the building blocks of a journey. This page explains the **Hold Until** and **Send to Destination** steps, which enable precise control over journey progression and data delivery.
9
9
10
10
> info "Public Beta"
11
-
> Event-Triggered Journeys is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. Event-Triggered Journeys is not currently HIPAA eligible.
11
+
> Event-Triggered Journeys is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available.
Copy file name to clipboardexpand all lines: src/engage/journeys/event-triggered-journeys.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ Unlike traditional audience-based journeys that rely on pre-defined user segment
10
10
On this page, you'll learn how to create an event-triggered journey, configure entry conditions, and work with published event-triggered journeys.
11
11
12
12
> info "Public Beta"
13
-
> Event-Triggered Journeys is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. Event-Triggered Journeys is not currently HIPAA eligible.
13
+
> Event-Triggered Journeys is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available.
Copy file name to clipboardexpand all lines: src/engage/journeys/journey-context.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ plan: engage-foundations
8
8
This page explains Journey context, which can help you dynamically adapt each journey to individual user interactions, creating highly relevant, real-time workflows.
9
9
10
10
> info "Public Beta"
11
-
> Event-Triggered Journeys is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. Event-Triggered Journeys is not currently HIPAA eligible.
11
+
> Event-Triggered Journeys is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available.
Copy file name to clipboardexpand all lines: src/privacy/data-retention-policy.md
+3
Original file line number
Diff line number
Diff line change
@@ -35,6 +35,9 @@ The default data retention period for each of the data types is as follows:
35
35
|**Team**| 365 days | Not applicable | 90 days | 365 days | Not applicable |
36
36
|**Free**| 180 days | Not applicable | 60 days | 180 days | Not applicable |
37
37
38
+
> info ""
39
+
> Segment calculates your data retention period starting from the date Segment ingests an event, not from the date an event originally occurred.
40
+
38
41
Through the self-serve Data Retention configuration in your workspace, you can configure a custom data retention period through the [Workspace Default Archive Retention Period](#workspace-default-archive-retention-period) setting.
39
42
40
43
Segment recommends keeping your data for at least 30 days to enable [replays](/docs/guides/what-is-replay/) of your data.
0 commit comments