Merge branch 'segmentio:develop' into develop

Author: samir-moloco

src/_data/catalog/slugs.yml

@@ -209,8 +209,8 @@ destinations:
     override: "actions-aggregations-io"
   - original: "fullstory-cloud-mode-actions"
     override: "actions-fullstory-cloud"
-  - original: "actions-klayvio"
-    override: "klayvio-actions"
+  - original: "klaviyo-actions"
+    override: "actions-klaviyo"
   - original: "google-analytics-4-cloud"
     override: "actions-google-analytics-4"
   - original: "appfit"

src/connections/alerting.md

@@ -5,14 +5,13 @@ beta: true
 
 Connections Alerting allows Segment users to receive in-app, email, and Slack notifications related to the performance and throughput of an event-streaming connection. 
 
-
 To access Connections Alerting, select an event-streaming connection (like a web library source or cloud mode destination) and click the **Alerts** tab. 
 
 On the Alerts tab, you can create alerts and view all active alerts for this connection. You can only edit or delete the alerts that you create.
 
 ## Source volume alerts
 
-You can create an alert that notifies you when the volume of events received by your source in the last 24 hours changes beyond a percentage you set. For example, if you set a change percentage of 4%, Segment notifies you if your source ingests less than 96% or more than 104% of the event volume over the previous 24 hour period. 
+You can create an alert that notifies you when the volume of events received by your source in the last 24 hours changes beyond a percentage you set. For example, if you set a change percentage of 4% and your source received 100 events over the first 24 hours, Segment would notify you the following day if your source ingested fewer than 96 or more than 104 events.
 
 To receive a source volume alert in a Slack channel, you must first create a Slack webhook. For more information about Slack webhooks, see the [Sending messages using incoming webhooks](https://api.slack.com/messaging/webhooks){:target="_blank”} documentation.
 

src/connections/destinations/catalog/actions-display-video-360/index.md

@@ -133,7 +133,8 @@ After you complete the set up process, allow up to 24 hours for Google to create
 
 Segment will copy all of your existing Personas Display & Video 360 Destination configurations to Display and Video 360 (Actions). Once the migration is completed , you will be notified by email. 
 
-The sole mandatory action involves **re-authenticating** for each migrated Personans Display & Video 360 Destination. While you may already possess OAuth credentials, it is essential to undergo reauthentication. This step is necessary to seamlessly integrate new audiences or implement updates to existing ones.
+
+As of April 2, 2024, Segment no longer requires you to re-authenticate for existing Personas Display & Video 360 destinations. Segment, as an External Data Partner, now uses a set of Segment DMP credentials to authenticate on your behalf.  To add Segment as an External Data Partner, open Advertiser Settings, navigate to Linked Accounts, and then enable “Segment DMP”. 
 
 Segment is disabling all existing Personas Display and Video 360 destinations. You can still access your existing configuration, but please refrain from enabling the destination, as it is set to be deprecated. You will no longer be able to create new instances of Personas Display and Video 360.
 

src/connections/destinations/catalog/adwords-remarketing-lists/index.md

@@ -2,6 +2,8 @@
 title: Google Ads Remarketing Lists Destination
 strat: google
 hide-boilerplate: true
+hide-dossier: false
+hide-cmodes: true
 id: 5a6b50f1c900fa00011858fd
 ---
 

src/connections/destinations/catalog/klaviyo/index.md

@@ -15,8 +15,8 @@ Klaviyo lets you send personalized newsletters, automates triggered emails, prod
 
 To configure Klaviyo as an Event Source to get data into your warehouse or other downstream tools, see the [Klaviyo Source](/docs/connections/sources/catalog/cloud-apps/klaviyo/) documentation.
 
-> info
-> Klaviyo is deprecating the endpoints used by this destination in June 2024. Segment will not update this destination with the new endpoint. Instead, we recommend customers switch to the new Klaviyo Actions destination, which already uses the new endpoints.
+> info "Klaviyo deprecating v1/v2 APIs"
+> Klaviyo will deprecate the endpoints used by this destination in June 2024. Segment will not update this destination with the new endpoint. Instead, Segment recommends customers switch to the new [Klaviyo Actions destination](/docs/connections/destinations/catalog/actions-klaviyo/), which already uses the new endpoints.
 
 
 ## Getting started

src/connections/functions/destination-functions.md

@@ -433,6 +433,9 @@ If you're sending your batch to an external service, the execution time of the f
 
 {% include content/ip-allowlist.md %}
 
+##### Can I use a Destination Function to send data to another Segment source?
+Yes, to do so, remove the `messageId` and the `writeKey` from the payload in your Function code. Leaving either field on your payload will cause unexpected behavior that may cause your event to be delivered to the wrong source or to not be delivered at all.
+
 ##### Can I view console.log() outputs in Destination Functions?
 
 Incorporating console.log() statements in your Destination Function code aids in debugging. However, logs generated by these statements will only be accessible in the [Event Delivery](/docs/connections/event-delivery/) view if the payloads encounter errors during processing. Logs from successfully processed payloads are not displayed.

src/privacy/consent-management/consent-in-segment-connections.md

@@ -8,7 +8,12 @@ related:
 redirect_from: "/privacy/consent-in-segment-connections"
 ---
 
-Segment Connections users can add the [consent object](#consent-object) to their sources to stamp events with the end user consent preferences captured by your consent management platform (CMP) and send them downstream to destinations in categories that an end user consented to share data with. Events without the consent object continue to flow to destinations without consent enforcement. 
+Segment Connections users can add the [consent object](#consent-object) to their sources to stamp events with the end user consent preferences captured by your consent management platform (CMP) and send them downstream to destinations in categories that an end user consented to share data with. Events without the consent object continue to flow to destinations without consent enforcement.
+
+> success ""
+> With the [Destination Actions framework](/docs/connections/destinations/destination-actions), you can send current end user consent preferences to flow to your destination alongside customer interactions so your destinations know when an end user revokes their consent. 
+>
+> For more information about sharing current end user consent preferences with your downstream destinations, see the [Sharing consent with Actions destinations](/docs/privacy/consent-management/consent-in-unify/#sharing-consent-with-actions-destinations) documentation. 
 
 For more information about configuring consent categories, see the [Configure Consent Management](/docs/privacy/consent-management/configure-consent-management/#step-1-create-consent-categories-in-the-segment-app) documentation.
 

src/unified-profiles/segment-for-flex.md

@@ -13,7 +13,7 @@ Before creating a Segment for Flex workspace, you must have requested access fro
 ## Step 1: Select your data sources
 
 > warning "Unable to change data source selection after this step"
-> After you've selected your data source and proceeded to the next step, you can't return to this page and make a different selection. You can add additional data sources after setting up your Segment for Flex workspace. For more information about sources in a Segment for Flex workspace, see the [Sources](#sources) documentation.
+> After you've selected your data source and proceeded to the next step, you can't return to this page and make a different selection. You can add additional data sources after setting up your Segment for Flex workspace. For more information about adding additional data sources after completing the Segment for Flex guided setup, see the optional [Add additional sources and destinations to your workspace](#optional-add-additional-sources-and-destinations-to-your-workspace) documentation.
 
 1. In Segment for Flex, select a data source to get started and click **Next**.
 2. Review the popup that explains how the data source connects to Segment, and click **Continue**.
@@ -123,6 +123,34 @@ If the Enable Sources and Test Connections check indicates there are problems wi
 - [Profile Explorer](/docs/unify/#profile-explorer){:target="_blank"}: Use the Profile Explorer to view all user data, including event history, traits, and identifiers. 
 - [Advanced Segment](https://app.segment.com/goto-my-workspace/overview){:target="_blank"}: Use the Advanced Segment option to view your full Segment workspace. Segment recommends working with the assistance of Professional Services when accessing Advanced Segment.
 
+## (Optional) Add additional sources and destinations to your workspace
+
+After you complete the Segment for Flex guided setup, you can use [Advanced Segment](https://app.segment.com/goto-my-workspace/overview){:target="_blank"} to connect your workspace to additional *sources*, or websites, server libraries, mobile SDKs, and cloud applications that can send data into Segment, and *destinations*, or apps and business tools that can receive forwarded data from Segment.   
+
+See the [Segment for Flex entitlements and limitations](#segment-for-flex-entitlements-and-limitations) documentation for more information about the sources and destinations supported by Segment for Flex workspaces.
+
+### Add a source to your workspace
+
+> info "Eligible sources"
+> You can add up to 5 sources to your Segment for Flex workspace. For more information about the types of sources you can add to your workspace, see the [Sources](#sources) documentation.  
+
+To add a source to your Segment for Flex workspace:
+1. Open your Segment for Flex workspace in [Advanced Segment](https://app.segment.com/goto-my-workspace/overview){:target="_blank"} mode. 
+2. On the Your Segment Overview page, find the sources column and click **+ Add More**.
+3. Select the source you'd like to add to your workspace, and click **Next**.
+4. Follow the setup flow, and click **Done** to complete setting up your source.
+
+### Add a destination to your workspace
+
+> info "Eligible destinations"
+> You can add up to 3 destinations to your Segment for Flex workspace. For more information about the types of destinations you can add to your workspace, see the [Destinations](#destinations) documentation.  
+
+To add a destination to your Segment for Flex workspace:
+1. Open your Segment for Flex workspace in [Advanced Segment](https://app.segment.com/goto-my-workspace/overview){:target="_blank"} mode. 
+2. On the Your Segment Overview page, find the destinations column and click **Add Destination** if you haven't yet created any additional destinations, or **+ Add More** if you've already created an additional destination.
+3. Select the destination you'd like to add to your workspace, and click **Next**.
+4. Follow the setup flow, and click **Done** to complete setting up your source. 
+
 ## Segment for Flex entitlements and limitations
 
 Segment for Flex workspaces created during the Unified Profiles setup process have the following entitlements and limitations:

src/unify/Traits/custom-traits.md

@@ -5,7 +5,7 @@ title: Custom Traits
 
 Custom traits are user or account traits collected from the Identify calls you send to Segment. For example, these could be demographics like `age` or `gender`, account-specific like `plan`, or even things like whether a user has seen a particular A/B test variation. From your sources, send custom traits as pieces of information that you know about a user in an Identify call.
 
-As opposed to [computed traits](/docs/unify/traits/computed-traits/) which are computed from your source data, or [SQL Traits](/docs/unify/traits/sql-traits/) which are computed from warehouse data, custom traits are created from source events you pass into Segment. 
+As opposed to [computed traits](/docs/unify/traits/computed-traits/) which are computed from your source data, or [SQL Traits](/docs/unify/traits/sql-traits/) which are computed from warehouse data, custom traits are created from source events you pass into Segment and have no trait limits. 
 
 {% include content/trait-types.md %}
 

src/unify/Traits/sql-traits.md

@@ -278,3 +278,8 @@ If you experience issues saving the SQL Trait query or previewing the results of
 ### Why can't I see error messages in SQL traits while other users can?
 To see error messages in SQL traits, you will need to have PII Access.
 
+### If I edit the SQL Trait query, when will that edit apply those changes?
+The SQL Trait edit will apply to its next scheduled computational run. If the edit was made too closely to its next scheduled run, then its changes will be applied to the subsequent scheduled run, at which point you'll see those updates reflected on its user's profiles.
+
+### If I request a resync for my SQL Trait, when will that resync run?
+The SQL Trait resync will apply to its next scheduled computational run. If the resync was made too closely to its next scheduled run, then its changes will be applied to the subsequent scheduled run, at which point you'll see those updates reflected on its user's profiles.