Merge branch 'develop' of github.com:segmentio/segment-docs into develop

markzegarelli · markzegarelli · commit 747ca10ce6d8 · 2023-01-12T10:10:47.000-08:00
diff --git a/src/connections/sources/catalog/libraries/mobile/amp/index.md b/src/connections/sources/catalog/libraries/mobile/amp/index.md
@@ -39,6 +39,23 @@ Within your `<body>` tags, include the following Segment analytics snippet:
   ```
 Replace `WRITE_KEY` with the write key you obtain from the AMP Source you've set up within the Segment UI.
 
+For sources in [EU workspaces](/docs/guides/regional-segment/), use the following snippet:
+
+  ```html
+<amp-analytics type="segment">
+    <script type="application/json">
+    {
+      "vars": {
+        "writeKey": "<SOURCE_WRITE_KEY>"
+      },
+      "requests": {
+        "host": "https://events.eu1.segmentapis.com/v1/pixel"
+      }
+    }
+    </script>
+</amp-analytics>
+  ```
+
 By default, the snippet will automatically fire a page event which you can read more about [here](/docs/connections/sources/catalog/libraries/mobile/amp/#page).
 
 
diff --git a/src/connections/sources/catalog/libraries/mobile/swift-ios/index.md b/src/connections/sources/catalog/libraries/mobile/swift-ios/index.md
@@ -445,6 +445,7 @@ analytics.add(plugin: idfaPlugin)
 Segment supports these destinations for Analytics Swift, with more to come:
 * [Amplitude](https://github.com/segment-integrations/analytics-swift-amplitude){:target="_blank"}
 * [Appsflyer](https://github.com/segment-integrations/analytics-swift-appsflyer){:target="_blank"}
+* [Braze (Partner Maintained)](https://github.com/braze-inc/analytics-swift-braze){:target="_blank"}
 * [Facebook App Events](https://github.com/segment-integrations/analytics-swift-facebook-app-events){:target="_blank"}
 * [Firebase](https://github.com/segment-integrations/analytics-swift-firebase){:target="_blank"}
 * [Mixpanel](https://github.com/segment-integrations/analytics-swift-mixpanel){:target="_blank"}
diff --git a/src/connections/sources/index.md b/src/connections/sources/index.md
@@ -78,7 +78,7 @@ To create a source:
 {% include components/reference-button.html
   href="https://segment.com/academy/intro/"
   icon="symbols/squares-arrow.svg"
-  title="The Analytic Quickstart Guide"
+  title="The Analytics Quickstart Guide"
   description="Analytics and data collection is a very broad topic and it can be quite overwhelming. How do you get started?"
 %}
 
diff --git a/src/engage/audiences/computed-traits.md b/src/engage/audiences/computed-traits.md
@@ -175,6 +175,9 @@ To edit a real-time Trait, follow these steps:
 
 Engage then processes your Trait edits. While the edit task runs, the trait remains locked and you can't make further changes. Once Engage has finished incorporating your changes, you'll be able to access your updated Trait.
 
+> warning ""
+> It is not possible to edit a trait to convert it from real-time to batch, or vice-versa. If the computation type needs to be changed, you will need to recreate the trait with the appropiate conditions.
+
 ## Accessing your Computed Traits using the Profiles API
 
 You can access your computed traits using the Profile API by querying the `/traits` endpoint. For example, you can query for the `emails_opened_last_30_days` with the following GET request:
diff --git a/src/engage/audiences/index.md b/src/engage/audiences/index.md
@@ -132,6 +132,10 @@ Engage then processes your realtime Audience or Trait edits. While the edit task
 > warning ""
 > If your audience includes historical data (Historical Backfill is enabled), editing an audience creates a new backfill task. The backfill task, and therefore the edit task, take longer to process if the audience is connected to a destination with rate limits. Rate-limited destinations dictate how fast Engage can backfill. View a list of [rate-limited destinations](/docs/engage/using-engage-data/#rate-limits-on-engage-event-destinations).
 
+> warning ""
+> It is not possible to edit an audience to convert it from real-time to batch, or vice-versa. If the computation type needs to be changed, you will need to recreate the audience with the appropriate conditions.
+
+
 ## Access your Audiences using the Profiles API
 
 You can access your Audiences using the Profile API by querying the `/traits` endpoint. For example, you can query for `high_value_user` property with the following `GET` request:
diff --git a/src/engage/content/email/template.md b/src/engage/content/email/template.md
@@ -38,7 +38,7 @@ You can send test emails before you include a template in marketing campaigns
 1. Select the email template you want to test on the Templates screen.
 2. From the Template Settings page, click **Test Email**.
 3. Enter email addresses that will receive the test email.
-4. Choose a test profile with traits that apply to your marketing campaign and click **Use as Test Profile**.
+4. Choose a test profile with traits that apply to your marketing campaign and click **Use as Test Profile**. The selected profile must have a userId assigned to it.
 5. Select **Send Test Email**.
 
 > success ""
diff --git a/src/engage/content/sms/template.md b/src/engage/content/sms/template.md
@@ -31,7 +31,7 @@ Send a test SMS message before you include it as a step in your Journey.
 
 1. After you build your SMS template, click **Test SMS**.
 2. Enter recipient phone numbers for the test message.
-3. Select a profile to test the SMS with and click  **Use as Test Profile**. To ensure merge tags work as expected, use test profiles with traits that apply to your campaign.
+3. Select a profile to test the SMS with and click  **Use as Test Profile**. To ensure merge tags work as expected, use test profiles with traits that apply to your campaign. The selected profile must have a userId assigned to it.
 4. Click **Send Test SMS**.
 
 If a recipient replies "Stop" to the test SMS, Twilio unsubscribes their phone number and sends an opt-out confirmation.
diff --git a/src/protocols/transform/index.md b/src/protocols/transform/index.md
@@ -112,7 +112,7 @@ Here's a list of Segment Transformations with some use case examples.
 
 - **Update a property value:** Use [Segment's Public API](https://docs.segmentapis.com/tag/Transformations){:target="_blank"} to transform the property `currency` to have the value `USD`. 
 
-- **Add a new property name and assign a value:** If you want to create a new property and set a static value, use [Segment's Public API](https://docs.segmentapis.com/tag/Transformations){:target="_blank"} to create `new_property: static_value`.
+- **Add a new property name and assign a value:** If you want to create a new property and set a static value, use [Segment's Public API](https://docs.segmentapis.com/tag/Transformations){:target="_blank"} to create `new_property: static_value`. Segment currently supports setting static values for top-level fields with `propertyValueTransformations`. However, Segment doesn't support changing fields outside the properties or traits object with `propertyRenames`.
 
 {% comment %}
 - **Change property value casing:** Transform property value casing to lowercase, uppercase, or title case. For example, Transform the property value `united states` to `USA` to remain consistent with your data tracking.
