From ee8a02a1bf14bb1fd31d759a2b643bc5f9bede01 Mon Sep 17 00:00:00 2001 From: Charity Holt <38872070+charholt@users.noreply.github.com> Date: Thu, 31 Oct 2024 14:07:35 -0400 Subject: [PATCH 01/24] Update index.md Update language around historical backfill to include how to ensure the backfill is running. --- src/unify/profiles-sync/profiles-sync-setup/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/unify/profiles-sync/profiles-sync-setup/index.md b/src/unify/profiles-sync/profiles-sync-setup/index.md index 1f7ec69dd1..4095cca23f 100644 --- a/src/unify/profiles-sync/profiles-sync-setup/index.md +++ b/src/unify/profiles-sync/profiles-sync-setup/index.md @@ -117,7 +117,7 @@ If you choose to re-enable a table or property to sync again, only new data gene #### Using historical backfill -Profiles Sync sends profiles to your warehouse on an hourly basis, beginning after you complete setup. You can use backfill, however, to sync historical profiles to your warehouse, as well. +Profiles Sync sends profiles to your warehouse on an hourly basis once setup is complete. Setup is considered complete after the initial automated backfill has finished, which will sync all profile data. To initiate the backfill, the Profiles Sync pipeline requires live data flowing into your workspace. If live data isn’t available, you can send test data to the workspace to start the backfill sooner. You can also use backfill to sync historical profiles to your warehouse. > info "" > You can only use historical backfill for tables that you enable with [Selective Sync](#using-selective-sync) during setup. Segment does not backfill tables that you disable with Selective Sync. From 94983a41058eed7b395f8e3282dd4d914274163d Mon Sep 17 00:00:00 2001 From: wilwong-segment <110120307+wilwong-segment@users.noreply.github.com> Date: Mon, 4 Nov 2024 10:50:33 -0800 Subject: [PATCH 02/24] Update linked-audiences-limits.md --- src/engage/audiences/linked-audiences-limits.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/engage/audiences/linked-audiences-limits.md b/src/engage/audiences/linked-audiences-limits.md index 61d35a2dc0..fa8e777feb 100644 --- a/src/engage/audiences/linked-audiences-limits.md +++ b/src/engage/audiences/linked-audiences-limits.md @@ -36,6 +36,6 @@ Event Size | 32 KB | Segment doesn’t emit messages for profiles whose total re Data Graph depth | 6 | You can't save a Data Graph if you exceed the limit. Preview size | 3K rows | The maximum number of rows you can have to generate a preview. The preview fails if you bring back too many entities. Entity value type ahead cache | Up to 100 unique values | The maximum number of entity values Segment stores in cache. -Entity columns | Up to 200 unique values | The maximum number of entity property columns Segment surfaces in the condition builder. -Run frequency | 15 minutes (this is the fastest time) | You can’t configure more frequency syncs. You can select **Compute Now** to trigger runs, but you’re limited by Profiles Sync for when new data syncs back to the data warehouse. +Entity columns | Up to 1000 unique values | The maximum number of entity property columns Segment surfaces in the condition builder. +Run frequency | 15 minutes (this is the fastest time) | You can’t configure more frequency syncs. You can select **Run Now** to trigger runs, but you’re limited by Profiles Sync for when new data syncs back to the data warehouse. From b845ccac5af2b056375a0523d3b1a8b5e91a83d4 Mon Sep 17 00:00:00 2001 From: Nick Aguilar Date: Wed, 6 Nov 2024 09:52:24 -0800 Subject: [PATCH 03/24] Adds role prerequisite for Facebook Custom Audiences (Actions) --- .../catalog/actions-facebook-custom-audiences/index.md | 1 + 1 file changed, 1 insertion(+) diff --git a/src/connections/destinations/catalog/actions-facebook-custom-audiences/index.md b/src/connections/destinations/catalog/actions-facebook-custom-audiences/index.md index 85f56197ae..b6102ac6ef 100644 --- a/src/connections/destinations/catalog/actions-facebook-custom-audiences/index.md +++ b/src/connections/destinations/catalog/actions-facebook-custom-audiences/index.md @@ -26,6 +26,7 @@ This destination sends audiences, or lists of users, from your data warehouse to ### Prerequisites - A Reverse ETL source already set up. If you don't yet have a Reverse ETL source, follow the instructions in Segment's [Reverse ETL documentation](/docs/connections/reverse-etl/#getting-started). Segment recommends setting an [External ID](#sync-audience) as the primary key for your Reverse ETL model, as you'll need an External ID to remove users from your custom audiences. - A Facebook account with [ads_management](https://developers.facebook.com/docs/permissions#ads_management){:target="_blank”} permissions for the target Facebook Ad Account(s). The Facebook Ad Account(s) must also be associated with a [Facebook Business Account](https://www.facebook.com/business/help/407323696966570?id=649869995454285){:target="_blank”}. +- Ensure that the user connecting to the destination via OAuth has at least an "Advertiser" or "Admin" role on the ad account. To manage permissions and roles for an ad account reference this [Facebook doc](https://www.facebook.com/business/help/186007118118684?id=829106167281625). ### Connect to Facebook Custom Audiences 1. From your Segment app, navigate to **Catalog > Destinations** and search for "Facebook Custom Audiences (Actions)". From f1378e49a39125037cddfa7119c2ce1dd92796fc Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 7 Nov 2024 12:20:06 -0500 Subject: [PATCH 04/24] first pass --- src/unify/data-graph/index.md | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/src/unify/data-graph/index.md b/src/unify/data-graph/index.md index f58c23ab3d..5fb4c4315d 100644 --- a/src/unify/data-graph/index.md +++ b/src/unify/data-graph/index.md @@ -414,4 +414,17 @@ Upon editing and saving changes to your Data Graph, a modal will pop up to warn ### Detect warehouse breaking changes -Segment has a service that regularly scans and monitors the Data Graph for changes that occur in your warehouse that may break components of the Data Graph, such as when the table being referenced by the Data Graph gets deleted from your warehouse or when the primary key column no longer exists. An alert banner will be displayed on the Data Graph landing page. The banner will be removed once the issues are resolved in your warehouse and/or the Data Graph. You will also have the option to trigger a manual sync of your warehouse schema. +Segment has a service that regularly scans and monitors the Data Graph for changes that occur in your warehouse that may break components of the Data Graph, like when the table being referenced by the Data Graph gets deleted from your warehouse or when the primary key column no longer exists. An alert banner will be displayed on the Data Graph landing page. The banner will be removed once the issues are resolved in your warehouse and/or the Data Graph. You will also have the option to trigger a manual sync of your warehouse schema. + +### Alerts for warehouse breaking changes + +Configure alerts for breaking changes to receive notifications over Slack, email, or in-app notification whenever Segment detects a breaking change in your warehouse. + +To configure alerts for breaking changes: +1. Open your workspace and navigate to **Settings > User Preferences > Activity Notifications**. +2. Select **Data Graph**. +3. Select one of the following notification methods: + - **Email**: Select this to receive notifications at either the email address associated with your account or another email address that you enter into this field. + - **Slack**: Select this and enter a Slack webhook URL and channel name to send alerts to a channel in your Slack workspace. + - **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. +4. Click **Save**. From 10b2a4e0c638d2e801182b1017febf8d1df6c7e6 Mon Sep 17 00:00:00 2001 From: stayseesong <83784848+stayseesong@users.noreply.github.com> Date: Thu, 7 Nov 2024 09:41:45 -0800 Subject: [PATCH 05/24] Update src/connections/destinations/catalog/actions-facebook-custom-audiences/index.md --- .../catalog/actions-facebook-custom-audiences/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/actions-facebook-custom-audiences/index.md b/src/connections/destinations/catalog/actions-facebook-custom-audiences/index.md index b6102ac6ef..5fbf9c529f 100644 --- a/src/connections/destinations/catalog/actions-facebook-custom-audiences/index.md +++ b/src/connections/destinations/catalog/actions-facebook-custom-audiences/index.md @@ -26,7 +26,7 @@ This destination sends audiences, or lists of users, from your data warehouse to ### Prerequisites - A Reverse ETL source already set up. If you don't yet have a Reverse ETL source, follow the instructions in Segment's [Reverse ETL documentation](/docs/connections/reverse-etl/#getting-started). Segment recommends setting an [External ID](#sync-audience) as the primary key for your Reverse ETL model, as you'll need an External ID to remove users from your custom audiences. - A Facebook account with [ads_management](https://developers.facebook.com/docs/permissions#ads_management){:target="_blank”} permissions for the target Facebook Ad Account(s). The Facebook Ad Account(s) must also be associated with a [Facebook Business Account](https://www.facebook.com/business/help/407323696966570?id=649869995454285){:target="_blank”}. -- Ensure that the user connecting to the destination via OAuth has at least an "Advertiser" or "Admin" role on the ad account. To manage permissions and roles for an ad account reference this [Facebook doc](https://www.facebook.com/business/help/186007118118684?id=829106167281625). +- Ensure that the user connecting to the destination using OAuth has at least an *Advertiser* or *Admin* role on the ad account. To manage permissions and roles for an ad account, reference [Facebook's documentation](https://www.facebook.com/business/help/186007118118684?id=829106167281625){:target="_blank"}. ### Connect to Facebook Custom Audiences 1. From your Segment app, navigate to **Catalog > Destinations** and search for "Facebook Custom Audiences (Actions)". From 8b35fb3b308e2e044d3abf84f3548acbc73c2f7a Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 7 Nov 2024 12:42:53 -0500 Subject: [PATCH 06/24] [netlify-build] --- src/unify/data-graph/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/unify/data-graph/index.md b/src/unify/data-graph/index.md index 5fb4c4315d..8cf518a981 100644 --- a/src/unify/data-graph/index.md +++ b/src/unify/data-graph/index.md @@ -416,7 +416,7 @@ Upon editing and saving changes to your Data Graph, a modal will pop up to warn Segment has a service that regularly scans and monitors the Data Graph for changes that occur in your warehouse that may break components of the Data Graph, like when the table being referenced by the Data Graph gets deleted from your warehouse or when the primary key column no longer exists. An alert banner will be displayed on the Data Graph landing page. The banner will be removed once the issues are resolved in your warehouse and/or the Data Graph. You will also have the option to trigger a manual sync of your warehouse schema. -### Alerts for warehouse breaking changes +### Receive alerts for warehouse breaking changes Configure alerts for breaking changes to receive notifications over Slack, email, or in-app notification whenever Segment detects a breaking change in your warehouse. From f5bbcfc0a1ed1be18d675520ee281ef559b2b1fc Mon Sep 17 00:00:00 2001 From: pwseg Date: Thu, 7 Nov 2024 11:57:41 -0600 Subject: [PATCH 07/24] Add connection types section --- src/segment-app/extensions/git.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/src/segment-app/extensions/git.md b/src/segment-app/extensions/git.md index 7a2f920a7f..eae8bd83d1 100644 --- a/src/segment-app/extensions/git.md +++ b/src/segment-app/extensions/git.md @@ -76,3 +76,21 @@ To manage Segment resources using Git and Terraform, follow these steps: For more information on using Terraform, visit [Terraform's documentation](https://developer.hashicorp.com/terraform/docs){:target="_blank"}. + +## Git Connections + +Git Connections enable Segment to sync data with your preferred Git repository through supported connection types. Segment supports several connection options connecting, including SSH and token-based authentication. + +> info "" +> Git Sync and the dbt integration operate independently. You don’t need Git Sync set up to use dbt, and dbt Cloud can trigger its own syncs without relying on Git Sync. + +### Supported connection types + +Segment supports the following credential types for setting up a Git Connection: + +- **SSH**: Compatible with GitHub, GitLab, and Bitbucket, SSH provides a secure method for connecting to your repository. +- **Git Token**: Git tokens are also supported across GitHub, GitLab, and Bitbucket, enabling token-based authentication for added flexibility. +- **GitHub App**: For GitHub users, GitHub App integrations offer enhanced security and functionality. This method is exclusive to GitHub and supports additional features, such as [CI checks](). + + + From 63965a4170646ce85420e539b38e88a238d43111 Mon Sep 17 00:00:00 2001 From: pwseg Date: Thu, 7 Nov 2024 12:03:09 -0600 Subject: [PATCH 08/24] add reusing git connections section --- src/segment-app/extensions/git.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/src/segment-app/extensions/git.md b/src/segment-app/extensions/git.md index eae8bd83d1..10d3c3c63e 100644 --- a/src/segment-app/extensions/git.md +++ b/src/segment-app/extensions/git.md @@ -92,5 +92,10 @@ Segment supports the following credential types for setting up a Git Connection: - **Git Token**: Git tokens are also supported across GitHub, GitLab, and Bitbucket, enabling token-based authentication for added flexibility. - **GitHub App**: For GitHub users, GitHub App integrations offer enhanced security and functionality. This method is exclusive to GitHub and supports additional features, such as [CI checks](). +### Reusing Git Connections + +Segment lets you set up multiple Git Connections, allowing you to reuse credentials across both dbt and Git Sync. You can either use the same credential for multiple configurations or create separate Git Connections for each product and environment as needed. + +If you plan to reuse a Git token across both dbt and Git Sync, ensure it has the necessary read and write permissions for both integrations. From 4e0e5a0b761619b8f16ac8e55357fdd41adddeb6 Mon Sep 17 00:00:00 2001 From: pwseg Date: Thu, 7 Nov 2024 12:04:49 -0600 Subject: [PATCH 09/24] Add Git Connections section to dbt page --- src/segment-app/extensions/dbt.md | 21 +++++++++++++++++++++ src/segment-app/extensions/git.md | 3 +-- 2 files changed, 22 insertions(+), 2 deletions(-) diff --git a/src/segment-app/extensions/dbt.md b/src/segment-app/extensions/dbt.md index 547bcdcfc4..a39aee6efb 100644 --- a/src/segment-app/extensions/dbt.md +++ b/src/segment-app/extensions/dbt.md @@ -69,3 +69,24 @@ After you've successfully set up dbt with a warehouse and connected to your Git 6. Enter your **Model Name**, then click **Create Model**. To change a connected model, ensure that you've removed it from all active Reverse ETL syncs. + +## Git Connections + +Git Connections enable Segment to sync data with your preferred Git repository through supported connection types. Segment supports several connection options connecting, including SSH and token-based authentication. + +> info "" +> Git Sync and the dbt integration operate independently. You don’t need Git Sync set up to use dbt, and dbt Cloud can trigger its own syncs without relying on Git Sync. + +### Supported connection types + +Segment supports the following credential types for setting up a Git Connection: + +- **SSH**: Compatible with GitHub, GitLab, and Bitbucket, SSH provides a secure method for connecting to your repository. +- **Git Token**: Git tokens are also supported across GitHub, GitLab, and Bitbucket, enabling token-based authentication for added flexibility. +- **GitHub App**: For GitHub users, GitHub App integrations offer enhanced security and functionality. This method is exclusive to GitHub and supports additional features, like [CI checks](). + +### Reusing Git Connections + +Segment lets you set up multiple Git Connections, allowing you to reuse credentials across both dbt and Git Sync. You can either use the same credential for multiple configurations or create separate Git Connections for each product and environment as needed. + +If you plan to reuse a Git token across both dbt and Git Sync, ensure it has the necessary read and write permissions for both integrations. \ No newline at end of file diff --git a/src/segment-app/extensions/git.md b/src/segment-app/extensions/git.md index 10d3c3c63e..93c2d212c5 100644 --- a/src/segment-app/extensions/git.md +++ b/src/segment-app/extensions/git.md @@ -90,7 +90,7 @@ Segment supports the following credential types for setting up a Git Connection: - **SSH**: Compatible with GitHub, GitLab, and Bitbucket, SSH provides a secure method for connecting to your repository. - **Git Token**: Git tokens are also supported across GitHub, GitLab, and Bitbucket, enabling token-based authentication for added flexibility. -- **GitHub App**: For GitHub users, GitHub App integrations offer enhanced security and functionality. This method is exclusive to GitHub and supports additional features, such as [CI checks](). +- **GitHub App**: For GitHub users, GitHub App integrations offer enhanced security and functionality. This method is exclusive to GitHub and supports additional features, like CI checks. ### Reusing Git Connections @@ -98,4 +98,3 @@ Segment lets you set up multiple Git Connections, allowing you to reuse credenti If you plan to reuse a Git token across both dbt and Git Sync, ensure it has the necessary read and write permissions for both integrations. - From b7836ed4a91d0d6b4dd68859ee90ff2a82cab453 Mon Sep 17 00:00:00 2001 From: pwseg Date: Thu, 7 Nov 2024 12:08:58 -0600 Subject: [PATCH 10/24] CI checks info --- src/segment-app/extensions/dbt.md | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/src/segment-app/extensions/dbt.md b/src/segment-app/extensions/dbt.md index a39aee6efb..c82c265f31 100644 --- a/src/segment-app/extensions/dbt.md +++ b/src/segment-app/extensions/dbt.md @@ -89,4 +89,16 @@ Segment supports the following credential types for setting up a Git Connection: Segment lets you set up multiple Git Connections, allowing you to reuse credentials across both dbt and Git Sync. You can either use the same credential for multiple configurations or create separate Git Connections for each product and environment as needed. -If you plan to reuse a Git token across both dbt and Git Sync, ensure it has the necessary read and write permissions for both integrations. \ No newline at end of file +If you plan to reuse a Git token across both dbt and Git Sync, ensure it has the necessary read and write permissions for both integrations. + +## Setting Up CI checks + +> info "CI Check availability" +> CI Checks are available only with the GitHub App connection. + +CI checks in Segment help prevent breaking changes to active dbt models. Avoid changing dbt models currently in use with an active Reverse ETL sync, since changes could disrupt existing mappings and active syncs. + +When CI checks are enabled, Segment monitors model changes in your Git repository. If a model already linked to an active Reverse ETL sync gets modified, Segment automatically rejects the change to maintain data integrity. + +To enable CI Checks, authorize a GitHub App credential for your Git connection. Once connected, you can enable CI Checks in the dbt model sync configuration section. + From 61f05e26b11aeb4823cd7f01125e938325db913e Mon Sep 17 00:00:00 2001 From: pwseg Date: Thu, 7 Nov 2024 12:12:10 -0600 Subject: [PATCH 11/24] troubleshooting sections --- src/segment-app/extensions/dbt.md | 2 ++ src/segment-app/extensions/git.md | 1 + 2 files changed, 3 insertions(+) diff --git a/src/segment-app/extensions/dbt.md b/src/segment-app/extensions/dbt.md index c82c265f31..4d1d2bc109 100644 --- a/src/segment-app/extensions/dbt.md +++ b/src/segment-app/extensions/dbt.md @@ -102,3 +102,5 @@ When CI checks are enabled, Segment monitors model changes in your Git repositor To enable CI Checks, authorize a GitHub App credential for your Git connection. Once connected, you can enable CI Checks in the dbt model sync configuration section. +## Troubleshooting dbt Extensions + diff --git a/src/segment-app/extensions/git.md b/src/segment-app/extensions/git.md index 93c2d212c5..e36ea3fd7c 100644 --- a/src/segment-app/extensions/git.md +++ b/src/segment-app/extensions/git.md @@ -98,3 +98,4 @@ Segment lets you set up multiple Git Connections, allowing you to reuse credenti If you plan to reuse a Git token across both dbt and Git Sync, ensure it has the necessary read and write permissions for both integrations. +## Troubleshooting Git Sync From 5c8bd727579525182bca44792f1421332fe68e74 Mon Sep 17 00:00:00 2001 From: pwseg Date: Thu, 7 Nov 2024 12:19:46 -0600 Subject: [PATCH 12/24] add troubleshooting section --- src/segment-app/extensions/dbt.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/src/segment-app/extensions/dbt.md b/src/segment-app/extensions/dbt.md index 4d1d2bc109..712191e60b 100644 --- a/src/segment-app/extensions/dbt.md +++ b/src/segment-app/extensions/dbt.md @@ -83,7 +83,7 @@ Segment supports the following credential types for setting up a Git Connection: - **SSH**: Compatible with GitHub, GitLab, and Bitbucket, SSH provides a secure method for connecting to your repository. - **Git Token**: Git tokens are also supported across GitHub, GitLab, and Bitbucket, enabling token-based authentication for added flexibility. -- **GitHub App**: For GitHub users, GitHub App integrations offer enhanced security and functionality. This method is exclusive to GitHub and supports additional features, like [CI checks](). +- **GitHub App**: For GitHub users, GitHub App integrations offer enhanced security and functionality. This method is exclusive to GitHub and supports additional features, like [CI checks](#setting-up-ci-checks). ### Reusing Git Connections @@ -104,3 +104,9 @@ To enable CI Checks, authorize a GitHub App credential for your Git connection. ## Troubleshooting dbt Extensions +The following table lists common dbt Extension errors, as well as their solutions: + +| Error | Error message | Solution | +| ----------- | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Failed sync | `Sync Failed: Incorrect dbt Project File Path: dbt project file not found` | Verify that the path to your `dbt_project.yml` file is relative to the repository root, excluding the root branch.
For example, use `project/dbt_project.yml` instead of `main/project/dbt_project.yml`. | +| Failed sync | `Sync Failed: remote: Write access to repository not granted` | Verify that the account associated with the token has a write role in the repository settings. Fine-grained tokens may require specific roles, depending on your Git provider. | \ No newline at end of file From 5bd65ed42269398163947c4124cc6e69cbac4313 Mon Sep 17 00:00:00 2001 From: pwseg Date: Thu, 7 Nov 2024 12:24:35 -0600 Subject: [PATCH 13/24] git troubleshooting --- src/segment-app/extensions/git.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/src/segment-app/extensions/git.md b/src/segment-app/extensions/git.md index e36ea3fd7c..b6b7dee43e 100644 --- a/src/segment-app/extensions/git.md +++ b/src/segment-app/extensions/git.md @@ -99,3 +99,11 @@ Segment lets you set up multiple Git Connections, allowing you to reuse credenti If you plan to reuse a Git token across both dbt and Git Sync, ensure it has the necessary read and write permissions for both integrations. ## Troubleshooting Git Sync + +When setting up Git Sync, you may run into an access error when setting up Git Sync with the following message: `“Unable to create Git Sync due to Git connection issues. Please check your configuration and try again`. + +This error can occur if there are issues with your Git connection settings or permissions. To resolve the error, verify that: + +- Your credentials have write access to the Git repository, as Segment requires this to sync changes. +- Your repository is hosted by GitHub, GitLab, or Bitbucket (Segment doesn't support self-hosted repositories). +- Branch protections are disabled on the repository. From ca0bdc3cb3b561ad0d8a84df211b8c582c476357 Mon Sep 17 00:00:00 2001 From: pwseg Date: Thu, 7 Nov 2024 12:28:31 -0600 Subject: [PATCH 14/24] final touches [netlify-build] --- src/segment-app/extensions/git.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/src/segment-app/extensions/git.md b/src/segment-app/extensions/git.md index b6b7dee43e..bb3009dabf 100644 --- a/src/segment-app/extensions/git.md +++ b/src/segment-app/extensions/git.md @@ -23,7 +23,7 @@ The Git sync extension syncs the following resources from Segment to your Git re - [Sources](/docs/connections/sources/) and [Destinations](/docs/connections/destinations/) - [Warehouses](/docs/connections/storage/warehouses/) -- [Destination Filters and Mappings](/docs/connections/destinations/destination-filters/) +- [Destination Filters and Mappings](/docs/connections/destinations/destination-filters/) for Connections - [Tracking Plans](/docs/protocols/tracking-plan/create/) - [Functions](/docs/connections/functions/) - [Transformations](/docs/protocols/transform/) @@ -31,6 +31,13 @@ The Git sync extension syncs the following resources from Segment to your Git re - [Users](/docs/segment-app/iam/concepts/#team-members) and [User groups](/docs/segment-app/iam/concepts/#user-groups) - [Labels](/docs/segment-app/iam/labels/#where-can-i-create-labels) +The Git sync extension doesn't support the following resources: + +- [Spaces](/docs/segment-app/workspace-home/) +- [Audiences](/docs/engage/audiences/) and [Journeys](/docs/engage/journeys/) +- [Data Graph](/docs/unify/data-graph/) +- Mappings for [Linked Audiences](/docs/engage/audiences/linked-audiences/) + Reach out to [Segment support](https://app.segment.com/workspaces?contact=1){:target="blank"} to request support for additional Git Sync resources. After you set up the Git sync extension for the first time, Segment performs an initial sync that sends the current state of your Segment workspace to the Git repository you connected. Segment automatically tracks all following workspace updates. @@ -49,7 +56,7 @@ Using HCL makes it easier to document Segment's data model, especially for users Segment supports one-way synchronization from Segment to Git, but you can set up two-way synchronization using the Segment Terraform provider. -Terraform offers an open-source way to manage Segment resources through a Git repository as an alternative to a fully managed two-way sync. However, this method requires third-party tools like [Atlantis](https://www.runatlantis.io/){:target="_blank"} for CI integration, which Segment doesn’t officially support. +Terraform offers an open-source way to manage Segment resources through a Git repository as an alternative to a fully managed two-way sync. This method requires third-party tools like [Atlantis](https://www.runatlantis.io/){:target="_blank"} for CI integration. To manage Segment resources using Git and Terraform, follow these steps: From 06fa7ffe8bf2232ef5bbf2b5aac0a4f584620213 Mon Sep 17 00:00:00 2001 From: pwseg Date: Thu, 7 Nov 2024 12:32:08 -0600 Subject: [PATCH 15/24] some more fixes --- src/segment-app/extensions/dbt.md | 2 +- src/segment-app/extensions/git.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/segment-app/extensions/dbt.md b/src/segment-app/extensions/dbt.md index 712191e60b..66edce2303 100644 --- a/src/segment-app/extensions/dbt.md +++ b/src/segment-app/extensions/dbt.md @@ -72,7 +72,7 @@ To change a connected model, ensure that you've removed it from all active Rever ## Git Connections -Git Connections enable Segment to sync data with your preferred Git repository through supported connection types. Segment supports several connection options connecting, including SSH and token-based authentication. +Git Connections enable Segment to sync data with your preferred Git repository through supported like SSH and token-based authentication. > info "" > Git Sync and the dbt integration operate independently. You don’t need Git Sync set up to use dbt, and dbt Cloud can trigger its own syncs without relying on Git Sync. diff --git a/src/segment-app/extensions/git.md b/src/segment-app/extensions/git.md index bb3009dabf..c522c303b6 100644 --- a/src/segment-app/extensions/git.md +++ b/src/segment-app/extensions/git.md @@ -86,7 +86,7 @@ For more information on using Terraform, visit [Terraform's documentation](https ## Git Connections -Git Connections enable Segment to sync data with your preferred Git repository through supported connection types. Segment supports several connection options connecting, including SSH and token-based authentication. +Git Connections enable Segment to sync data with your preferred Git repository through supported like SSH and token-based authentication. > info "" > Git Sync and the dbt integration operate independently. You don’t need Git Sync set up to use dbt, and dbt Cloud can trigger its own syncs without relying on Git Sync. @@ -96,7 +96,7 @@ Git Connections enable Segment to sync data with your preferred Git repository t Segment supports the following credential types for setting up a Git Connection: - **SSH**: Compatible with GitHub, GitLab, and Bitbucket, SSH provides a secure method for connecting to your repository. -- **Git Token**: Git tokens are also supported across GitHub, GitLab, and Bitbucket, enabling token-based authentication for added flexibility. +- **Git Token**: Git tokens are also supported across GitHub, GitLab, and Bitbucket, enabling token-based authentication.. - **GitHub App**: For GitHub users, GitHub App integrations offer enhanced security and functionality. This method is exclusive to GitHub and supports additional features, like CI checks. ### Reusing Git Connections From 7840eae47d4d813efc5873495ed26e1ef25e43db Mon Sep 17 00:00:00 2001 From: pwseg Date: Thu, 7 Nov 2024 12:33:04 -0600 Subject: [PATCH 16/24] even more fixes --- src/segment-app/extensions/git.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/segment-app/extensions/git.md b/src/segment-app/extensions/git.md index c522c303b6..9be4925088 100644 --- a/src/segment-app/extensions/git.md +++ b/src/segment-app/extensions/git.md @@ -107,7 +107,7 @@ If you plan to reuse a Git token across both dbt and Git Sync, ensure it has the ## Troubleshooting Git Sync -When setting up Git Sync, you may run into an access error when setting up Git Sync with the following message: `“Unable to create Git Sync due to Git connection issues. Please check your configuration and try again`. +When setting up Git Sync, you may run into an access error with the following message: `“Unable to create Git Sync due to Git connection issues. Please check your configuration and try again`. This error can occur if there are issues with your Git connection settings or permissions. To resolve the error, verify that: From 8acc4c14a1ad2a6d1970e894d07cd7de17a2be3a Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Thu, 7 Nov 2024 12:42:49 -0600 Subject: [PATCH 17/24] Update src/segment-app/extensions/git.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- src/segment-app/extensions/git.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/segment-app/extensions/git.md b/src/segment-app/extensions/git.md index 9be4925088..da1aa02735 100644 --- a/src/segment-app/extensions/git.md +++ b/src/segment-app/extensions/git.md @@ -89,7 +89,7 @@ For more information on using Terraform, visit [Terraform's documentation](https Git Connections enable Segment to sync data with your preferred Git repository through supported like SSH and token-based authentication. > info "" -> Git Sync and the dbt integration operate independently. You don’t need Git Sync set up to use dbt, and dbt Cloud can trigger its own syncs without relying on Git Sync. +> Git Sync and the dbt integration operate independently. You don’t need to set up Git Sync to use dbt, and dbt Cloud can trigger its own syncs without relying on Git Sync. ### Supported connection types From 10328cd2cda5ec2c159f9e7be60fd66f1a099270 Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Thu, 7 Nov 2024 12:42:57 -0600 Subject: [PATCH 18/24] Update src/segment-app/extensions/dbt.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- src/segment-app/extensions/dbt.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/segment-app/extensions/dbt.md b/src/segment-app/extensions/dbt.md index 66edce2303..335ab21d58 100644 --- a/src/segment-app/extensions/dbt.md +++ b/src/segment-app/extensions/dbt.md @@ -94,7 +94,7 @@ If you plan to reuse a Git token across both dbt and Git Sync, ensure it has the ## Setting Up CI checks > info "CI Check availability" -> CI Checks are available only with the GitHub App connection. +> CI checks are available only with the GitHub App connection. CI checks in Segment help prevent breaking changes to active dbt models. Avoid changing dbt models currently in use with an active Reverse ETL sync, since changes could disrupt existing mappings and active syncs. From 5196788ee755e59eede9bf875328e946bff76d98 Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Thu, 7 Nov 2024 12:43:08 -0600 Subject: [PATCH 19/24] Update src/segment-app/extensions/dbt.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- src/segment-app/extensions/dbt.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/segment-app/extensions/dbt.md b/src/segment-app/extensions/dbt.md index 335ab21d58..d2622e6779 100644 --- a/src/segment-app/extensions/dbt.md +++ b/src/segment-app/extensions/dbt.md @@ -93,7 +93,7 @@ If you plan to reuse a Git token across both dbt and Git Sync, ensure it has the ## Setting Up CI checks -> info "CI Check availability" +> info "CI check availability" > CI checks are available only with the GitHub App connection. CI checks in Segment help prevent breaking changes to active dbt models. Avoid changing dbt models currently in use with an active Reverse ETL sync, since changes could disrupt existing mappings and active syncs. From d64b6e8899d38b1f2e5e34a105c40860ecc97143 Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Thu, 7 Nov 2024 12:43:24 -0600 Subject: [PATCH 20/24] Update src/segment-app/extensions/dbt.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- src/segment-app/extensions/dbt.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/segment-app/extensions/dbt.md b/src/segment-app/extensions/dbt.md index d2622e6779..6c885657aa 100644 --- a/src/segment-app/extensions/dbt.md +++ b/src/segment-app/extensions/dbt.md @@ -82,7 +82,7 @@ Git Connections enable Segment to sync data with your preferred Git repository t Segment supports the following credential types for setting up a Git Connection: - **SSH**: Compatible with GitHub, GitLab, and Bitbucket, SSH provides a secure method for connecting to your repository. -- **Git Token**: Git tokens are also supported across GitHub, GitLab, and Bitbucket, enabling token-based authentication for added flexibility. +- **Git token**: Git tokens are supported across GitHub, GitLab, and Bitbucket, enabling token-based authentication for added flexibility. - **GitHub App**: For GitHub users, GitHub App integrations offer enhanced security and functionality. This method is exclusive to GitHub and supports additional features, like [CI checks](#setting-up-ci-checks). ### Reusing Git Connections From 64c9119556a028ff9639d08cc5cb748a92720bb5 Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Thu, 7 Nov 2024 12:45:10 -0600 Subject: [PATCH 21/24] Update src/segment-app/extensions/dbt.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- src/segment-app/extensions/dbt.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/segment-app/extensions/dbt.md b/src/segment-app/extensions/dbt.md index 6c885657aa..2b811103de 100644 --- a/src/segment-app/extensions/dbt.md +++ b/src/segment-app/extensions/dbt.md @@ -75,7 +75,7 @@ To change a connected model, ensure that you've removed it from all active Rever Git Connections enable Segment to sync data with your preferred Git repository through supported like SSH and token-based authentication. > info "" -> Git Sync and the dbt integration operate independently. You don’t need Git Sync set up to use dbt, and dbt Cloud can trigger its own syncs without relying on Git Sync. +> Git Sync and the dbt integration operate independently. You don’t need to set up Git Sync to use dbt, and dbt Cloud can trigger its own syncs without relying on Git Sync. ### Supported connection types From e01c6dbcd008eaf4986e9c2625fd12cc861b0ac6 Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Thu, 7 Nov 2024 12:49:31 -0600 Subject: [PATCH 22/24] token not Token smh --- src/segment-app/extensions/git.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/segment-app/extensions/git.md b/src/segment-app/extensions/git.md index da1aa02735..04b87ed6c9 100644 --- a/src/segment-app/extensions/git.md +++ b/src/segment-app/extensions/git.md @@ -96,7 +96,7 @@ Git Connections enable Segment to sync data with your preferred Git repository t Segment supports the following credential types for setting up a Git Connection: - **SSH**: Compatible with GitHub, GitLab, and Bitbucket, SSH provides a secure method for connecting to your repository. -- **Git Token**: Git tokens are also supported across GitHub, GitLab, and Bitbucket, enabling token-based authentication.. +- **Git token**: Git tokens are also supported across GitHub, GitLab, and Bitbucket, enabling token-based authentication.. - **GitHub App**: For GitHub users, GitHub App integrations offer enhanced security and functionality. This method is exclusive to GitHub and supports additional features, like CI checks. ### Reusing Git Connections From 0e4279ec4783fd611a32773b664a7eb4aefbe8b4 Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Thu, 7 Nov 2024 12:54:20 -0600 Subject: [PATCH 23/24] minor rewording --- src/unify/profiles-sync/profiles-sync-setup/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/unify/profiles-sync/profiles-sync-setup/index.md b/src/unify/profiles-sync/profiles-sync-setup/index.md index 4095cca23f..a825af5bd6 100644 --- a/src/unify/profiles-sync/profiles-sync-setup/index.md +++ b/src/unify/profiles-sync/profiles-sync-setup/index.md @@ -117,7 +117,7 @@ If you choose to re-enable a table or property to sync again, only new data gene #### Using historical backfill -Profiles Sync sends profiles to your warehouse on an hourly basis once setup is complete. Setup is considered complete after the initial automated backfill has finished, which will sync all profile data. To initiate the backfill, the Profiles Sync pipeline requires live data flowing into your workspace. If live data isn’t available, you can send test data to the workspace to start the backfill sooner. You can also use backfill to sync historical profiles to your warehouse. +Profiles Sync sends profiles to your warehouse hourly once setup completes. Setup is complete after an initial automated backfill syncs all profile data. To initiate the backfill, the Profiles Sync requires live data flowing into your workspace. If live data isn’t available, you can send test data to trigger the backfill sooner. Backfill can also sync historical profiles to your warehouse. > info "" > You can only use historical backfill for tables that you enable with [Selective Sync](#using-selective-sync) during setup. Segment does not backfill tables that you disable with Selective Sync. From e1555844276dcb658f9be3009500c81a834cad5e Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 7 Nov 2024 14:04:26 -0500 Subject: [PATCH 24/24] catalog? --- src/_data/catalog/destination_categories.yml | 2 +- src/_data/catalog/destinations.yml | 4 ++-- src/_data/catalog/source_categories.yml | 2 +- src/_data/catalog/sources.yml | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/src/_data/catalog/destination_categories.yml b/src/_data/catalog/destination_categories.yml index 3103ad53f9..3b6931cbdc 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-11-05 +# destination categories last updated 2024-11-07 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 874fe520e8..0993a8143c 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-11-05 +# destination data last updated 2024-11-07 items: - id: 637e8d185e2dec264895ea89 display_name: 1Flow @@ -18340,7 +18340,7 @@ items: slug: actions-attio hidden: false endpoints: - - US + - EU regions: - us-west-2 - eu-west-1 diff --git a/src/_data/catalog/source_categories.yml b/src/_data/catalog/source_categories.yml index 89bb865849..c9831057c6 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-11-05 +# source categories last updated 2024-11-07 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 b369b05898..fde7054b35 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-11-05 +# sources last updated 2024-11-07 items: - id: 8HWbgPTt3k display_name: .NET