From 98bf8d9bdada7d0b8b7b37849fb119cccc4a73f2 Mon Sep 17 00:00:00 2001 From: pwseg Date: Tue, 26 Nov 2024 14:45:02 -0600 Subject: [PATCH] Add HIPAA ineligibility to callout --- src/engage/journeys/event-triggered-journeys.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/engage/journeys/event-triggered-journeys.md b/src/engage/journeys/event-triggered-journeys.md index 59716f8d2c..24de8a47e2 100644 --- a/src/engage/journeys/event-triggered-journeys.md +++ b/src/engage/journeys/event-triggered-journeys.md @@ -11,7 +11,7 @@ Unlike traditional audience-based journeys that rely on pre-defined user segment On this page, you'll learn how to create an event-triggered journey, configure entry conditions, and work with published event-triggered journeys. > info "Private Beta" -> Event-Triggered Journeys is in private beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. +> Event-Triggered Journeys is in private beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. During private beta, Event-Triggered Journeys is not HIPAA eligible. ## Overview