Merge branch 'master' into DOC-780

Author: stayseesong

src/_data/sidenav/main.yml

@@ -390,6 +390,8 @@ sections:
       title: Audiences Overview
     - path: '/engage/audiences/account-audiences'
       title: Account-level Audiences
+    - path: '/engage/audiences/generative-audiences'
+      title: Generative Audiences
     - path: '/engage/audiences/organization'
       title: Organize Audiences
 

src/connections/sources/catalog/libraries/server/node/index.md

@@ -653,6 +653,46 @@ analytics.track({
 ```
 
 
+## OAuth 2.0
+
+> info ""
+> OAuth 2.0 is currently in private beta and is governed by Segment’s [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank"}.
+
+Enable [OAuth 2.0](/docs/connections/oauth/) in your Segment workspace to guarantee authorized communication between your server environment and Segment's Tracking API. To support the non-interactive server environment, the OAuth workflow used is a signed client assertion JWT.  
+
+You will need a public and private key pair where:
+- The public key is uploaded to the Segment dashboard. 
+- The private key is kept in your server environment to be used by this SDK. 
+
+Your server will verify its identity by signing a token request and will receive a token that is used to to authorize all communication with the Segment Tracking API.
+
+You'll need to provide the OAuth Application ID and the public key's ID, both of which are provided in the Segment dashboard.  There are also options available to specify the authorization server, custom scope, maximum number of retries, or a custom HTTP client if your environment has special rules for separate Segment endpoints.
+
+Be sure to implement handling for Analytics SDK errors. Good logging helps distinguish any configuration issues.
+
+For more information, see the [Segment OAuth 2.0 documentation](/docs/connections/oauth/).
+
+```ts
+import { Analytics, OAuthSettings } from '@segment/analytics-node';
+import { readFileSync } from 'fs'
+
+const privateKey = readFileSync('private.pem', 'utf8')
+
+const settings: OAuthSettings = {
+  clientId: '<CLIENT_ID_FROM_DASHBOARD>',
+  clientKey: privateKey,
+  keyId: '<PUB_KEY_ID_FROM_DASHBOARD>',
+}
+
+const analytics = new Analytics({
+  writeKey: '<MY_WRITE_KEY>',
+  oauthSettings: settings,
+})
+
+analytics.on('error', (err) => { console.error(err) })
+
+analytics.track({ userId: 'foo', event: 'bar' })
+```
 ## Troubleshooting
 
 {% include content/troubleshooting-intro.md %}

src/connections/sources/catalog/libraries/server/python/index.md

@@ -530,12 +530,49 @@ analytics.write_key = 'YOUR_WRITE_KEY'
 
 ## Google App Engine
 
-Google App Engine my not resolve project dependencies. If this is the case add the following to your project alongside analytics-python:
+Google App Engine may not resolve project dependencies. If this is the case add the following to your project alongside analytics-python:
 - [requests](https://github.com/kennethreitz/requests){:target="_blank"}
 - python-dateutil](https://github.com/paxan/python-dateutil){:target="_blank"}
 
 If you're having issues with threads outliving your request, check [Background threads and synchronous mode](#background-threads-and-synchronous-mode)
 
+## OAuth 2.0
+
+> info ""
+> OAuth 2.0 is currently in private beta and is governed by Segment’s [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank"}.
+
+Enable [OAuth 2.0](/docs/connections/oauth/) in your Segment workspace to guarantee authorized communication between your server environment and Segment's Tracking API. To support the non-interactive server environment, the OAuth workflow used is a signed client assertion JWT.  
+
+You will need a public and private key pair where:
+- The public key is uploaded to the Segment dashboard. 
+- The private key is kept in your server environment to be used by this SDK. 
+Your server will verify its identity by signing a token request and will receive a token that is used to to authorize all communication with the Segment Tracking API.
+
+You'll need to provide the OAuth Application ID and the public key's ID, both of which are provided in the Segment dashboard.  There are also options available to specify the authorization server, custom scope, maximum number of retries, or a custom HTTP client if your environment has special rules for separate segment endpoints.
+
+Be sure to implement handling for Analytics SDK errors. Good logging will help distinguish any configuration issues.
+
+For more information, see the [Segment OAuth 2.0 documentation](/docs/connections/oauth/).
+
+```python
+import segment.analytics as analytics
+with open("private_key.pem") as f:
+    privatekey = f.read()
+
+analytics.write_key = '<YOUR WRITE KEY HERE>'
+
+analytics.oauth_client_id = 'CLIENT_ID' # OAuth application ID from segment dashboard
+analytics.oauth_client_key = privatekey # generated as a public/private key pair in PEM format from OpenSSL
+analytics.oauth_key_id = 'KEY_ID' # From segment dashboard after uploading public key
+
+def on_error(error, items):
+    print("An error occurred: ", error)
+analytics.on_error = on_error
+
+analytics.track('AUser', 'track')
+analytics.flush()
+```
+
 ## Troubleshooting
 
 ### Request size limits

src/engage/audiences/generative-audiences.md

@@ -0,0 +1,117 @@
+---
+title: Generative Audiences
+beta: true
+plan: engage-foundations
+---
+ 
+> info "Generative Audiences is in private beta"
+> Generative Audiences is in private beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. [Contact Segment](https://segment.com/help/contact/){:target="_blank"} with any feedback or questions.
+
+With Generative Audiences, part of Segment's CustomerAI, use generative AI to create Engage Audiences with natural language prompts. 
+
+Describe your desired audience based on events performed, profile traits, or existing audiences in your workspace. Based on your prompt, Segment builds the audience with generative AI.
+
+In this article, you'll learn how to use Generative Audiences along with some best practices.
+ 
+## Create an audience with Generative Audiences
+
+To create an audience with Generative Audiences: 
+
+1. From the Segment app, navigate to **Engage > Audiences**.
+2. Click **+ New audience**, then select **Audience** from the dropdown menu.
+3. Select your audience type. Generative Audiences is available for all audience types except Linked Audiences.
+4. From the Build screen, click **Build with AI**.
+5. Enter your audience prompt in the description box. 
+- Use a minimum of 20 characters and up to 300 characters maximum. 
+6. Click **Build**. Based on your prompt, CustomerAI generates audience conditions for your review. 
+- Segment displays a progress bar until the audience conditions are generated.
+
+> success ""
+> To help you write your prompt, view these [example prompts](#example-prompts) and [best practices](#best-practices).
+
+### Modify an audience description 
+
+Once Segment generates the audience conditions, the prompt box remains open for reference. You can close this box, or modify your audience description and click **Build with AI** again. 
+
+Modifying an audience description overwrites the existing conditions previously generated. You can also edit any conditions straight from the audience builder. 
+
+## Example prompts
+
+Use the following examples to help you get started with audience prompts. 
+
+- To build an audience with customers who haven't made a purchase in the last 30 days, enter: `Customers who haven't purchased in the last 30 days.` 
+
+- To find all profiles that have recently opened an email, enter: `Profiles that recently opened an email.`
+
+- To build an audience with customers who spend over $50 on an order, enter: `Customers who have orders greater than $50.`
+
+> info ""
+> You'll have more accurate results if you base your audience prompts on specific events and traits that are in your Segment space.
+
+### Using negative conditions 
+
+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.   
+
+1. **Prompt**: "Customers who have not purchased in the last 30 days." 
+- **Expected output**: Segment generates audience conditions where *the event is performed at most 0 times*.
+
+2. **Prompt**: "Customers who don't have a phone number."
+- **Expected output**: Segment generates audience conditions where *the trait doesn't exist*.
+
+3. **Prompt**: "Customers who haven't received an email in the last 6 months."
+- **Expected output**: Segment generates audience conditions where *the event has been performed exactly 0 times*.
+
+## Best practices
+
+As you use Generative Audiences, keep the following best practices in mind:
+
+- Avoid using any customer Personal Identifiable Information (PII) or sensitive data. Personal, confidential, or sensitive information isn't required to use CustomerAI. 
+- Write specific descriptions. CustomerAI generates more accurate conditions when you use the names of existing events and traits. 
+- Ensure that all events and traits you reference exist in your workspace.
+- Try different prompts. If you don't receive what you want on the first try, rewrite your prompt. Submitting a new prompt replaces existing conditions.
+- Preview your audience to ensure you're matching with the correct profiles prior to moving on to the next step.
+
+### View events and traits in your workspace
+
+As you're writing your prompt, you can view traits and events that are active in your workspace from the audience builder. After you add a condition in the builder, click the property field to view active and inactive traits or events in your workspace. 
+
+You can also use the Profile explorer (**Unify** > **Profile explorer**) to view specific events and traits associated with profiles in your Segment space. 
+
+Learn more about [using existing events and traits](/docs/engage/audiences/) to build audiences. 
+ 
+> warning ""
+> Due to a [limited space schema](#limited-space-schema), CustomerAI may not recognize some events or traits that are inactive in your workspace. 
+ 
+## Error handling
+
+Engage uses the following error messages with Generative Audiences:
+
+| Error message        | Cause                  |
+|---------------------------|---------------------------------------|
+| Something went wrong      | An unknown exception occurred.                  |
+| Something went wrong. Try again later. | The AI service is down, or the LLM returned an error. |
+| Segment had trouble creating an audience from this description. Try rewording it using these [best practices](#best-practices). | The prompt referenced an invalid or non-existing trait, audience, or event within the workspace. You may also see this when an audience description is impossible to build or misunderstood. |
+
+## Known limitations
+
+### Limited space schema
+
+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.
+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. 
+
+### Language support
+
+At this time, Segment only supports audience description prompts in the English language. Support in other languages is currently unavailable and might provide undesired results. 
+
+
+## More about Segment's generative AI service
+
+#### How is my data used?
+
+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.
+
+Behind the scenes, Segment instructs GPT to generate an audience based on the user inputted audience description and contextual information such as traits and events performed in your workspace.
+
+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.
+
+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.