|
| 1 | +--- |
| 2 | +title: Generative Audiences |
| 3 | + |
| 4 | +--- |
| 5 | + |
| 6 | +Generative Audiences, part of Segment's CustomerAI, uses generative AI to create Engage Audiences with natural language prompts. |
| 7 | + |
| 8 | +Build audiences by describing your desired audience based on events performed, profile traits, or referencing existing audiences in your workspace. Based on your prompt, Segment builds the audience with Generative AI. |
| 9 | + |
| 10 | +In this article, you'll learn how to use Generative Audiences along with some best practices. |
| 11 | + |
| 12 | +<!-- CUT |
| 13 | +## Build an audience with Generative AI |
| 14 | +--> |
| 15 | + |
| 16 | +## Getting started with CustomerAI |
| 17 | +Use these steps to get started with CustomerAI: |
| 18 | +<!-- ask for a demo of this process --> |
| 19 | +1. From your message composer, select **Launch AI Copywriter**. |
| 20 | +2. In the drag-and-drop editor for in-app messages, select a text block and select in the block's toolbar. |
| 21 | +3. Enter a product name or description in the input field. |
| 22 | +4. Select the output language. This can be different from your input language. |
| 23 | +5. Select an appoximate output length. |
| 24 | +6. Click **Generate Copy**. |
| 25 | + |
| 26 | +## Create an audience with Generative Audiences |
| 27 | + |
| 28 | +To use Generative Audiences to create your audience: |
| 29 | + |
| 30 | +1. Navigate to **Engage > Audiences**, and click **+ New audience**. |
| 31 | +2. From the dropdown menu, select **Audience**. |
| 32 | +3. Select **Generative Audiences** as your audience type. Generative Audiences is available in all audience types except Linked Audiences. |
| 33 | +4. From the Build screen, click **Help me build**. |
| 34 | +5. Enter your prompt in the audience description box. |
| 35 | +- Use a minimum of 20 characters and up to 300 characters maximum. |
| 36 | +6. Click **Build**. Based on your prompt, CustomerAI generates audience conditions for you to review. |
| 37 | +- Segment displays a progress bar until the audience conditions are generated. |
| 38 | + |
| 39 | +> success "" |
| 40 | +> View some [example prompts](#use-cases-and-examples) and [best practices](#best-practices). |
| 41 | +
|
| 42 | +### Modify an audience description |
| 43 | + |
| 44 | +Once Segment generates the audience conditions, the prompt box will remain open for reference. You can close this box, or modify your audience description and click **Build** again. |
| 45 | + |
| 46 | +Modifying an audience overwrites the existing audience conditions Segment previously generated. |
| 47 | + |
| 48 | +> success "" |
| 49 | +> Once Segment generates the audience, you can adjust or remove any conditions straight from the audience builder. |
| 50 | +
|
| 51 | + |
| 52 | +## Use cases and examples |
| 53 | + |
| 54 | +View the table below for a few example prompts: |
| 55 | + |
| 56 | + |
| 57 | +| Audience description | Prompt | |
| 58 | +|------------------------|--------------------------------| |
| 59 | +| Build an audience with customers who haven't made a purchase in the last 30 days | "Customers who haven't purchased in the last 30 days." | |
| 60 | +| Build an audience with customers who spend over $50 on an order | "Customers who have orders greater than $50." | |
| 61 | +| Find all profiles that have recently opened an email. | "Profiles that recently opened an email." | |
| 62 | + |
| 63 | + |
| 64 | +## Best practices |
| 65 | + |
| 66 | +As you use generative audiences, keep the following best practices in mind: |
| 67 | + |
| 68 | +- Write specific descriptions. CustomerAI generates more accurate conditions when you use the names of existing events and traits. <!-- should I say "customerAI generates" or "Generative Audiences generates"? --> |
| 69 | +- Ensure that all events and traits you reference exist in your workspace. |
| 70 | +- Avoid using sensitive data, or customer Personal Identifiable Information (PII). |
| 71 | +- Experiment with your prompts. If you don't receive what you want on the first try, rewrite your prompt. Submitting a new prompt replaces existing conditions. |
| 72 | + |
| 73 | +> success "" |
| 74 | +> Segment recommends previewing your audience to ensure you're matching with the correct profiles prior to moving on to the next step. |
| 75 | +
|
| 76 | + |
| 77 | +## Known limitations |
| 78 | + |
| 79 | +### Limited Space Schema |
| 80 | + |
| 81 | +Segment's generative AI service is handled by a third party that needs to be fed 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. |
| 82 | + |
| 83 | +Event properties may not be populated due to this. |
| 84 | + |
| 85 | +### Foreign language support |
| 86 | + |
| 87 | +At this time, Segment only supports audience description prompts in the English language. Foreign language support is currently unavailable and might provide undesired results. |
| 88 | + |
| 89 | +### Negative conditions |
| 90 | + |
| 91 | +Audience descriptions around not having profile traits or users who have not performed certain events are expected to have their conditions configured in the following way: |
| 92 | + |
| 93 | +- "Customers who have not purchased in the last 30 days." |
| 94 | + |
| 95 | + |
| 96 | +The expected output is for Segment to generate a condition where the *event is performed at most 0 times*. |
| 97 | + |
| 98 | +- "Customers who don't have a phone number." |
| 99 | + |
| 100 | + |
| 101 | + |
| 102 | +The expected output is to generate a condition where the *trait doesn't exist*. |
| 103 | + |
| 104 | + |
| 105 | +## Error handling |
| 106 | + |
| 107 | +Engage uses the following error messages with Generative Audiences: |
| 108 | + |
| 109 | +| Error message | Cause | |
| 110 | +|---------------------------|---------------------------------------| |
| 111 | +| Something went wrong | This error displays when one of the following occur: <br> - Not found exception <br> - Invalid LLM output <br> - LLM error terminal <br> - Uknown exception | |
| 112 | +| Something went wrong. Try again later. | The AI service is down or the LLM returned an error. | |
| 113 | +| Segment had trouble creating an audience from this description. Try rewording it using these [best practices](#best-practices). | Referenced an invalid or non-existing trait, audience, or event within the workspace. You may also see this when an objective is impossible or misunderstood. | |
| 114 | + |
| 115 | + |
| 116 | +## More about Segment's Generative AI service |
| 117 | + |
| 118 | +#### How is my data used? |
| 119 | + |
| 120 | +In order to generate the audience based on your description, Segment sends your query to OpenAI, Segment's 3rd party AI service. All queries sent to OpenAI from Segment are anonymized, meaning that OpenAI won't be able to identify from whom the query was sent unless you include uniquely identifiable information in the input. |
| 121 | + |
| 122 | +Behind the scenes, Segment instructs GPT to generate an audience based on required parameters from Segment's system and contextual information such as traits and events performed in your workspace. |
| 123 | + |
| 124 | +GPT is OpenAI's state of the art natural language generation tool powered by artificial intelligence. It can perform a variety of natural language tasks like text generation, completion, and classification. CustomerAI uses the service to help generate audiences and inspire segmentation. |
| 125 | + |
| 126 | +Per OpenAI's policy, data sent to OpenAI's API with Segment isn't used to train or improve their models and will be deleted after 30 days. Any content generated using GPT is your intellectual property. Segment won't assert any claims of copyright ownership on such content and makes no warranty of any kind with respect to any AI generated content. |
0 commit comments