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/engage/audiences/customerAI-audiences.md
+17-16Lines changed: 17 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,6 +48,19 @@ Use the following examples to help you get started with audience prompts.
48
48
> info ""
49
49
> You'll have more accurate results if you base your audience prompts on specific events and traits that are in your Segment space.
50
50
51
+
### Using negative conditions
52
+
53
+
Below are a few examples of how CustomerAI configures audience conditions for negative prompts. Negative conditions might include, for example, building an audience of users without a certain profile trait, or who haven't performed certain events.
54
+
55
+
1.**Prompt**: "Customers who have not purchased in the last 30 days."
56
+
-**Expected output**: Segment generates audience conditions where *the event is performed at most 0 times*.
57
+
58
+
2.**Prompt**: "Customers who don't have a phone number."
3.**Prompt**: "Customers who haven't received an email in the last 6 months."
62
+
-**Expected output**: Segment generates audience conditions where *the event has been performed exactly 0 times*.
63
+
51
64
## Best practices
52
65
53
66
As you build audiences with CustomerAI, keep the following best practices in mind:
@@ -64,23 +77,10 @@ As you're writing your prompt, you can view traits and events that are active in
64
77
65
78
You can also use the Profile explorer (**Unify** > **Profile explorer**) to view specific events and traits associated with profiles in your Segment space.
66
79
67
-
Learn more about [using existing events and traits](/docs/engage/audiences/#building-an-audience) to build audiences.
80
+
Learn more about [using existing events and traits](/docs/engage/audiences/) to build audiences.
68
81
69
82
> warning ""
70
83
> Due to a [limited space schema](#limited-space-schema), CustomerAI may not recognize some events or traits that are inactive in your workspace.
71
-
72
-
### Using negative conditions
73
-
74
-
Below are a few examples of how CustomerAI configures audience conditions for negative prompts. Negative conditions might include, for example, building an audience of users without a certain profile trait, or who haven't performed certain events.
75
-
76
-
1.**Prompt**: "Customers who have not purchased in the last 30 days."
77
-
-**Expected output**: Segment generates audience conditions where *the event is performed at most 0 times*.
78
-
79
-
2.**Prompt**: "Customers who don't have a phone number."
3.**Prompt**: "Customers who haven't received an email in the last 6 months."
83
-
-**Expected output**: Segment generates audience conditions where *the event has been performed exactly 0 times*.
84
84
85
85
## Error handling
86
86
@@ -94,9 +94,10 @@ Engage uses the following error messages with CustomerAI audiences:
94
94
95
95
## Known limitations
96
96
97
-
### Limited space schema
97
+
### Limited space schema
98
98
99
-
Segment's generative AI service is handled by a third party that needs context about your Engage workspace and has limitations to how many contextual parameters Segment can send it. Because of this, Segment limits the amount of data it sends to the AI service. Segment solves this limitation by including up to 100,000 of the most recently used events and traits in your Engage space. As a result, some event properties may not be populated.
99
+
Segment's generative AI service is handled by a third party that needs context about your Engage workspace and has limitations to how many contextual parameters Segment can send it.
100
+
Segment solves this limitation by including only the most recently used properties and values for events and traits within your Engage space. As a result, some event and traits within your workspace may not be recognized.
0 commit comments