Merge pull request #7171 from segmentio/develop

pwseg · web-flow · commit f955a6d3d41a · 2024-10-24T14:23:12.000-05:00
Release 24.43.2
diff --git a/CODEOWNERS b/CODEOWNERS
@@ -47,7 +47,7 @@ CODEOWNERS  @segmentio/segment-doc-team
 /src/unify @pwseg 
 
 # Protocols owners
-/src/protocols @forstisabella
+/src/protocols @forstisabella @pwseg
 
 # Storage owners
-/src/connections/storage @forstisabella
+/src/connections/storage @forstisabella @pwseg
diff --git a/src/_data/catalog/destination_categories.yml b/src/_data/catalog/destination_categories.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination categories last updated 2024-10-22 
+# destination categories last updated 2024-10-24 
 items:
 - display_name: A/B Testing
   slug: a-b-testing
diff --git a/src/_data/catalog/destinations.yml b/src/_data/catalog/destinations.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2024-10-22 
+# destination data last updated 2024-10-24 
 items:
 - id: 637e8d185e2dec264895ea89
   display_name: 1Flow
diff --git a/src/_data/catalog/destinations_private.yml b/src/_data/catalog/destinations_private.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2024-10-22 
+# destination data last updated 2024-10-24 
 items:
   - id: 54521fd925e721e32a72eee1
     display_name: Pardot
diff --git a/src/_data/catalog/source_categories.yml b/src/_data/catalog/source_categories.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# source categories last updated 2024-10-22 
+# source categories last updated 2024-10-24 
 items:
   - display_name: A/B Testing
     slug: a-b-testing
diff --git a/src/_data/catalog/sources.yml b/src/_data/catalog/sources.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# sources last updated 2024-10-22 
+# sources last updated 2024-10-24 
 items:
   - id: 8HWbgPTt3k
     display_name: .NET
diff --git a/src/assets/pdf/Segment_VAT_GST_FAQ.pdf b/src/assets/pdf/Segment_VAT_GST_FAQ.pdf
diff --git a/src/assets/pdf/faq-segment-dissolution-vat.pdf b/src/assets/pdf/faq-segment-dissolution-vat.pdf
diff --git a/src/connections/functions/insert-functions.md b/src/connections/functions/insert-functions.md
@@ -500,6 +500,10 @@ However, if your function aims to enrich event data by fetching additional infor
 
 No, Destination Insert Functions are currently available for use with Cloud Mode (server-side) destinations only. Segment is in the early phases of exploration and discovery for supporting customer web plugins for custom Device Mode destinations and other use cases, but this is unsupported today.
 
+##### Can I use Insert Functions with Storage destinations?
+
+Insert Functions are only supported by Cloud Mode (server-side) destinations and aren't compatible with Storage destinations.
+
 ##### Can I connect an insert function to multiple destinations?
 
 Yes, an insert function can be connected to multiple destinations. 
diff --git a/src/engage/faqs.md b/src/engage/faqs.md
@@ -151,3 +151,7 @@ Based on Engage behavior, standard source events such as Page, Track and Identif
 ## Why can't I connect the audience/computed trait to an existing destination in my workspace?
 
 Engage will not allow you to connect an audience/computed trait to a destination that is already linked to a [Connections-based source](/docs/connections/sources/). Instead, create a new instance of the destination with the correct Engage space selected as the data source.
+
+## How are the "5 most common values" for traits calculated?
+
+The "5 most common values" are the most frequently observed values for a given trait across all users, not tied to any individual user.
diff --git a/src/guides/usage-and-billing/billing.md b/src/guides/usage-and-billing/billing.md
@@ -34,7 +34,7 @@ All Segment customers with a US business address may be subject to state and loc
 
 Segment collects Value Added Tax (VAT) and Goods and Services Tax (GST) on the services sold to its international customers located in certain foreign jurisdictions. 
 
-For more information about sales tax, VAT, and GST, see the [Segment VAT/GST FAQs](/docs/assets/pdf/faq-segment-dissolution-vat.pdf).
+For more information about sales tax, VAT, and GST, see the [Segment VAT/GST FAQs](/docs/assets/pdf/Segment_VAT_GST_FAQ.pdf).
 
 
 ## Do I qualify for a tax exemption?
diff --git a/src/unify/Traits/predictions/using-predictions.md b/src/unify/Traits/predictions/using-predictions.md
@@ -126,3 +126,7 @@ Yes. Keep the following in mind when you work with Predictions:
 - **Predictions will not work as intended if you track more than 5,000 unique events in your workspace.**
 - **Prediction is failing with error "We weren't able to create this prediction because your requested prediction event is not being tracked anymore. Please choose a different prediction event and try again."** Predictions are computed based on the available data and the conditions specified for the trait. A gap in tracking events for seven continuous days could potentially affect the computation of the prediction.
 Nevertheless, once data tracking resumes and there is enough data, the prediction should be recomputed.
+
+#### How is the average calculated?
+
+The probabilities for all users are added together and then divided by the total number of users. If a user's score in "Likelier to convert than average" is below 1, it means they are less likely than the average user to convert.
diff --git a/src/unify/data-graph/setup-guides/databricks-setup.md b/src/unify/data-graph/setup-guides/databricks-setup.md
@@ -67,9 +67,7 @@ Run the following SQL to grant your Service Principal user read-only access to a
 GRANT USAGE, SELECT, USE SCHEMA ON CATALOG `${catalog}` TO `${client_id}`;
 ```
 
-## (Optional) Step 5: Restrict read-only access
-
-### Restrict read-only access to schemas
+## (Optional) Step 5: Restrict read-only access to schemas
 
 Restrict access to specific schemas by running the following SQL:
 
@@ -79,19 +77,6 @@ USE CATALOG `${catalog}`;
 GRANT USAGE, SELECT ON SCHEMA `${schema_1}` TO `${client_id}`;
 GRANT USAGE, SELECT ON SCHEMA `${schema_2}` TO `${client_id}`;
 ...
-```
-### Restrict read-only access to tables
-Restrict access to specific tables by running the following SQL: 
-
-```sql
-GRANT USAGE ON CATALOG `${catalog}` TO `${client_id}`;
-USE CATALOG `${catalog}`;
-GRANT USAGE ON SCHEMA `${schema_1}` TO `${client_id}`;
-USE SCHEMA `${schema_1}`;
-GRANT SELECT ON TABLE `${table_1}` TO `${client_id}`;
-GRANT SELECT ON TABLE `${table_2}` TO `${client_id}`;
-...
-
 ```
 
 ## Step 6: Validate the permissions of your Service Principal user
diff --git a/src/unify/profile-api.md b/src/unify/profile-api.md
@@ -243,7 +243,7 @@ All top-level API resources have support for bulk fetches using "list" API metho
 Each API request has an associated request identifier. You can find this value in the response headers, under `Request-Id`.
 
 ```bash
-curl -i https://profiles.segment.com/v1/spaces/<space_id>/collections/users/profiles
+curl -i https://profiles.segment.com/v1/spaces/<space_id>/collections/users/profiles/<identifier>/metadata
 HTTP/1.1 200 OK
 Date: Mon, 01 Jul 2013 17:27:06 GMT
 Status: 200 OK
