segmentio · pwseg · Oct 1, 2025 · Oct 1, 2025
@@ -21,9 +21,9 @@ To create an audience with Generative Audiences:
 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. 
+    - Use a minimum of 20 characters and up to 300 characters maximum. 
 6. Click **Build**. Based on your prompt, Segment generates audience conditions for your review. 
-- Segment displays a progress bar until the audience conditions are generated.
+    - 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).
@@ -55,13 +55,13 @@ Use the following examples to help you get started with audience prompts.
 This section shows a few examples of how Generative Audiences 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*.
+    - **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*.
+    - **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*.
+    - **Expected output**: Segment generates audience conditions where *the event has been performed exactly 0 times*.
 
 ## Best practices
 

@@ -233,8 +233,8 @@ To create a new audience or trait:
 1. Go to your **Computed Traits** or **Audiences** tab in Engage and select **Create**.
 
 2. Configure and preview your Audience or Trait.
-- A lightning bolt next to `Realtime Enabled` indicates that the computation updates in real-time.
-- Configure the **Include Historical Event Data** option to limit how far back event data is processed by setting a lookback window (for example, the “last 90 days”). When the **Include Historical Event Data** option is unchecked, Segment only uses event data received after audience creation. However, trait data is always included as part of the filtering criteria whenever it is defined in the audience as lookback windows don't apply to trait data since it represents a snapshot of profile attributes at a given time.
+    - A lightning bolt next to `Realtime Enabled` indicates that the computation updates in real-time.
+    - Configure the **Include Historical Event Data** option to limit how far back event data is processed by setting a lookback window (for example, the “last 90 days”). When the **Include Historical Event Data** option is unchecked, Segment only uses event data received after audience creation. However, trait data is always included as part of the filtering criteria whenever it is defined in the audience as lookback windows don't apply to trait data since it represents a snapshot of profile attributes at a given time.
 
 3. Select destinations to connect, then review and create your audience or trait.
 
@@ -324,9 +324,9 @@ To create an Activation event health spikes or drops alert:
 3. On the Create alert sidesheet, select the **Activation event health spikes or drops** alert and pick a destination for which you'd like to monitor event health. 
 4. Enter a percentage threshold to trigger activation event health notifications. 
 5. Select one or more of the following alert channels:
