From b9edf43b30963e75f2370aa4d8ea8a324cdbdd78 Mon Sep 17 00:00:00 2001
From: tbols17 <113375224+tbols17@users.noreply.github.com>
Date: Tue, 15 Jul 2025 09:02:15 -0700
Subject: [PATCH] Update Predictions Destination information.md

updated a list of destination identifiers that we explicitly support
---
 src/unify/Traits/predictions/index.md | 22 +++++++++++++++++++++-
 1 file changed, 21 insertions(+), 1 deletion(-)

diff --git a/src/unify/Traits/predictions/index.md b/src/unify/Traits/predictions/index.md
index 00e4a0e461..13b461d764 100644
--- a/src/unify/Traits/predictions/index.md
+++ b/src/unify/Traits/predictions/index.md
@@ -135,4 +135,24 @@ Segment then uses this criteria to build the prediction and create specific perc
 
 ## Use cases
 
-For use cases and information on how Segment builds prediction, read [Using Predictions](/docs/unify/traits/predictions/using-predictions/).
+Once a trait successfully computes, you can send them downstream to some destinations, or use them in an audience. Predictive Traits support destinations that support this list of identifiers:
+
+    ANONYMOUS = "anonymous_id"
+    USER = "user_id"
+    EMAIL = "email"
+    PHONE = "phone"
+    IOS_IDFA = "ios.idfa"
+    ANDROID_IDFA = "android.idfa"
+    GROUP = "group_id"
+    NAME = "name"
+    GA_CLIENT = "ga_client_id"
+    GOOGLE = "google_gid"
+    BRAZE = "braze_id"
+    SEGMENT = "segment_id"
+
+Other destinations may drop events published by Predictive Traits
+
+For use additional cases and information on how Segment builds prediction, read [Using Predictions](/docs/unify/traits/predictions/using-predictions/). 
+
+
+