diff --git a/src/_data/catalog/destination_categories.yml b/src/_data/catalog/destination_categories.yml index 56c3981edb..d6fd5f95ee 100644 --- 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-17 +# destination categories last updated 2024-10-22 items: - display_name: A/B Testing slug: a-b-testing diff --git a/src/_data/catalog/destinations.yml b/src/_data/catalog/destinations.yml index 108a4a8b78..d7d42e3ccc 100644 --- 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-17 +# destination data last updated 2024-10-22 items: - id: 637e8d185e2dec264895ea89 display_name: 1Flow @@ -33239,8 +33239,10 @@ items: slug: actions-dynamic-yield-audiences hidden: false endpoints: + - EU - US regions: + - eu-west-1 - us-west-2 url: connections/destinations/catalog/actions-dynamic-yield-audiences previous_names: @@ -111820,6 +111822,14 @@ items: mobile: true server: true settings: + - name: allowUserIdFallback + type: boolean + defaultValue: false + description: >- + If an event is missing the Override-value, you can allow these events to + UserId on the event instead. + required: false + label: Allow Fallback to UserId when an override field does not exist on an event - name: apiKey type: string defaultValue: '' diff --git a/src/_data/catalog/destinations_private.yml b/src/_data/catalog/destinations_private.yml index 4869e4029e..6b02b50f8d 100644 --- 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-17 +# destination data last updated 2024-10-22 items: - id: 54521fd925e721e32a72eee1 display_name: Pardot diff --git a/src/_data/catalog/source_categories.yml b/src/_data/catalog/source_categories.yml index b81a003531..c8bf3c67c1 100644 --- 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-17 +# source categories last updated 2024-10-22 items: - display_name: A/B Testing slug: a-b-testing diff --git a/src/_data/catalog/sources.yml b/src/_data/catalog/sources.yml index 67d447c702..5b1a50727f 100644 --- 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-17 +# sources last updated 2024-10-22 items: - id: 8HWbgPTt3k display_name: .NET diff --git a/src/connections/destinations/catalog/actions-braze-cloud/index.md b/src/connections/destinations/catalog/actions-braze-cloud/index.md index 0db913dff1..c332f1969b 100644 --- a/src/connections/destinations/catalog/actions-braze-cloud/index.md +++ b/src/connections/destinations/catalog/actions-braze-cloud/index.md @@ -3,9 +3,11 @@ title: Braze Cloud Mode (Actions) Destination hide-boilerplate: true hide-dossier: false id: 60f9d0d048950c356be2e4da +redirect_from: + - '/connections/destinations/catalog/braze-cloud-mode-actions/' versions: - name: 'Braze Web Mode (Actions)' - link: '/docs/connections/destinations/catalog/braze-web-device-mode-actions/' + link: '/docs/connections/destinations/catalog/actions-braze-web/' - name: 'Braze (Classic)' link: '/docs/connections/destinations/catalog/braze' --- diff --git a/src/connections/destinations/catalog/actions-braze-web/index.md b/src/connections/destinations/catalog/actions-braze-web/index.md index d5a8d40aca..62f7d07f8f 100644 --- a/src/connections/destinations/catalog/actions-braze-web/index.md +++ b/src/connections/destinations/catalog/actions-braze-web/index.md @@ -4,10 +4,11 @@ hide-boilerplate: true hide-dossier: false redirect_from: - '/connections/destinations/catalog/vendor-braze/' + - '/connections/destinations/catalog/braze-web-device-mode-actions/' id: 60fb01aec459242d3b6f20c1 versions: - name: 'Braze Cloud Mode (Actions)' - link: '/docs/connections/destinations/catalog/braze-cloud-mode-actions' + link: '/docs/connections/destinations/catalog/actions-braze-cloud' - name: 'Braze (Classic)' link: '/docs/connections/destinations/catalog/braze' --- diff --git a/src/connections/destinations/catalog/braze/index.md b/src/connections/destinations/catalog/braze/index.md index 2406ad1ae4..969131a11c 100644 --- a/src/connections/destinations/catalog/braze/index.md +++ b/src/connections/destinations/catalog/braze/index.md @@ -5,7 +5,7 @@ hide-personas-partial: true hide-integrations-object: true maintenance: true maintenance-content: > - Future updates to this destination are limited to security updates and bug fixes. New versions of this destination are available. See [Braze Cloud Mode (Actions)](/docs/connections/destinations/catalog/braze-cloud-mode-actions) for a server-side integration and [Braze Web Mode (Actions)](/docs/connections/destinations/catalog/braze-web-device-mode-actions) for a device-mode integration with access to Braze SDK features. + Future updates to this destination are limited to security updates and bug fixes. New versions of this destination are available. See [Braze Cloud Mode (Actions)](/docs/connections/destinations/catalog/actions-braze-cloud) for a server-side integration and [Braze Web Mode (Actions)](/docs/connections/destinations/catalog/actions-braze-web) for a device-mode integration with access to Braze SDK features.
If you use a Braze mobile [device-mode connection](/docs/connections/destinations/#connection-modes), for example to use Braze Content Cards or In-App Messaging, use the Braze (Classic) Destination. Segment will continue to make updates to the Segment Braze mobile device-mode SDK. diff --git a/src/connections/functions/source-functions.md b/src/connections/functions/source-functions.md index 2a83322376..646db8e948 100644 --- a/src/connections/functions/source-functions.md +++ b/src/connections/functions/source-functions.md @@ -434,3 +434,7 @@ No. Tracking Pixels operate client-side only and need to be loaded onto your web ##### What is the maximum data size that can be displayed in console.logs() when testing a Function? The test function interface has a 4KB console logging limit. Outputs surpassing this limit will not be visible in the user interface. + +#### Can I send a custom response from my Source Function to an external tool? + +No, Source Functions can't send custom responses to the tool that triggered the Function's webhook. Source Functions can only send a success or failure response, not a custom one. diff --git a/src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md b/src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md index 13ffb41f51..ba9c0f9542 100644 --- a/src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md +++ b/src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md @@ -3,7 +3,7 @@ title: BigQuery Reverse ETL Setup redirect_from: - '/reverse-etl/bigquery-setup/' --- -To set up your BigQuery source with Reverse ETL, you must [construct a BigQuery role and service account](#constructing-your-own-role-or-policy] and [create a BigQuery source in the Segment app](#set-up-bigquery-as-your-reverse-etl-source). +To set up your BigQuery source with Reverse ETL, you must [construct a BigQuery role and service account](#constructing-your-own-role-or-policy) and [create a BigQuery source in the Segment app](#set-up-bigquery-as-your-reverse-etl-source). > info "BigQuery Reverse ETL sources support Segment's dbt extension" > If you have an existing dbt account with a Git repository, you can use [Segment's dbt extension](/docs/segment-app/extensions/dbt/) to centralize model management and versioning, reduce redundancies, and run CI checks to prevent breaking changes. diff --git a/src/connections/sources/about-cloud-sources.md b/src/connections/sources/about-cloud-sources.md index 4678c3e96e..fbc375c085 100644 --- a/src/connections/sources/about-cloud-sources.md +++ b/src/connections/sources/about-cloud-sources.md @@ -15,8 +15,7 @@ Event Cloud Sources can export their data both into Segment warehouses, and into ### Object Cloud-App Sources -Object Cloud App Sources can export data and import it directly into a Segment warehouse. You *must* have a Segment warehouse enabled before you enable these. From the warehouse, you analyze your data with SQL, or use Engage SQL Traits to build audiences. Some examples of Object Cloud sources are Salesforce (account information), Zendesk (support cases), and Stripe (payments information). - +Object Cloud App Sources can export data and import it directly into a Segment warehouse. You *must* have a Segment warehouse enabled before you enable these. From the warehouse, you can analyze your data with SQL, use [Reverse ETL](/docs/connections/reverse-etl) to extract data, or use Engage SQL Traits to build audiences. Some examples of Object Cloud sources are Salesforce (account information), Zendesk (support cases), and Stripe (payments information). > note "" > In the app, data from website, mobile, and server sources can go to a warehouse **or** to destinations. Object Cloud-App Source data can **only** go to Warehouses. diff --git a/src/segment-app/extensions/dbt.md b/src/segment-app/extensions/dbt.md index acef4c709a..547bcdcfc4 100644 --- a/src/segment-app/extensions/dbt.md +++ b/src/segment-app/extensions/dbt.md @@ -50,8 +50,8 @@ To set up dbt Cloud: 2. Click **Manage dbt Cloud**. 3. Add your dbt Cloud API key or dbt Personal Access Token and an optional custom subdomain, then click **Save**. -> info "Add a custom subdomain" -> By default, dbt sets the subdomain to 'cloud'. To identify your custom subdomain, open your URL and copy the portion before `.getdbt.com`. For example, if your domain was `https://subdomain.getdbt.com/`, your subdomain would be `subdomain`. +> info "Adding a custom subdomain" +> By default, dbt sets the subdomain to cloud. To identify your custom subdomain, open your URL and copy the portion before `.getdbt.com`. For example, if your domain was `https://subdomain.getdbt.com/`, your subdomain would be `subdomain`. ### Model syncs