-  - **Email**: Select this to receive notifications at the provided email address. 
-  - **Slack**: Select this to send alerts to one or more channels in your workspace. You can post messages to your channel with either a [webhook](https://api.slack.com/messaging/webhooks){:target="_blank”} or a [workflow](https://slack.com/help/articles/360041352714-Build-a-workflow--Create-a-workflow-that-starts-outside-of-Slack){:target="_blank”}. 
-  - **In-app**: Select this to receive notifications in the Segment app. To view your notifications, select the bell next to your user icon in the Segment app. 
+    - **Email**: Select this to receive notifications at the provided email address. 
+    - **Slack**: Select this to send alerts to one or more channels in your workspace. You can post messages to your channel with either a [webhook](https://api.slack.com/messaging/webhooks){:target="_blank”} or a [workflow](https://slack.com/help/articles/360041352714-Build-a-workflow--Create-a-workflow-that-starts-outside-of-Slack){:target="_blank”}. 
+    - **In-app**: Select this to receive notifications in the Segment app. To view your notifications, select the bell next to your user icon in the Segment app. 
 6. Click **Save**.
 
 To make changes to an Activation event health spikes or drops alert, select the icon in the Actions column for the alert and click **Edit**. 
@@ -343,9 +343,9 @@ To create an Audience size change alert:
 3. On the Create alert sidesheet, select the **Audience size change alert** and pick a destination for which you'd like to monitor event health. 
 4. Enter a percentage threshold to trigger audience size change notifications. 
 5. Select one or more of the following alert channels:
-  - **Email**: Select this to receive notifications at the provided email address. 
-  - **Slack**: Select this to send alerts to one or more channels in your workspace. You can post messages to your channel with either a [webhook](https://api.slack.com/messaging/webhooks){:target="_blank”} or a [workflow](https://slack.com/help/articles/360041352714-Build-a-workflow--Create-a-workflow-that-starts-outside-of-Slack){:target="_blank”}. 
-  - **In-app**: Select this to receive notifications in the Segment app. To view your notifications, select the bell next to your user icon in the Segment app. 
+    - **Email**: Select this to receive notifications at the provided email address. 
+    - **Slack**: Select this to send alerts to one or more channels in your workspace. You can post messages to your channel with either a [webhook](https://api.slack.com/messaging/webhooks){:target="_blank”} or a [workflow](https://slack.com/help/articles/360041352714-Build-a-workflow--Create-a-workflow-that-starts-outside-of-Slack){:target="_blank”}. 
+    - **In-app**: Select this to receive notifications in the Segment app. To view your notifications, select the bell next to your user icon in the Segment app. 
 6. Click **Save**.
 
 To make changes to an Audience size change alert, select the icon in the Actions column for the alert and click **Edit**. 
@@ -384,11 +384,11 @@ You can download a copy of your Audience by visiting the Audiences overview page
 1. Navigate to **Engage > Audiences**.
 2. Select the Audience you'd like to download as a CSV, then click **Download CSV**.
 3. Select the data fields that you'd like to include in your CSV as columns.
-- Your CSV contains all users in this audience with the selected fields. You can filter by `External ID`, `SQL trait`, `Computed Trait`, and `Custom Trait`.
+    - Your CSV contains all users in this audience with the selected fields. You can filter by `External ID`, `SQL trait`, `Computed Trait`, and `Custom Trait`.
 4. Click **Next**.
 5. Before you can download the CSV, you'll need to generate it. There are two different options for formatting:
-- **Formatted:** Displays external IDs and traits as distinct columns.  
-- **Unformatted:** Contains the following columns: a user/account key, a JSON object containing the external IDs (optional, if selected), and a JSON object containing the traits (optional, if selected).
+    - **Formatted:** Displays external IDs and traits as distinct columns.  
+    - **Unformatted:** Contains the following columns: a user/account key, a JSON object containing the external IDs (optional, if selected), and a JSON object containing the traits (optional, if selected).
 6. Click **Generate CSV**.
 
 Once Segment generates the CSV, you can download the file directly. You'll receive an email notification of the CSV completion, with a URL to the Audience overview page. Generating a CSV can take a substantial amount of time for large audiences. After you generate the CSV file, leave the modal window open while Segment creates the file. If the audience recalculates between when you click Generate and when you download the file, you might want to regenerate the file. The CSV is a snapshot from when you clicked Generate, and could be outdated.
@@ -397,7 +397,7 @@ Note the following limits for the CSV downloader:
 - You can't download more than one CSV for the same audience at the same time.
 - You can only generate one CSV every five minutes.
 - Each CSV represents a snapshot at a given point in time that references the data from the audience's most recent computational run. This applies to both real time and batch audiences, as the CSV is not updated in real time. To locate the snapshot's given point of time, click on the Download CSV button, and the popup modal will contain an information icon ℹ️, which when hovered over will reveal the snapshot's details.
-  - ![CSV Snapshot details](https://github.com/user-attachments/assets/b7af772a-2ba7-4411-ba95-a913992f10ae)
+    - ![CSV Snapshot details](https://github.com/user-attachments/assets/b7af772a-2ba7-4411-ba95-a913992f10ae)
 
 > warning ""
 > You can't add account traits and identifiers using the CSV downloader with account-level audiences. This is because every row listed in the CSV file is a user, and since account traits and identifiers only exist on accounts, they wouldn't exist as a user's custom trait and appear on the CSV.

@@ -45,7 +45,6 @@ Follow these steps to integrate Analytics Kotlin:
 ```java
  <uses-permission android:name="android.permission.INTERNET"/>
  <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>
-
 ```
 
 For detailed instructions on integrating Analytics Kotlin, follow the steps in the [Analytics Kotlin getting started section](/docs/connections/sources/catalog/libraries/mobile/kotlin-android#getting-started).
@@ -262,8 +261,8 @@ Next, you’ll create a push notification certificate, which lets your app recei
 3. If you are using the Quickstart app and see a provisioning error message, you may need to rename the bundle ID to a unique identifier. To do so, [give your bundle a new name](https://developer.apple.com/account/resources/certificates/list){:target="_blank"}, then enter your new identifier in the **Identity** section of the General pane.
 4. Go to the **Capabilities** tab and make sure that Push Notifications are enabled.
 5. Verify that you successfully created your certificates:
-- Sign in to the Apple developer portal and click on  **Certificates, IDs & Profile**. In the **Certificates** section, select **Development** or **Production**, depending on the type of certificate you want to verify.
-- Alternatively, go to **Applications > Utilities > Keychain Access** and select **Certificates**. Search for `iPhone`, and verify that your certificate has a disclosure triangle, which indicates that your private key exists in the keychain.
+    - Sign in to the Apple developer portal and click on  **Certificates, IDs & Profile**. In the **Certificates** section, select **Development** or **Production**, depending on the type of certificate you want to verify.
+    - Alternatively, go to **Applications > Utilities > Keychain Access** and select **Certificates**. Search for `iPhone`, and verify that your certificate has a disclosure triangle, which indicates that your private key exists in the keychain.
 
 #### Option 2: Manually create a certificate
 
@@ -350,9 +349,9 @@ Follow these steps to set up mobile push in Twilio Engage.
 6. Copy and save both the **SID** and **Secret** field contents.
 7. Return to the API keys & tokens page. In the **Live credentials** section, copy the Account SID credentials.
 8. Return to your Segment workspace and navigate to **Engage > Engage settings > Channels**.  Under **SMS Service with Twilio**, click the **Get Started** button. The **Set up and validate your Twilio account** page appears.
-11. Under **Enter your Twilio API Key information**, paste the Account SID, API Key SID, and API Key Secret you copied above into their corresponding fields.
-12. Click **Verify**, then select the messaging services you want to use in your space.
-13. Click **Save Twilio Account.**
+9. Under **Enter your Twilio API Key information**, paste the Account SID, API Key SID, and API Key Secret you copied above into their corresponding fields.
+10. Click **Verify**, then select the messaging services you want to use in your space.
+11. Click **Save Twilio Account.**
 
 > info "Removing messaging services"
 > To remove a messaging service, navigate to Engage > Engage settings > Channels and click the pencil icon under **Twilio messaging service**. Enter the account credentials by either using the API key secret or creating a new API key. Once you've selected the desired services, they will override the existing ones, effectively removing the ones you no longer need.
@@ -361,11 +360,11 @@ Follow these steps to set up mobile push in Twilio Engage.
 
 Complete mobile push onboarding by creating a new push service:
 
-2. In your Segment workspace, navigate to **Engage > Engage settings**.
-3. Click the pencil icon next to **Messaging services**, then click **Create new push service**.
+1. In your Segment workspace, navigate to **Engage > Engage settings**.
+2. Click the pencil icon next to **Messaging services**, then click **Create new push service**.
     - If you don't see the pencil icon, select **Create new push service**.
-4. Name the push service, select or create APN and FCM credentials, then click **Create Push Service**.
-5. Your new messaging service appears in the **Add messaging services** dropdown. Select it, then click **Save**.
+3. Name the push service, select or create APN and FCM credentials, then click **Create Push Service**.
+4. Your new messaging service appears in the **Add messaging services** dropdown. Select it, then click **Save**.
 
 ## Build a mobile push template
 

@@ -4,6 +4,7 @@ plan: engage-premier
 ---
 > info "Engage Premier End of Life"
 > Engage Premier features, including Channels, Broadcasts, content templates, and Subscriptions, will no longer be available after December 15, 2025. 
+
 To add structure to your marketing content, you can organize templates into folders and duplicate them within your Segment space.
 
 ## Organize with folders
@@ -50,8 +51,8 @@ To duplicate an email, SMS, or push template:
 2. Select the tab for the template type (Email, SMS, or Push) you'd like to clone.
 3. Select the **...** icon next to your template, then click **Duplicate**.
 4. Configure your duplicate template:
-- For SMS and push, edit your template, and save the duplicate once you're finished.
-- For email, add a template name on the **Duplicate Template** popup screen, then click **Duplicate**. You can then edit your email template from the Templates page.
+    - For SMS and push, edit your template, and save the duplicate once you're finished.
+    - For email, add a template name on the **Duplicate Template** popup screen, then click **Duplicate**. You can then edit your email template from the Templates page.
 
 Learn more about configuring [email](/docs/engage/content/email/template/), [SMS](/docs/engage/content/sms/template/), and [push](/docs/engage/content/mobile-push/) templates.
 

@@ -133,7 +133,7 @@ Segment **doesn't** copy the following:
 5. Review the duplicated journey and make any needed changes.
 6. If your journey includes destination sends, be sure to copy the new destination keys into your destination system.
 
-> warning
+> warning ""
 > Currently, you can only duplicate journeys within the same Engage space. Duplicating across spaces or workspaces is not supported.
 
 ## Best practices

@@ -131,8 +131,8 @@ You’ll now need to enable event webhooks, which trigger webhook notifications
 2. Click the pencil edit icon next to **Event Webhook**.
 3. On the Event Webhook page, set authorization method to none.
 4. Copy and paste the following URL, depending on your region,  into the **HTTP Post URL** field:
-  - US: `https://engage-ma-webhook-api.engage.segment.com/sendgrid`
-  - EU:`https://engage-ma-webhook-api.euw1.engage.segment.com/sendgrid`
+    - US: `https://engage-ma-webhook-api.engage.segment.com/sendgrid`
+    - EU:`https://engage-ma-webhook-api.euw1.engage.segment.com/sendgrid`
 
     ![Adding the HTTP Post URL](images/webhook.png "Adding the HTTP Post URL")
 
@@ -262,7 +262,7 @@ To send WhatsApp messages in Twilio Engage, you'll register a Twilio number with
 ### Register a Twilio number with WhatsApp
 
 1. [Purchase an SMS-capable phone number](https://support.twilio.com/hc/en-us/articles/223135247-How-to-Search-for-and-Buy-a-Twilio-Phone-Number-from-Console){:target="_blank"} within your Twilio Console.
-  - For international numbers, view Twilio's [Phone Number Regulations](https://www.twilio.com/en-us/guidelines/regulatory){:target="_blank"} guidelines. 
+    - For international numbers, view Twilio's [Phone Number Regulations](https://www.twilio.com/en-us/guidelines/regulatory){:target="_blank"} guidelines. 
 2. From the Twilio side menu, navigate to **Messaging > Senders > WhatsApp Senders**.
 3. Select **Create new sender**.
 4. From the **New Sender** builder, find **Twilio phone number**, then choose the phone number you purchased in Step 1. Select **Continue**.

@@ -60,8 +60,10 @@ You can use these characters in your CSV file:
 - The following non-English characters:
 
 
-```àáâäǎæãåāçćčċďðḍèéêëěẽēėęğġgg͟hħḥh̤ìíîïǐĩīıįķk͟hłļľl̥ṁm̐òóôöǒœøõōřṛr̥ɽßşșśšṣs̤s̱sțťþṭt̤ʈùúûüǔũūűůŵýŷÿźžżẓz̤ÀÁ
-ÄǍÆÃÅĀÇĆČĊĎÐḌÈÉÊËĚẼĒĖĘĞĠGG͟HĦḤH̤ÌÍÎÏǏĨĪIĮĶK͟HŁĻĽL̥ṀM̐ÒÓÔÖǑŒØÕŌŘṚR̥ɌSẞŚŠŞȘṢS̤S̱ȚŤÞṬT̤ƮÙÚÛÜǓŨŪŰŮŴÝŶŸŹŽŻẒZ```
+```
+àáâäǎæãåāçćčċďðḍèéêëěẽēėęğġgg͟hħḥh̤ìíîïǐĩīıįķk͟hłļľl̥ṁm̐òóôöǒœøõōřṛr̥ɽßşșśšṣs̤s̱sțťþṭt̤ʈùúûüǔũūűůŵýŷÿźžżẓz̤ÀÁ
+ÄǍÆÃÅĀÇĆČĊĎÐḌÈÉÊËĚẼĒĖĘĞĠGG͟HĦḤH̤ÌÍÎÏǏĨĪIĮĶK͟HŁĻĽL̥ṀM̐ÒÓÔÖǑŒØÕŌŘṚR̥ɌSẞŚŠŞȘṢS̤S̱ȚŤÞṬT̤ƮÙÚÛÜǓŨŪŰŮŴÝŶŸŹŽŻẒZ
+```
 
 ## View Update History