From 1aa4517306c594c27e9359ab3fa05c8dc95a1fad Mon Sep 17 00:00:00 2001 From: dineshraj-arunmozhi <87521197+dineshraj-arunmozhi@users.noreply.github.com> Date: Tue, 24 Sep 2024 18:15:41 +0100 Subject: [PATCH 01/56] Update setup.md correction of the link pointing to a old documentation. --- src/connections/reverse-etl/setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/reverse-etl/setup.md b/src/connections/reverse-etl/setup.md index 4272485914..ba795eb770 100644 --- a/src/connections/reverse-etl/setup.md +++ b/src/connections/reverse-etl/setup.md @@ -87,7 +87,7 @@ To create a mapping: * Added or updated records * Deleted records 7. In the **Map fields** section, define how to map the record columns from your model to your destination. Map the fields that come from your source to fields that the destination expects to find. Fields on the destination side depend on the type of Action selected. - * If you’re setting up a Destination Action, some mapping fields might require data to be in the form of an object or array. See the [supported objects and arrays for mapping](/docs/connections/reverse-etl/manage-retl/#supported-object-and-arrays) for more information. + * If you’re setting up a Destination Action, some mapping fields might require data to be in the form of an object or array. See the [supported objects and arrays for mapping](docs/connections/reverse-etl/setup/#supported-object-and-arrays) for more information. * _(Optional)_ Use the [Suggested Mappings](#suggested-mappings) feature to identify and match near-matching field names to streamline the field mapping process. 8. In the **Send test record section**, select a test record to preview the fields that you mapped to your destination. When you've verified that the records appear as expected, click **Next**. 9. Enter a name for your mapping. The name initially defaults to the Action's name, for example, `Track Event`, but you can make changes to this default name. From e9ead23480dc2c1389b667af9376127217707207 Mon Sep 17 00:00:00 2001 From: Gil Omer Date: Wed, 9 Oct 2024 10:43:20 -0400 Subject: [PATCH 02/56] update Reverse-ETL bigQuery docs --- .../bigquery-setup.md | 26 ++++++++++--------- 1 file changed, 14 insertions(+), 12 deletions(-) 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 03b876dba3..fb132c12f1 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 @@ -4,7 +4,7 @@ redirect_from: - '/reverse-etl/bigquery-setup/' --- -Set up BigQuery as your Reverse ETL source. +## Create service account > warning "" > You need to be an account admin to set up the Segment BigQuery connector as well as write permissions for the `__segment_reverse_etl` dataset. @@ -22,16 +22,6 @@ To set up the Segment BigQuery connector: 10. When your service account pulls up, click the 3 dots under **Actions** and select **Manage keys**. 11. Click **Add Key > Create new key**. 12. In the pop-up window, select **JSON** for the key type and click **Create**. The file will download. -13. Copy all the content within the file you just created and downloaded. -14. Navigate to the Segment UI and paste all the credentials you copied from step 13 into the **Enter your credentials** section. -19. Enter your **Data Location**. -20. Click **Test Connection** to test to see if the connection works. If the connection fails, make sure you have the right permissions and credentials and try again. -6. Click **Add source** if the test connection is successful. - -After you've added BigQuery as a source, you can [add a model](/docs/connections/reverse-etl/setup/#step-2-add-a-model). - -> 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. ## Constructing your own role or policy When you construct your own role or policy, Segment needs the following permissions: @@ -52,4 +42,16 @@ Permission | Details The `bigquery.datasets.*` permissions can be scoped only to the `__segment_reverse_etl` dataset. -After you've successfully added your BigQuery source, [add a model](/docs/connections/reverse-etl/setup/#step-2-add-a-model) and follow the rest of the steps in the Reverse ETL setup guide. \ No newline at end of file +After you've successfully added your BigQuery source, [add a model](/docs/connections/reverse-etl/setup/#step-2-add-a-model) and follow the rest of the steps in the Reverse ETL setup guide. + +## Set up BigQuery as your Reverse ETL source +1. Copy all the content within the **JSON** file created and downloaded in previous section. +2. Navigate to the Segment UI and paste all the credentials you copied from previous step into the **Enter your credentials** section. +3. Enter your **Data Location**. +4. Click **Test Connection** to test to see if the connection works. If the connection fails, make sure you have the right permissions and credentials and try again. +5. Click **Add source** if the test connection is successful. + +After you've added BigQuery as a source, you can [add a model](/docs/connections/reverse-etl/setup/#step-2-add-a-model). + +> 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. From adb2ed41e3869d9c08d334717c669517dd95de86 Mon Sep 17 00:00:00 2001 From: Gil Omer Date: Wed, 9 Oct 2024 15:24:26 -0400 Subject: [PATCH 03/56] change the order --- .../bigquery-setup.md | 41 +++++++++---------- 1 file changed, 19 insertions(+), 22 deletions(-) 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 fb132c12f1..674a933bd9 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,6 +3,24 @@ title: BigQuery Reverse ETL Setup redirect_from: - '/reverse-etl/bigquery-setup/' --- +## Constructing your own role or policy +When you construct your own role or policy, Segment needs the following permissions: + +Permission | Details +---------- | -------- +`bigquery.datasets.create` | This allows Segment to create/manage a `__segment_reverse_etl` dataset for tracking state between syncs. +`bigquery.datasets.get` | This allows Segment to determine if the aforementioned dataset exists. +`bigquery.jobs.create` | This allows Segment to execute queries on any datasets or tables your model query references, and also allows Segment to manage tables used for tracking. + +If you don't want to grant Segment `bigquery.datasets.create` access, you can create your own `__segment_reverse_etl` dataset and give Segment the following permissions: + +Permission | Details +---------- | -------- +`bigquery.datasets.get` | This allows Segment to determine if the `__segment_reverse_etl` dataset exists. +`bigquery.tables.create` | This allows Segment to determine if the tables Segment uses to track state in the `__segment_reverse_etl` dataset exists. +`bigquery.jobs.create` | This allows Segment to execute queries on any datasets or tables your model query references, and also allows Segment to manage tables used for tracking. + +The `bigquery.datasets.*` permissions can be scoped only to the `__segment_reverse_etl` dataset. ## Create service account @@ -23,27 +41,6 @@ To set up the Segment BigQuery connector: 11. Click **Add Key > Create new key**. 12. In the pop-up window, select **JSON** for the key type and click **Create**. The file will download. -## Constructing your own role or policy -When you construct your own role or policy, Segment needs the following permissions: - -Permission | Details ----------- | -------- -`bigquery.datasets.create` | This allows Segment to create/manage a `__segment_reverse_etl` dataset for tracking state between syncs. -`bigquery.datasets.get` | This allows Segment to determine if the aforementioned dataset exists. -`bigquery.jobs.create` | This allows Segment to execute queries on any datasets or tables your model query references, and also allows Segment to manage tables used for tracking. - -If you don't want to grant Segment `bigquery.datasets.create` access, you can create your own `__segment_reverse_etl` dataset and give Segment the following permissions: - -Permission | Details ----------- | -------- -`bigquery.datasets.get` | This allows Segment to determine if the `__segment_reverse_etl` dataset exists. -`bigquery.tables.create` | This allows Segment to determine if the tables Segment uses to track state in the `__segment_reverse_etl` dataset exists. -`bigquery.jobs.create` | This allows Segment to execute queries on any datasets or tables your model query references, and also allows Segment to manage tables used for tracking. - -The `bigquery.datasets.*` permissions can be scoped only to the `__segment_reverse_etl` dataset. - -After you've successfully added your BigQuery source, [add a model](/docs/connections/reverse-etl/setup/#step-2-add-a-model) and follow the rest of the steps in the Reverse ETL setup guide. - ## Set up BigQuery as your Reverse ETL source 1. Copy all the content within the **JSON** file created and downloaded in previous section. 2. Navigate to the Segment UI and paste all the credentials you copied from previous step into the **Enter your credentials** section. @@ -51,7 +48,7 @@ After you've successfully added your BigQuery source, [add a model](/docs/connec 4. Click **Test Connection** to test to see if the connection works. If the connection fails, make sure you have the right permissions and credentials and try again. 5. Click **Add source** if the test connection is successful. -After you've added BigQuery as a source, you can [add a model](/docs/connections/reverse-etl/setup/#step-2-add-a-model). +After you've added BigQuery as a source, you can [add a model](/docs/connections/reverse-etl/setup/#step-2-add-a-model) and follow the rest of the steps in the Reverse ETL setup guide. > 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. From 753310575eae980106b8206d69bddc062b46c940 Mon Sep 17 00:00:00 2001 From: Gil Omer Date: Wed, 9 Oct 2024 15:37:54 -0400 Subject: [PATCH 04/56] update role creation section --- .../bigquery-setup.md | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) 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 674a933bd9..e9bcead265 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 @@ -22,6 +22,13 @@ Permission | Details The `bigquery.datasets.*` permissions can be scoped only to the `__segment_reverse_etl` dataset. +To create a new role in BigQuery console: +1. Navigate to **IAM & Admin > Roles** in BigQuery. +2. Click **+ CREATE ROLE** to create a new role. +3. Add **title** and **Description** as you like. +4. Click **ADD PERMISSIONS** and add the permission listed in the above tables. You will to repeat that until all required permissions were added. +5. Click **CREATE**. + ## Create service account > warning "" @@ -29,10 +36,10 @@ The `bigquery.datasets.*` permissions can be scoped only to the `__segment_rever To set up the Segment BigQuery connector: 1. Navigate to **IAM & Admin > Service Accounts** in BigQuery. -2. Click **+ Create Service Account** to create a new service account -3. Enter your **Service account name** and a description of what the account will do +2. Click **+ Create Service Account** to create a new service account. +3. Enter your **Service account name** and a description of what the account will do. 4. Click **Create and Continue**. -5. In the **Grant this service account access to project** section, select the *BigQuery User* role to add. +5. In the **Grant this service account access to project** section, select the role you created in the previous section. 6. Click **+ Add another role** and add the *BigQuery Job User* role. 7. Click **Continue**. 8. Click **Done**. From 5e07f378f19f42dfd558ac339c0a7be965255a16 Mon Sep 17 00:00:00 2001 From: joeynmq <37472597+joeynmq@users.noreply.github.com> Date: Thu, 10 Oct 2024 16:38:23 +0800 Subject: [PATCH 05/56] Update index.md --- .../destinations/catalog/actions-braze-web/index.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/src/connections/destinations/catalog/actions-braze-web/index.md b/src/connections/destinations/catalog/actions-braze-web/index.md index 6431c99979..f4bb8aeba7 100644 --- a/src/connections/destinations/catalog/actions-braze-web/index.md +++ b/src/connections/destinations/catalog/actions-braze-web/index.md @@ -172,3 +172,14 @@ When "Enable SDK Authentication" is enabled, Segment will set Braze's `enableSdk Keep the following in mind if you plan to move to Braze (Actions) from the classic Braze destination. {% include components/actions-map-table.html name="braze-web" %} + + +## FAQ + +### How Debounce Middleware works? + +The [Debounce Middleware](/docs/connections/destinations/catalog/actions-braze-web/#debounce-middleware) action is unique and behaves differently from the other actions. Debounce Middleware logic is executed at the source-level: + +- When an Identify call is fired on a website, we will first cache and compare the user traits. If the user traits object differs from what has been cached previously, the data will be passed on to the destination flow (Destination Filters → Insert Functions → Destination Mappings). + +- Otherwise, if user traits are the same as what's cached, we assume that that data was already sent to Braze and a new request is not made to their system. From baea5ce0d4d6a69f045b97cd7a13861f5bf7da81 Mon Sep 17 00:00:00 2001 From: Gil Omer Date: Thu, 10 Oct 2024 11:53:28 -0400 Subject: [PATCH 06/56] updating bigquery source setup --- .../bigquery-setup.md | 84 +++++++++++-------- 1 file changed, 48 insertions(+), 36 deletions(-) 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 e9bcead265..e8a27b1d93 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 @@ -4,15 +4,29 @@ redirect_from: - '/reverse-etl/bigquery-setup/' --- ## Constructing your own role or policy -When you construct your own role or policy, Segment needs the following permissions: +> warning "" +> You need to be an account admin to set up the Segment BigQuery connector as well as write permissions for the `__segment_reverse_etl` dataset. -Permission | Details ----------- | -------- -`bigquery.datasets.create` | This allows Segment to create/manage a `__segment_reverse_etl` dataset for tracking state between syncs. -`bigquery.datasets.get` | This allows Segment to determine if the aforementioned dataset exists. -`bigquery.jobs.create` | This allows Segment to execute queries on any datasets or tables your model query references, and also allows Segment to manage tables used for tracking. +When constructing a role and service-account we provide guidance for two approaches: +1. Grant full access - this approach gives Segment all the required permissions and is slightly faster as it also gives us to permission to automatically complete the setup for you. +2. Grant limited access - this approach is more secured, but because of the limited access we have, we require few additional one time setup steps from you. -If you don't want to grant Segment `bigquery.datasets.create` access, you can create your own `__segment_reverse_etl` dataset and give Segment the following permissions: +You can choose whatever works best for you and skip the other step. + + +### Grant full access +With this approach we will use BigQuery predefined roles: +1. Navigate to **IAM & Admin > Service Accounts** in BigQuery. +2. Click **+ Create Service Account** to create a new service account. +3. Enter your **Service account name** and a description of what the account will do. +4. Click **Create and Continue**. +5. Click **+ Add another role** and add the *BigQuery User* role. +6. Click **+ Add another role** and add the *BigQuery Data Editor* role. +7. Click **Continue**. +8. Click **Done**. + +### Grant limited access +With this approach we will use costume role with the below permissions: Permission | Details ---------- | -------- @@ -20,40 +34,38 @@ Permission | Details `bigquery.tables.create` | This allows Segment to determine if the tables Segment uses to track state in the `__segment_reverse_etl` dataset exists. `bigquery.jobs.create` | This allows Segment to execute queries on any datasets or tables your model query references, and also allows Segment to manage tables used for tracking. -The `bigquery.datasets.*` permissions can be scoped only to the `__segment_reverse_etl` dataset. -To create a new role in BigQuery console: 1. Navigate to **IAM & Admin > Roles** in BigQuery. -2. Click **+ CREATE ROLE** to create a new role. +2. Click **+ CREATE ROLE** to create a new role. 3. Add **title** and **Description** as you like. -4. Click **ADD PERMISSIONS** and add the permission listed in the above tables. You will to repeat that until all required permissions were added. -5. Click **CREATE**. - -## Create service account - -> warning "" -> You need to be an account admin to set up the Segment BigQuery connector as well as write permissions for the `__segment_reverse_etl` dataset. - -To set up the Segment BigQuery connector: -1. Navigate to **IAM & Admin > Service Accounts** in BigQuery. -2. Click **+ Create Service Account** to create a new service account. -3. Enter your **Service account name** and a description of what the account will do. -4. Click **Create and Continue**. -5. In the **Grant this service account access to project** section, select the role you created in the previous section. -6. Click **+ Add another role** and add the *BigQuery Job User* role. -7. Click **Continue**. -8. Click **Done**. -9. Search for the service account you just created. -10. When your service account pulls up, click the 3 dots under **Actions** and select **Manage keys**. -11. Click **Add Key > Create new key**. -12. In the pop-up window, select **JSON** for the key type and click **Create**. The file will download. +4. Click **ADD PERMISSIONS** and add the permission listed in the above tables. You will to repeat that until all required permissions were added. +5. Click **CREATE**. +6. Navigate to **IAM & Admin > Service Accounts** in BigQuery. +7. Click **+ Create Service Account** to create a new service account. +8. Enter your **Service account name** and a description of what the account will do. +9. Click **Create and Continue**. +10. In the **Grant this service account access to project** section, select the role you just created. +11. Click **Continue**. +12. Click **Done**. +13. Navigate to the BigQuery SQL editor and create a dataset that will be used by Segment: + ``` + CREATE SCHEMA IF NOT EXISTS `__segment_reverse_etl`; + ``` +14. Grant additional permissions just on the newly created dataset: + ``` + GRANT `roles/bigquery.dataEditor` ON SCHEMA `__segment_reverse_etl` TO "serviceAccount:"; + ``` ## Set up BigQuery as your Reverse ETL source -1. Copy all the content within the **JSON** file created and downloaded in previous section. -2. Navigate to the Segment UI and paste all the credentials you copied from previous step into the **Enter your credentials** section. -3. Enter your **Data Location**. -4. Click **Test Connection** to test to see if the connection works. If the connection fails, make sure you have the right permissions and credentials and try again. -5. Click **Add source** if the test connection is successful. +1. In the BigQuery console, search for the service account you just created. +2. When your service account pulls up, click the 3 dots under **Actions** and select **Manage keys**. +3. Click **Add Key > Create new key**. +4. In the pop-up window, select **JSON** for the key type and click **Create**. The file will be downloaded. +5. Copy all the content within the **JSON** file created and downloaded in previous section. +6. Navigate to the Segment UI and paste all the credentials you copied from previous step into the **Enter your credentials** section. +7. Enter your **Data Location**. +8. Click **Test Connection** to test to see if the connection works. If the connection fails, make sure you have the right permissions and credentials and try again. +9. Click **Add source** if the test connection is successful. After you've added BigQuery as a source, you can [add a model](/docs/connections/reverse-etl/setup/#step-2-add-a-model) and follow the rest of the steps in the Reverse ETL setup guide. From c923a0d2e0578f977efd13600460e317ddc9f650 Mon Sep 17 00:00:00 2001 From: Gil Omer Date: Thu, 10 Oct 2024 12:13:31 -0400 Subject: [PATCH 07/56] typo and make the custom role more strict --- .../bigquery-setup.md | 19 +++++++++---------- 1 file changed, 9 insertions(+), 10 deletions(-) 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 e8a27b1d93..673eea4bc9 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 @@ -4,34 +4,33 @@ redirect_from: - '/reverse-etl/bigquery-setup/' --- ## Constructing your own role or policy + > warning "" > You need to be an account admin to set up the Segment BigQuery connector as well as write permissions for the `__segment_reverse_etl` dataset. -When constructing a role and service-account we provide guidance for two approaches: -1. Grant full access - this approach gives Segment all the required permissions and is slightly faster as it also gives us to permission to automatically complete the setup for you. -2. Grant limited access - this approach is more secured, but because of the limited access we have, we require few additional one time setup steps from you. - -You can choose whatever works best for you and skip the other step. +When creating a role and service-account, we offer two approaches: +1. **Grant Full Access**: This option provides Segment with all the necessary permissions and allows us to complete the setup for you automatically. It's the quicker option, requiring minimal effort on your part. +2. **Grant Limited Access**: This option is more secure, as it restricts permissions. However, due to the limited access, a few additional setup steps will need to be completed manually by you. These are one-time steps, and we will guide you through the process. +You are free to choose the approach that best suits your needs, and can skip the other. -### Grant full access +### Grant Full Access With this approach we will use BigQuery predefined roles: 1. Navigate to **IAM & Admin > Service Accounts** in BigQuery. 2. Click **+ Create Service Account** to create a new service account. -3. Enter your **Service account name** and a description of what the account will do. +3. Enter your **Service account name** and a description of what the service-account will do. 4. Click **Create and Continue**. 5. Click **+ Add another role** and add the *BigQuery User* role. 6. Click **+ Add another role** and add the *BigQuery Data Editor* role. 7. Click **Continue**. 8. Click **Done**. -### Grant limited access -With this approach we will use costume role with the below permissions: +### Grant Limited Access +With this approach we will use custom role with the below permissions: Permission | Details ---------- | -------- `bigquery.datasets.get` | This allows Segment to determine if the `__segment_reverse_etl` dataset exists. -`bigquery.tables.create` | This allows Segment to determine if the tables Segment uses to track state in the `__segment_reverse_etl` dataset exists. `bigquery.jobs.create` | This allows Segment to execute queries on any datasets or tables your model query references, and also allows Segment to manage tables used for tracking. From 8ba9f5d336299ae240191a13d497809f614b5d45 Mon Sep 17 00:00:00 2001 From: Gil Omer Date: Thu, 10 Oct 2024 12:20:23 -0400 Subject: [PATCH 08/56] more info regarding location --- .../reverse-etl-source-setup-guides/bigquery-setup.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) 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 673eea4bc9..cba2fbbfbb 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 @@ -62,7 +62,10 @@ Permission | Details 4. In the pop-up window, select **JSON** for the key type and click **Create**. The file will be downloaded. 5. Copy all the content within the **JSON** file created and downloaded in previous section. 6. Navigate to the Segment UI and paste all the credentials you copied from previous step into the **Enter your credentials** section. -7. Enter your **Data Location**. +7. Enter your **Data Location**. The data location can be found by: + - In the BigQuery console navigate to your dataset: In the explorer panel on the left, expand the project and dataset to view the tables. + - Click on the name of the dataset, and it will open a page showing its details. + - The Location of the dataset (like US, EU, etc.) is displayed in the Dataset Info. 8. Click **Test Connection** to test to see if the connection works. If the connection fails, make sure you have the right permissions and credentials and try again. 9. Click **Add source** if the test connection is successful. From fc28a3d59b2d050a06c401b547b852a0961ba449 Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Thu, 10 Oct 2024 11:46:18 -0500 Subject: [PATCH 09/56] quick fix [netlify-build] --- .../reverse-etl-source-setup-guides/bigquery-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 cba2fbbfbb..f20277f6b3 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 @@ -65,7 +65,7 @@ Permission | Details 7. Enter your **Data Location**. The data location can be found by: - In the BigQuery console navigate to your dataset: In the explorer panel on the left, expand the project and dataset to view the tables. - Click on the name of the dataset, and it will open a page showing its details. - - The Location of the dataset (like US, EU, etc.) is displayed in the Dataset Info. + - The Location of the dataset (like US or EU) is displayed in the Dataset Info. 8. Click **Test Connection** to test to see if the connection works. If the connection fails, make sure you have the right permissions and credentials and try again. 9. Click **Add source** if the test connection is successful. From 272a6e2e9d9b698445d6e0812b2410c277a5bd94 Mon Sep 17 00:00:00 2001 From: Gil Omer Date: Thu, 10 Oct 2024 13:02:37 -0400 Subject: [PATCH 10/56] add highlight --- .../reverse-etl-source-setup-guides/bigquery-setup.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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 f20277f6b3..5661e63b2e 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 @@ -20,8 +20,8 @@ With this approach we will use BigQuery predefined roles: 2. Click **+ Create Service Account** to create a new service account. 3. Enter your **Service account name** and a description of what the service-account will do. 4. Click **Create and Continue**. -5. Click **+ Add another role** and add the *BigQuery User* role. -6. Click **+ Add another role** and add the *BigQuery Data Editor* role. +5. Click **+ Add another role** and add the **BigQuery User** role. +6. Click **+ Add another role** and add the **BigQuery Data Editor** role. 7. Click **Continue**. 8. Click **Done**. From c3bc8874e1ca811ce4a9cf05bfa226845c4bbe6d Mon Sep 17 00:00:00 2001 From: Gil Omer Date: Thu, 10 Oct 2024 14:42:23 -0400 Subject: [PATCH 11/56] add additional required permission --- .../reverse-etl-source-setup-guides/bigquery-setup.md | 1 + 1 file changed, 1 insertion(+) 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 5661e63b2e..40aa116a63 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 @@ -32,6 +32,7 @@ Permission | Details ---------- | -------- `bigquery.datasets.get` | This allows Segment to determine if the `__segment_reverse_etl` dataset exists. `bigquery.jobs.create` | This allows Segment to execute queries on any datasets or tables your model query references, and also allows Segment to manage tables used for tracking. +`bigquery.tables.getData` | This allows Segment to run `SELECT` queries on tables that will be defined in the model. 1. Navigate to **IAM & Admin > Roles** in BigQuery. From d52f8195369aedcbd1e1c6e0b4077cbc6db94691 Mon Sep 17 00:00:00 2001 From: Gil Omer <80776787+gilsegment@users.noreply.github.com> Date: Thu, 10 Oct 2024 14:43:53 -0400 Subject: [PATCH 12/56] Update src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- .../reverse-etl-source-setup-guides/bigquery-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 40aa116a63..d780b9b0a8 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 @@ -12,7 +12,7 @@ When creating a role and service-account, we offer two approaches: 1. **Grant Full Access**: This option provides Segment with all the necessary permissions and allows us to complete the setup for you automatically. It's the quicker option, requiring minimal effort on your part. 2. **Grant Limited Access**: This option is more secure, as it restricts permissions. However, due to the limited access, a few additional setup steps will need to be completed manually by you. These are one-time steps, and we will guide you through the process. -You are free to choose the approach that best suits your needs, and can skip the other. +You can choose the approach that best suits your needs. ### Grant Full Access With this approach we will use BigQuery predefined roles: From 8490ddd243525e879f14917af8615d06b50d0d6a Mon Sep 17 00:00:00 2001 From: Gil Omer <80776787+gilsegment@users.noreply.github.com> Date: Thu, 10 Oct 2024 14:44:22 -0400 Subject: [PATCH 13/56] Update src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- .../reverse-etl-source-setup-guides/bigquery-setup.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) 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 d780b9b0a8..09f67f4d4c 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 @@ -18,7 +18,8 @@ You can choose the approach that best suits your needs. With this approach we will use BigQuery predefined roles: 1. Navigate to **IAM & Admin > Service Accounts** in BigQuery. 2. Click **+ Create Service Account** to create a new service account. -3. Enter your **Service account name** and a description of what the service-account will do. +3. Enter your **Service account name** and a description of what the service account will do. + 4. Click **Create and Continue**. 5. Click **+ Add another role** and add the **BigQuery User** role. 6. Click **+ Add another role** and add the **BigQuery Data Editor** role. From 060be82c9858e6b0e18df972bb076e22c4a3bf3c Mon Sep 17 00:00:00 2001 From: Gil Omer <80776787+gilsegment@users.noreply.github.com> Date: Thu, 10 Oct 2024 14:44:54 -0400 Subject: [PATCH 14/56] Update src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- .../reverse-etl-source-setup-guides/bigquery-setup.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) 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 09f67f4d4c..ffe4865c58 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 @@ -23,8 +23,7 @@ With this approach we will use BigQuery predefined roles: 4. Click **Create and Continue**. 5. Click **+ Add another role** and add the **BigQuery User** role. 6. Click **+ Add another role** and add the **BigQuery Data Editor** role. -7. Click **Continue**. -8. Click **Done**. +7. Click **Continue**., then click **Done**. ### Grant Limited Access With this approach we will use custom role with the below permissions: From f2c2bced036e8640735cfdce997069211f1ac149 Mon Sep 17 00:00:00 2001 From: Gil Omer <80776787+gilsegment@users.noreply.github.com> Date: Thu, 10 Oct 2024 14:48:20 -0400 Subject: [PATCH 15/56] Update src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- .../reverse-etl-source-setup-guides/bigquery-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 ffe4865c58..c75b3f3b42 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 @@ -52,7 +52,7 @@ Permission | Details CREATE SCHEMA IF NOT EXISTS `__segment_reverse_etl`; ``` 14. Grant additional permissions just on the newly created dataset: - ``` + ```sql GRANT `roles/bigquery.dataEditor` ON SCHEMA `__segment_reverse_etl` TO "serviceAccount:"; ``` From 62beb232a50d1ad1a86ee8a84c8d835c1c7021c1 Mon Sep 17 00:00:00 2001 From: Gil Omer <80776787+gilsegment@users.noreply.github.com> Date: Thu, 10 Oct 2024 14:48:31 -0400 Subject: [PATCH 16/56] Update src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- .../reverse-etl-source-setup-guides/bigquery-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 c75b3f3b42..02b4e18899 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 @@ -48,7 +48,7 @@ Permission | Details 11. Click **Continue**. 12. Click **Done**. 13. Navigate to the BigQuery SQL editor and create a dataset that will be used by Segment: - ``` + ```sql CREATE SCHEMA IF NOT EXISTS `__segment_reverse_etl`; ``` 14. Grant additional permissions just on the newly created dataset: From 018f1111461f394ba0df60ab998c77793f3b0648 Mon Sep 17 00:00:00 2001 From: Gil Omer <80776787+gilsegment@users.noreply.github.com> Date: Thu, 10 Oct 2024 14:48:51 -0400 Subject: [PATCH 17/56] Update src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- .../reverse-etl-source-setup-guides/bigquery-setup.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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 02b4e18899..6c901893cb 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 @@ -15,8 +15,8 @@ When creating a role and service-account, we offer two approaches: You can choose the approach that best suits your needs. ### Grant Full Access -With this approach we will use BigQuery predefined roles: -1. Navigate to **IAM & Admin > Service Accounts** in BigQuery. +With this approach, use BigQuery predefined roles to create a service account for Segment to assume. +1. In BigQuery, navigate to **IAM & Admin > Service Accounts**. 2. Click **+ Create Service Account** to create a new service account. 3. Enter your **Service account name** and a description of what the service account will do. From 3be45e5e7367813a283351ebdb1781bfb3a5b90e Mon Sep 17 00:00:00 2001 From: Gil Omer <80776787+gilsegment@users.noreply.github.com> Date: Thu, 10 Oct 2024 14:49:06 -0400 Subject: [PATCH 18/56] Update src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md Co-authored-by: Prayansh Srivastava --- .../reverse-etl-source-setup-guides/bigquery-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 6c901893cb..d3478bbce6 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 @@ -21,7 +21,7 @@ With this approach, use BigQuery predefined roles to create a service account fo 3. Enter your **Service account name** and a description of what the service account will do. 4. Click **Create and Continue**. -5. Click **+ Add another role** and add the **BigQuery User** role. +5. Click **+ Add another role** and add the [**BigQuery User**](https://cloud.google.com/bigquery/docs/access-control#bigquery.user) role. 6. Click **+ Add another role** and add the **BigQuery Data Editor** role. 7. Click **Continue**., then click **Done**. From 225da70ab51835e5568a97880c6e38da944632ab Mon Sep 17 00:00:00 2001 From: Gil Omer <80776787+gilsegment@users.noreply.github.com> Date: Thu, 10 Oct 2024 14:49:36 -0400 Subject: [PATCH 19/56] Update src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md Co-authored-by: Prayansh Srivastava --- .../reverse-etl-source-setup-guides/bigquery-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 d3478bbce6..0abb75ba39 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 @@ -26,7 +26,7 @@ With this approach, use BigQuery predefined roles to create a service account fo 7. Click **Continue**., then click **Done**. ### Grant Limited Access -With this approach we will use custom role with the below permissions: +With this approach we will setup a custom role with the following permissions: Permission | Details ---------- | -------- From 7c22cc153652788898b6790ebaf750700f0e950b Mon Sep 17 00:00:00 2001 From: Gil Omer <80776787+gilsegment@users.noreply.github.com> Date: Thu, 10 Oct 2024 14:49:49 -0400 Subject: [PATCH 20/56] Update src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- .../reverse-etl-source-setup-guides/bigquery-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 0abb75ba39..c277272e53 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 @@ -35,7 +35,7 @@ Permission | Details `bigquery.tables.getData` | This allows Segment to run `SELECT` queries on tables that will be defined in the model. -1. Navigate to **IAM & Admin > Roles** in BigQuery. +1. In BigQuery, navigate to **IAM & Admin > Roles**. 2. Click **+ CREATE ROLE** to create a new role. 3. Add **title** and **Description** as you like. 4. Click **ADD PERMISSIONS** and add the permission listed in the above tables. You will to repeat that until all required permissions were added. From 1379da91e216b27474719f43b87efe33ea38ca38 Mon Sep 17 00:00:00 2001 From: Gil Omer <80776787+gilsegment@users.noreply.github.com> Date: Thu, 10 Oct 2024 14:50:02 -0400 Subject: [PATCH 21/56] Update src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md Co-authored-by: Prayansh Srivastava --- .../reverse-etl-source-setup-guides/bigquery-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 c277272e53..c8332f3987 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 @@ -38,7 +38,7 @@ Permission | Details 1. In BigQuery, navigate to **IAM & Admin > Roles**. 2. Click **+ CREATE ROLE** to create a new role. 3. Add **title** and **Description** as you like. -4. Click **ADD PERMISSIONS** and add the permission listed in the above tables. You will to repeat that until all required permissions were added. +4. Click **ADD PERMISSIONS** and add the permission listed in the above tables. You will need to repeat that until all required permissions are added. 5. Click **CREATE**. 6. Navigate to **IAM & Admin > Service Accounts** in BigQuery. 7. Click **+ Create Service Account** to create a new service account. From 3f6d47920eaaedef615b6e720c006934d37a640a Mon Sep 17 00:00:00 2001 From: Gil Omer <80776787+gilsegment@users.noreply.github.com> Date: Thu, 10 Oct 2024 14:50:16 -0400 Subject: [PATCH 22/56] Update src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- .../reverse-etl-source-setup-guides/bigquery-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 c8332f3987..654d091bb1 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 @@ -40,7 +40,7 @@ Permission | Details 3. Add **title** and **Description** as you like. 4. Click **ADD PERMISSIONS** and add the permission listed in the above tables. You will need to repeat that until all required permissions are added. 5. Click **CREATE**. -6. Navigate to **IAM & Admin > Service Accounts** in BigQuery. +6. Navigate to **IAM & Admin > Service Accounts**. 7. Click **+ Create Service Account** to create a new service account. 8. Enter your **Service account name** and a description of what the account will do. 9. Click **Create and Continue**. From 96e98bf540d394bde354e28a32848da0a3610b05 Mon Sep 17 00:00:00 2001 From: Gil Omer <80776787+gilsegment@users.noreply.github.com> Date: Thu, 10 Oct 2024 14:50:27 -0400 Subject: [PATCH 23/56] Update src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md Co-authored-by: Prayansh Srivastava --- .../reverse-etl-source-setup-guides/bigquery-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 654d091bb1..34e7961eb7 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 @@ -46,7 +46,7 @@ Permission | Details 9. Click **Create and Continue**. 10. In the **Grant this service account access to project** section, select the role you just created. 11. Click **Continue**. -12. Click **Done**. +12. Click **Done**. Copy and keep the Service Account email handy for the next steps 13. Navigate to the BigQuery SQL editor and create a dataset that will be used by Segment: ```sql CREATE SCHEMA IF NOT EXISTS `__segment_reverse_etl`; From 5238b2b395a190c0aee63c40030e7d16d0f4de33 Mon Sep 17 00:00:00 2001 From: Gil Omer <80776787+gilsegment@users.noreply.github.com> Date: Thu, 10 Oct 2024 14:50:48 -0400 Subject: [PATCH 24/56] Update src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- .../reverse-etl-source-setup-guides/bigquery-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 34e7961eb7..cd8b7573a5 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 @@ -57,7 +57,7 @@ Permission | Details ``` ## Set up BigQuery as your Reverse ETL source -1. In the BigQuery console, search for the service account you just created. +1. In the BigQuery console, search for the service account you created. 2. When your service account pulls up, click the 3 dots under **Actions** and select **Manage keys**. 3. Click **Add Key > Create new key**. 4. In the pop-up window, select **JSON** for the key type and click **Create**. The file will be downloaded. From 7d533f6f572846f1dad383684b5e883d189a2bf0 Mon Sep 17 00:00:00 2001 From: Gil Omer <80776787+gilsegment@users.noreply.github.com> Date: Thu, 10 Oct 2024 15:10:40 -0400 Subject: [PATCH 25/56] Apply suggestions from code review Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- .../reverse-etl-source-setup-guides/bigquery-setup.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) 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 cd8b7573a5..5037688fe5 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 @@ -8,9 +8,9 @@ redirect_from: > warning "" > You need to be an account admin to set up the Segment BigQuery connector as well as write permissions for the `__segment_reverse_etl` dataset. -When creating a role and service-account, we offer two approaches: -1. **Grant Full Access**: This option provides Segment with all the necessary permissions and allows us to complete the setup for you automatically. It's the quicker option, requiring minimal effort on your part. -2. **Grant Limited Access**: This option is more secure, as it restricts permissions. However, due to the limited access, a few additional setup steps will need to be completed manually by you. These are one-time steps, and we will guide you through the process. +There are two approaches you can take when granting Segment access to your BigQuery resources: +1. **Grant Full Access**: This option allows Segment to automatically complete the setup for you after you provide Segment with all the necessary permissions. This option requires less time and engineering effort on your part. +2. **Grant Limited Access**: This option is more secure, as it restricts the permissions Segment has access to. However, due to the limited access, you must complete a few additional setup steps. These are one-time steps, and the documentation provides you with the information required to complete this process. You can choose the approach that best suits your needs. From 720c2753468d8dbfcfd971ab891b66b498013bea Mon Sep 17 00:00:00 2001 From: Gil Omer <80776787+gilsegment@users.noreply.github.com> Date: Thu, 10 Oct 2024 15:11:21 -0400 Subject: [PATCH 26/56] Update src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md Co-authored-by: Prayansh Srivastava --- .../reverse-etl-source-setup-guides/bigquery-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 5037688fe5..c72de9d80d 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 @@ -22,7 +22,7 @@ With this approach, use BigQuery predefined roles to create a service account fo 4. Click **Create and Continue**. 5. Click **+ Add another role** and add the [**BigQuery User**](https://cloud.google.com/bigquery/docs/access-control#bigquery.user) role. -6. Click **+ Add another role** and add the **BigQuery Data Editor** role. +6. Click **+ Add another role** and add the [**BigQuery Data Editor**](https://cloud.google.com/bigquery/docs/access-control#bigquery.dataEditor) role. 7. Click **Continue**., then click **Done**. ### Grant Limited Access From fc7edc121082e00d47e908c8231500e12fd95ebd Mon Sep 17 00:00:00 2001 From: Gil Omer <80776787+gilsegment@users.noreply.github.com> Date: Thu, 10 Oct 2024 15:20:04 -0400 Subject: [PATCH 27/56] Update src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md Co-authored-by: Prayansh Srivastava --- .../reverse-etl-source-setup-guides/bigquery-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 c72de9d80d..2583cfea34 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 @@ -51,7 +51,7 @@ Permission | Details ```sql CREATE SCHEMA IF NOT EXISTS `__segment_reverse_etl`; ``` -14. Grant additional permissions just on the newly created dataset: +14. Grant Limited Access to the Segment Reverse ETL dataset ```sql GRANT `roles/bigquery.dataEditor` ON SCHEMA `__segment_reverse_etl` TO "serviceAccount:"; ``` From 6fe618d61ad537c8a52308d9d16e7210c30c7175 Mon Sep 17 00:00:00 2001 From: Gil Omer <80776787+gilsegment@users.noreply.github.com> Date: Thu, 10 Oct 2024 15:20:55 -0400 Subject: [PATCH 28/56] Update src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- .../reverse-etl-source-setup-guides/bigquery-setup.md | 8 ++++++++ 1 file changed, 8 insertions(+) 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 2583cfea34..82d441c5fa 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 @@ -56,6 +56,14 @@ Permission | Details GRANT `roles/bigquery.dataEditor` ON SCHEMA `__segment_reverse_etl` TO "serviceAccount:"; ``` +### BigQuery resource location +When connecting your BigQuery warehouse to Segment, you'll need to know the location of your resources. + +You can find the location of your BigQuery resources using the following method: +1. In the BigQuery console, navigate to your dataset. In the explorer panel on the left, expand the project and dataset to view the tables. +2. Click on the name of the dataset, and it opens a page showing its details. +3. The Location of the dataset (like US or EU) is displayed in the Dataset Info. + ## Set up BigQuery as your Reverse ETL source 1. In the BigQuery console, search for the service account you created. 2. When your service account pulls up, click the 3 dots under **Actions** and select **Manage keys**. From fa8ba2420f748b75b05ade958f9a47157145685f Mon Sep 17 00:00:00 2001 From: Gil Omer <80776787+gilsegment@users.noreply.github.com> Date: Thu, 10 Oct 2024 15:21:36 -0400 Subject: [PATCH 29/56] Update src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- .../bigquery-setup.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) 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 82d441c5fa..888535ca9e 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 @@ -69,14 +69,14 @@ You can find the location of your BigQuery resources using the following method: 2. When your service account pulls up, click the 3 dots under **Actions** and select **Manage keys**. 3. Click **Add Key > Create new key**. 4. In the pop-up window, select **JSON** for the key type and click **Create**. The file will be downloaded. -5. Copy all the content within the **JSON** file created and downloaded in previous section. -6. Navigate to the Segment UI and paste all the credentials you copied from previous step into the **Enter your credentials** section. -7. Enter your **Data Location**. The data location can be found by: - - In the BigQuery console navigate to your dataset: In the explorer panel on the left, expand the project and dataset to view the tables. - - Click on the name of the dataset, and it will open a page showing its details. - - The Location of the dataset (like US or EU) is displayed in the Dataset Info. -8. Click **Test Connection** to test to see if the connection works. If the connection fails, make sure you have the right permissions and credentials and try again. -9. Click **Add source** if the test connection is successful. +5. Copy all the content in the JSON file you created in the previous step. +6. Open the Segment app and navigate to **Connections > Sources**. +7. On the My sources page, click **+ Add source**. +8. Search for "BigQuery" and select the BigQuery source from the sources catalog. On the BigQuery overview page, click **Add Source**. +9. On the Set up BigQuery page, enter a name for your source and paste all the credentials you copied from previous step into the **Enter your credentials** section. +10. Enter the location of your BigQuery warehouse in the **Data Location** field. +11. Click **Test Connection** to test to see if the connection works. If the connection fails, make sure you have the right permissions and credentials and try again. +12. If the test connection completes successfully, click **Add source** to complete the setup process. After you've added BigQuery as a source, you can [add a model](/docs/connections/reverse-etl/setup/#step-2-add-a-model) and follow the rest of the steps in the Reverse ETL setup guide. From 70d7adf699db4f094ff188fa0cbdbfb05d1f6262 Mon Sep 17 00:00:00 2001 From: Gil Omer Date: Thu, 10 Oct 2024 15:38:39 -0400 Subject: [PATCH 30/56] use lower case when needed --- .../reverse-etl-source-setup-guides/bigquery-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 888535ca9e..56b4183a4a 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 @@ -51,7 +51,7 @@ Permission | Details ```sql CREATE SCHEMA IF NOT EXISTS `__segment_reverse_etl`; ``` -14. Grant Limited Access to the Segment Reverse ETL dataset +14. Grant limited Access to the Segment Reverse ETL dataset ```sql GRANT `roles/bigquery.dataEditor` ON SCHEMA `__segment_reverse_etl` TO "serviceAccount:"; ``` From ec3b0af462ac7831d7a6fdf32031b8f9bdae99ae Mon Sep 17 00:00:00 2001 From: prigiattiperrut <47340158+prigiattiperrut@users.noreply.github.com> Date: Fri, 11 Oct 2024 13:44:32 +0100 Subject: [PATCH 31/56] Update faq.md --- src/protocols/faq.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/protocols/faq.md b/src/protocols/faq.md index be0e83f046..e3925f54a9 100644 --- a/src/protocols/faq.md +++ b/src/protocols/faq.md @@ -208,3 +208,7 @@ Transformations are but one tool among many to help you improve data quality. Se ### Are transformations applied when using the Event Tester? Transformations are not applied to events sent through the [Event Tester](/docs/connections/test-connections/). The Event Tester operates independently from the Segment pipeline, focusing solely on testing specific connections to a destination. For a transformation to take effect, the event must be processed through the Segment pipeline. + +### Why am I getting the error "rules must contain less than or equal to 200 items" when using the Public API and can this limit be increased? + +This error occurs because there is a limit of 200 rules per API update, which is by design to ensure stable API performance. Unfortunately, increasing this limit isn’t possible at the moment. To work around this, split your update into smaller batches with 200 or fewer rules each. From d3431e2ac54de90e0772eaa11c0cc54411fbb55f Mon Sep 17 00:00:00 2001 From: Gil Omer Date: Fri, 11 Oct 2024 09:32:49 -0400 Subject: [PATCH 32/56] [netlify-build] From 52069f93d8d511ed2f972435d7eee567c516d08a Mon Sep 17 00:00:00 2001 From: Gil Omer Date: Fri, 11 Oct 2024 13:38:24 -0400 Subject: [PATCH 33/56] remove extra dot --- .../reverse-etl-source-setup-guides/bigquery-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 56b4183a4a..4db0d14788 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 @@ -23,7 +23,7 @@ With this approach, use BigQuery predefined roles to create a service account fo 4. Click **Create and Continue**. 5. Click **+ Add another role** and add the [**BigQuery User**](https://cloud.google.com/bigquery/docs/access-control#bigquery.user) role. 6. Click **+ Add another role** and add the [**BigQuery Data Editor**](https://cloud.google.com/bigquery/docs/access-control#bigquery.dataEditor) role. -7. Click **Continue**., then click **Done**. +7. Click **Continue**, then click **Done**. ### Grant Limited Access With this approach we will setup a custom role with the following permissions: From 171fa392ec2daefea125501b6750be170f67e407 Mon Sep 17 00:00:00 2001 From: Gil Omer Date: Fri, 11 Oct 2024 13:45:33 -0400 Subject: [PATCH 34/56] [netlify-build] some additional changes --- .../bigquery-setup.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) 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 4db0d14788..bdb319227a 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,6 +3,9 @@ title: BigQuery Reverse ETL Setup redirect_from: - '/reverse-etl/bigquery-setup/' --- +> 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. + ## Constructing your own role or policy > warning "" @@ -23,7 +26,7 @@ With this approach, use BigQuery predefined roles to create a service account fo 4. Click **Create and Continue**. 5. Click **+ Add another role** and add the [**BigQuery User**](https://cloud.google.com/bigquery/docs/access-control#bigquery.user) role. 6. Click **+ Add another role** and add the [**BigQuery Data Editor**](https://cloud.google.com/bigquery/docs/access-control#bigquery.dataEditor) role. -7. Click **Continue**, then click **Done**. +7. Click **Continue**, then click **Done**. ### Grant Limited Access With this approach we will setup a custom role with the following permissions: @@ -37,7 +40,7 @@ Permission | Details 1. In BigQuery, navigate to **IAM & Admin > Roles**. 2. Click **+ CREATE ROLE** to create a new role. -3. Add **title** and **Description** as you like. +3. Add **Title** and **Description** as you like. 4. Click **ADD PERMISSIONS** and add the permission listed in the above tables. You will need to repeat that until all required permissions are added. 5. Click **CREATE**. 6. Navigate to **IAM & Admin > Service Accounts**. @@ -46,12 +49,12 @@ Permission | Details 9. Click **Create and Continue**. 10. In the **Grant this service account access to project** section, select the role you just created. 11. Click **Continue**. -12. Click **Done**. Copy and keep the Service Account email handy for the next steps +12. Click **Done**. Copy and keep the Service Account email handy for the next steps. 13. Navigate to the BigQuery SQL editor and create a dataset that will be used by Segment: ```sql CREATE SCHEMA IF NOT EXISTS `__segment_reverse_etl`; ``` -14. Grant limited Access to the Segment Reverse ETL dataset +14. Grant limited access to the Segment Reverse ETL dataset ```sql GRANT `roles/bigquery.dataEditor` ON SCHEMA `__segment_reverse_etl` TO "serviceAccount:"; ``` @@ -71,14 +74,11 @@ You can find the location of your BigQuery resources using the following method: 4. In the pop-up window, select **JSON** for the key type and click **Create**. The file will be downloaded. 5. Copy all the content in the JSON file you created in the previous step. 6. Open the Segment app and navigate to **Connections > Sources**. -7. On the My sources page, click **+ Add source**. +7. On the _My sources_ page, click **+ Add source**. 8. Search for "BigQuery" and select the BigQuery source from the sources catalog. On the BigQuery overview page, click **Add Source**. -9. On the Set up BigQuery page, enter a name for your source and paste all the credentials you copied from previous step into the **Enter your credentials** section. +9. On the _Set up BigQuery_ page, enter a name for your source and paste all the credentials you copied from previous step into the **Enter your credentials** section. 10. Enter the location of your BigQuery warehouse in the **Data Location** field. 11. Click **Test Connection** to test to see if the connection works. If the connection fails, make sure you have the right permissions and credentials and try again. 12. If the test connection completes successfully, click **Add source** to complete the setup process. After you've added BigQuery as a source, you can [add a model](/docs/connections/reverse-etl/setup/#step-2-add-a-model) and follow the rest of the steps in the Reverse ETL setup guide. - -> 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. From 459c2387d73b6e4eee1dd10695f90af4d6889637 Mon Sep 17 00:00:00 2001 From: Gil Omer <80776787+gilsegment@users.noreply.github.com> Date: Mon, 14 Oct 2024 21:13:16 -0400 Subject: [PATCH 35/56] Update src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- .../reverse-etl-source-setup-guides/bigquery-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 bdb319227a..b5f4962a57 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 @@ -74,7 +74,7 @@ You can find the location of your BigQuery resources using the following method: 4. In the pop-up window, select **JSON** for the key type and click **Create**. The file will be downloaded. 5. Copy all the content in the JSON file you created in the previous step. 6. Open the Segment app and navigate to **Connections > Sources**. -7. On the _My sources_ page, click **+ Add source**. +7. On the My sources page, click **+ Add source**. 8. Search for "BigQuery" and select the BigQuery source from the sources catalog. On the BigQuery overview page, click **Add Source**. 9. On the _Set up BigQuery_ page, enter a name for your source and paste all the credentials you copied from previous step into the **Enter your credentials** section. 10. Enter the location of your BigQuery warehouse in the **Data Location** field. From e8b44cb494f5cae6a2a076a10d7ed3264986ec42 Mon Sep 17 00:00:00 2001 From: Gil Omer <80776787+gilsegment@users.noreply.github.com> Date: Mon, 14 Oct 2024 21:13:29 -0400 Subject: [PATCH 36/56] Update src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- .../reverse-etl-source-setup-guides/bigquery-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 b5f4962a57..69ed0702f4 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 @@ -76,7 +76,7 @@ You can find the location of your BigQuery resources using the following method: 6. Open the Segment app and navigate to **Connections > Sources**. 7. On the My sources page, click **+ Add source**. 8. Search for "BigQuery" and select the BigQuery source from the sources catalog. On the BigQuery overview page, click **Add Source**. -9. On the _Set up BigQuery_ page, enter a name for your source and paste all the credentials you copied from previous step into the **Enter your credentials** section. +9. On the Set up BigQuery page, enter a name for your source and paste all the credentials you copied from previous step into the **Enter your credentials** section. 10. Enter the location of your BigQuery warehouse in the **Data Location** field. 11. Click **Test Connection** to test to see if the connection works. If the connection fails, make sure you have the right permissions and credentials and try again. 12. If the test connection completes successfully, click **Add source** to complete the setup process. From 6faadd5508243ab6a40af86733f761096508b3d1 Mon Sep 17 00:00:00 2001 From: Gil Omer <80776787+gilsegment@users.noreply.github.com> Date: Mon, 14 Oct 2024 21:13:52 -0400 Subject: [PATCH 37/56] Update src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- .../reverse-etl-source-setup-guides/bigquery-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 69ed0702f4..59e43db2ad 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 @@ -41,7 +41,7 @@ Permission | Details 1. In BigQuery, navigate to **IAM & Admin > Roles**. 2. Click **+ CREATE ROLE** to create a new role. 3. Add **Title** and **Description** as you like. -4. Click **ADD PERMISSIONS** and add the permission listed in the above tables. You will need to repeat that until all required permissions are added. +4. Click **ADD PERMISSIONS** and add the permission listed in the above tables. Repeat this step until you've added all required permissions. 5. Click **CREATE**. 6. Navigate to **IAM & Admin > Service Accounts**. 7. Click **+ Create Service Account** to create a new service account. From 20e96e9dfc98f9da012bc92c139afc17ea39fa79 Mon Sep 17 00:00:00 2001 From: Gil Omer <80776787+gilsegment@users.noreply.github.com> Date: Mon, 14 Oct 2024 21:14:27 -0400 Subject: [PATCH 38/56] Update src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- .../reverse-etl-source-setup-guides/bigquery-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 59e43db2ad..b8bea74d48 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 @@ -29,7 +29,7 @@ With this approach, use BigQuery predefined roles to create a service account fo 7. Click **Continue**, then click **Done**. ### Grant Limited Access -With this approach we will setup a custom role with the following permissions: +With this approach, you can set up a custom role with the following permissions: Permission | Details ---------- | -------- From 3bb85f001314ab32f746d593ac7373b4eac123af Mon Sep 17 00:00:00 2001 From: Gil Omer <80776787+gilsegment@users.noreply.github.com> Date: Mon, 14 Oct 2024 21:15:41 -0400 Subject: [PATCH 39/56] Update src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- .../reverse-etl-source-setup-guides/bigquery-setup.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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 b8bea74d48..bad4254d30 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 @@ -24,8 +24,8 @@ With this approach, use BigQuery predefined roles to create a service account fo 3. Enter your **Service account name** and a description of what the service account will do. 4. Click **Create and Continue**. -5. Click **+ Add another role** and add the [**BigQuery User**](https://cloud.google.com/bigquery/docs/access-control#bigquery.user) role. -6. Click **+ Add another role** and add the [**BigQuery Data Editor**](https://cloud.google.com/bigquery/docs/access-control#bigquery.dataEditor) role. +5. Click **+ Add another role** and add the [**BigQuery User**](https://cloud.google.com/bigquery/docs/access-control#bigquery.user){:target="_blank”} role. +6. Click **+ Add another role** and add the [**BigQuery Data Editor**](https://cloud.google.com/bigquery/docs/access-control#bigquery.dataEditor){:target="_blank”} role. 7. Click **Continue**, then click **Done**. ### Grant Limited Access From d0541dbdf9cdfb866ed0d5b7d02f85351a1662d0 Mon Sep 17 00:00:00 2001 From: Gil Omer <80776787+gilsegment@users.noreply.github.com> Date: Mon, 14 Oct 2024 21:17:08 -0400 Subject: [PATCH 40/56] Update src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- .../reverse-etl-source-setup-guides/bigquery-setup.md | 2 ++ 1 file changed, 2 insertions(+) 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 bad4254d30..481065a9ca 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,6 +3,8 @@ 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). + > 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. From 4baab70b7c5c24573f1d6ecbc95de991af91b851 Mon Sep 17 00:00:00 2001 From: Gil Omer <80776787+gilsegment@users.noreply.github.com> Date: Mon, 14 Oct 2024 21:17:21 -0400 Subject: [PATCH 41/56] Update src/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- .../reverse-etl-source-setup-guides/bigquery-setup.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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 481065a9ca..13ffb41f51 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 @@ -14,8 +14,8 @@ To set up your BigQuery source with Reverse ETL, you must [construct a BigQuery > You need to be an account admin to set up the Segment BigQuery connector as well as write permissions for the `__segment_reverse_etl` dataset. There are two approaches you can take when granting Segment access to your BigQuery resources: -1. **Grant Full Access**: This option allows Segment to automatically complete the setup for you after you provide Segment with all the necessary permissions. This option requires less time and engineering effort on your part. -2. **Grant Limited Access**: This option is more secure, as it restricts the permissions Segment has access to. However, due to the limited access, you must complete a few additional setup steps. These are one-time steps, and the documentation provides you with the information required to complete this process. +- **Grant Full Access**: This option allows Segment to automatically complete the setup for you after you provide Segment with all the necessary permissions. This option requires less time and engineering effort on your part. +- **Grant Limited Access**: This option is more secure, as it restricts the permissions Segment has access to. However, due to the limited access, you must complete a few additional setup steps. These are one-time steps, and the documentation provides you with the information required to complete this process. You can choose the approach that best suits your needs. From cde7271ebea99493f04470ae6977128e559e824d Mon Sep 17 00:00:00 2001 From: Spencer Attick <23665784+spencerattick@users.noreply.github.com> Date: Tue, 15 Oct 2024 06:40:51 -0400 Subject: [PATCH 42/56] array info for Triggers --- src/connections/destinations/actions.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/connections/destinations/actions.md b/src/connections/destinations/actions.md index bb8852d078..375228e66c 100644 --- a/src/connections/destinations/actions.md +++ b/src/connections/destinations/actions.md @@ -38,7 +38,8 @@ A Destination Action contains a hierarchy of components, that work together to e | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Global Settings | Define authentication and connection-related information like API and Secret keys. | | Mappings | Handle the individual calls to the destination. In them, you define what type of call you want to make to the destination, and what Triggers that call. Individual Destination Actions may come enabled with some predefined mappings to handle common events like Screen calls, Identify calls, and Track calls. Mappings have two components that make this possible: **Triggers** and an **Action**. | -| Triggers | Enable you to define *when* the corresponding Action fires. As part of a Trigger, you can use condition-based filters to narrow the scope of the Trigger.

Self-service users can add a maximum of two conditions per Trigger. | +| Triggers | Enable you to define *when* the corresponding Action fires. As part of a Trigger, you can use condition-based filters to narrow the scope of the Trigger.

Self-service users can add a maximum of two conditions per Trigger.

Triggers do not currently support matching on event fields containing ‘.$’ or ‘.$.’, which reference an array type. + | | Actions | Determine the information sent to the destination. In the Configure action section, you map the fields that come from your source, to fields that the destination expects to find. Fields on the destination side depend on the type of action selected. | For example, in the Amplitude (Actions) destination, you define your API and Secret keys in the destination's global settings. Then, the provided Page Calls mapping: From 44e7f3c2f1a99ecefc17d13ccf4c5fb01745cbba Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Wed, 16 Oct 2024 10:03:28 -0400 Subject: [PATCH 43/56] first draft --- .../configure-consent-management.md | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/src/privacy/consent-management/configure-consent-management.md b/src/privacy/consent-management/configure-consent-management.md index e47c607d82..12ea33b85a 100644 --- a/src/privacy/consent-management/configure-consent-management.md +++ b/src/privacy/consent-management/configure-consent-management.md @@ -43,15 +43,13 @@ Once you've created consent categories in the Segment app, you need to integrate - Reads the end user consent preference from your CMP and includes the [consent object](/docs/privacy/consent-management/consent-in-segment-connections/#consent-object) in every event - If using Unify and Engage, generates the [Segment Consent Preference Updated](/docs/privacy/consent-management/consent-in-unify/#segment-consent-preference-updated-event) event every time a user provides or updates their consent preferences with their anonymousId and userId -Segment provides a OneTrust wrapper for the following web and mobile sources: -- **Analytics.js**: Please follow the instructions from the README in the [@segmentio/analytics-consent-wrapper-onetrust](https://github.com/segmentio/analytics-next/tree/master/packages/consent/consent-wrapper-onetrust){:target="_blank"} repository. For more information about Segment's Analytics.js OneTrust wrapper, see the [Analytics.js OneTrust Wrapper](/docs/privacy/consent-management/onetrust-wrapper) documentation. You should also navigate to your Analytics.js source in the Segment app, select **Settings > Analytics.js**, and enable **Destination Filters** before enabling your OneTrust wrapper. -- **Kotlin**: Please follow the instructions from the README in the [@segment-integrations/analytics-kotlin-consent](https://github.com/segment-integrations/analytics-kotlin-consent/blob/main/README.md#getting-started){:target="_blank"} repository. -- **Swift**: Please follow the instructions from the README in the [@segment-integrations/analytics-swift-consent](https://github.com/segment-integrations/analytics-swift-consent#segment-consent-management){:target="_blank"} repository. -- **React Native**: Please follow the instructions from the README in the [@segmentio/analytics-react-native](https://github.com/segmentio/analytics-react-native/tree/master/packages/plugins/plugin-onetrust){:target="_blank"} repository. +Segment supports the following wrappers: -Ketch provides a web integration for their Consent & Preference Management product. For more information, see the Ketch [Segment Tag Management Automation](https://docs.ketch.com/ketch/docs/segment-tag-management-automation){:target="_blank"} documentation. - -TrustArc provides a web integration for their Cookie Consent Manager. For more information, see the [TrustArc Segment Wrapper](https://github.com/trustarc/trustarc-segment-wrapper){:target="_blank"} documentation. +| Consent Management Platform | Supported web libraries | Supported mobile libraries | Contact | +| --------------------------- | -------------------------- | ---------------------------- | ------------- | +| OneTrust |![supported](/docs/images/supported.svg) [Analytics.js](https://github.com/segmentio/analytics-next/tree/master/packages/consent/consent-wrapper-onetrust){:target="_blank"} | ![supported](/docs/images/supported.svg) [Kotlin](https://github.com/segment-integrations/analytics-kotlin-consent/blob/main/README.md#getting-started){:target="_blank"}
![supported](/docs/images/supported.svg) [Swift](https://github.com/segment-integrations/analytics-swift-consent#segment-consent-management){:target="_blank"}
![supported](/docs/images/supported.svg) [React Native](https://github.com/segmentio/analytics-react-native/tree/master/packages/plugins/plugin-onetrust){:target="_blank"} | For support and troubleshooting, contact [Segment](mailto:friends@segment.com){:target="_blank"}. | +| Ketch | ![supported](/docs/images/supported.svg) [Analytics.js](https://docs.ketch.com/ketch/docs/segment-tag-management-automation){:target="_blank"} | ![unsupported](/docs/images/unsupported.svg) | For support and troubleshooting, contact [Ketch](https://www.ketch.com/contact-us){:target="_blank"}. | +| TrustArc | ![supported](/docs/images/supported.svg) [Analytics.js](https://github.com/trustarc/trustarc-segment-wrapper){:target="_blank"} | ![unsupported](/docs/images/unsupported.svg) | For support and troubleshooting, contact [TrustArc](https://trustarc.com/contact/){:target="_blank"}. | If you'd like to integrate with any other CMP, Segment requires you to build your own wrapper or use any mechanism provided it meets the above requirements of data and event generation. To get started building your own wrapper, follow the instructions in the [@segment/analytics-consent-tools](https://github.com/segmentio/analytics-next/tree/master/packages/consent/consent-tools){:target="_blank"} repository. From f45cb43dfb8a9288cf24591fd76e7f59caab87c5 Mon Sep 17 00:00:00 2001 From: prigiattiperrut <47340158+prigiattiperrut@users.noreply.github.com> Date: Wed, 16 Oct 2024 16:27:38 +0100 Subject: [PATCH 44/56] Update custom-domain.md --- src/connections/sources/custom-domain.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/connections/sources/custom-domain.md b/src/connections/sources/custom-domain.md index f87650c2af..b0d6a32a4c 100644 --- a/src/connections/sources/custom-domain.md +++ b/src/connections/sources/custom-domain.md @@ -51,7 +51,8 @@ To configure Custom Domain: - **Domain Name**: Enter the subdomain that Segment should use for event request tracking. - **Additional Domain Name**: If applicable, add an additional subdomain. This field is optional. - **Source names**: Select the sources you would like to use for Custom Domain. For a list of all sources that support Custom Domain, see [Supported sources](#supported-sources). - - **Is the domain name enabled for Content Policy**: Select either Yes or No. You are not required to create a Content Policy prior to requesting Custom Domain. + - **Is the domain name enabled for Content Policy**: Select either Yes or No. You are not required to create a Content Policy prior to requesting Custom Domain. If you have a Content Security Policy (CSP) enabled, you must add the new subdomains provided by Segment to your CSP once the Custom Domain feature is enabled. This ensures that the subdomains are not blocked by your CSP when loading Segment. + - **Description**: Enter an optional description for your service request. If you are requesting Custom Domain for multiple workspaces, enter any additional workspace slugs and source names into this field. 4. Segment provides you with a list of nameservers you should add to your DNS. Once you receive the nameservers from Segment, update your DNS. 5. After you've updated your DNS, Segment verifies that you've made all required updates and then provides you with two custom domains, one for the Tracking API and a second for your CDN. From a907f7e8ef698b91620de7fc793ab3e4d0c457a1 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Wed, 16 Oct 2024 11:44:34 -0400 Subject: [PATCH 45/56] Update src/connections/sources/custom-domain.md --- src/connections/sources/custom-domain.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/sources/custom-domain.md b/src/connections/sources/custom-domain.md index b0d6a32a4c..a8a9f570b5 100644 --- a/src/connections/sources/custom-domain.md +++ b/src/connections/sources/custom-domain.md @@ -51,7 +51,7 @@ To configure Custom Domain: - **Domain Name**: Enter the subdomain that Segment should use for event request tracking. - **Additional Domain Name**: If applicable, add an additional subdomain. This field is optional. - **Source names**: Select the sources you would like to use for Custom Domain. For a list of all sources that support Custom Domain, see [Supported sources](#supported-sources). - - **Is the domain name enabled for Content Policy**: Select either Yes or No. You are not required to create a Content Policy prior to requesting Custom Domain. If you have a Content Security Policy (CSP) enabled, you must add the new subdomains provided by Segment to your CSP once the Custom Domain feature is enabled. This ensures that the subdomains are not blocked by your CSP when loading Segment. + - **Is the domain name enabled for Content Policy**: Select either Yes or No. You are not required to create a Content Policy prior to requesting Custom Domain. If you've enabled a Content Security Policy (CSP), you must add the new subdomains provided by Segment to your CSP once you've enabled the Custom Domain feature. This ensures that the CSP does not block the subdomains when you load Segment. - **Description**: Enter an optional description for your service request. If you are requesting Custom Domain for multiple workspaces, enter any additional workspace slugs and source names into this field. 4. Segment provides you with a list of nameservers you should add to your DNS. Once you receive the nameservers from Segment, update your DNS. From 12a2c3c441c1a35799b773cfa12a8410d58bce43 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Wed, 16 Oct 2024 12:05:57 -0400 Subject: [PATCH 46/56] [netlify-build] --- .../configure-consent-management.md | 21 ++++++++++++------- 1 file changed, 14 insertions(+), 7 deletions(-) diff --git a/src/privacy/consent-management/configure-consent-management.md b/src/privacy/consent-management/configure-consent-management.md index 12ea33b85a..d7d15ebacd 100644 --- a/src/privacy/consent-management/configure-consent-management.md +++ b/src/privacy/consent-management/configure-consent-management.md @@ -39,19 +39,26 @@ Before you can configure consent in Segment, take the following steps: ## Step 2: Integrating your CMP with Segment -Once you've created consent categories in the Segment app, you need to integrate your CMP with Segment. Segment recommends using a CMP wrapper, but you can use any solution provided it meets the following criteria: -- Reads the end user consent preference from your CMP and includes the [consent object](/docs/privacy/consent-management/consent-in-segment-connections/#consent-object) in every event -- If using Unify and Engage, generates the [Segment Consent Preference Updated](/docs/privacy/consent-management/consent-in-unify/#segment-consent-preference-updated-event) event every time a user provides or updates their consent preferences with their anonymousId and userId +Once you've created consent categories in the Segment app, you need to integrate your CMP with Segment. -Segment supports the following wrappers: +Segment supports the following CMPs: | Consent Management Platform | Supported web libraries | Supported mobile libraries | Contact | | --------------------------- | -------------------------- | ---------------------------- | ------------- | -| OneTrust |![supported](/docs/images/supported.svg) [Analytics.js](https://github.com/segmentio/analytics-next/tree/master/packages/consent/consent-wrapper-onetrust){:target="_blank"} | ![supported](/docs/images/supported.svg) [Kotlin](https://github.com/segment-integrations/analytics-kotlin-consent/blob/main/README.md#getting-started){:target="_blank"}
![supported](/docs/images/supported.svg) [Swift](https://github.com/segment-integrations/analytics-swift-consent#segment-consent-management){:target="_blank"}
![supported](/docs/images/supported.svg) [React Native](https://github.com/segmentio/analytics-react-native/tree/master/packages/plugins/plugin-onetrust){:target="_blank"} | For support and troubleshooting, contact [Segment](mailto:friends@segment.com){:target="_blank"}. | -| Ketch | ![supported](/docs/images/supported.svg) [Analytics.js](https://docs.ketch.com/ketch/docs/segment-tag-management-automation){:target="_blank"} | ![unsupported](/docs/images/unsupported.svg) | For support and troubleshooting, contact [Ketch](https://www.ketch.com/contact-us){:target="_blank"}. | +| OneTrust |![supported](/docs/images/supported.svg) [Analytics.js](https://github.com/segmentio/analytics-next/tree/master/packages/consent/consent-wrapper-onetrust){:target="_blank"}* | ![supported](/docs/images/supported.svg) [Kotlin](https://github.com/segment-integrations/analytics-kotlin-consent/blob/main/README.md#getting-started){:target="_blank"}
![supported](/docs/images/supported.svg) [Swift](https://github.com/segment-integrations/analytics-swift-consent#segment-consent-management){:target="_blank"}
![supported](/docs/images/supported.svg) [React Native](https://github.com/segmentio/analytics-react-native/tree/master/packages/plugins/plugin-onetrust){:target="_blank"} | For support and troubleshooting, contact [Segment](mailto:friends@segment.com){:target="_blank"}. | | TrustArc | ![supported](/docs/images/supported.svg) [Analytics.js](https://github.com/trustarc/trustarc-segment-wrapper){:target="_blank"} | ![unsupported](/docs/images/unsupported.svg) | For support and troubleshooting, contact [TrustArc](https://trustarc.com/contact/){:target="_blank"}. | +| Ketch | ![supported](/docs/images/supported.svg) [Analytics.js](https://docs.ketch.com/ketch/docs/segment-tag-management-automation){:target="_blank"} | ![unsupported](/docs/images/unsupported.svg) | For support and troubleshooting, contact [Ketch](https://www.ketch.com/contact-us){:target="_blank"}. | + +*_If you send data to device-mode destinations connected to your Analytics.js source, you must navigate to your Analytics.js source in the Segment app, select **Settings > Analytics.js**, and enable Destination Filters._ + +> success "" +> For more information about Segment’s Analytics.js OneTrust wrapper, see the [Analytics.js OneTrust Wrapper](/docs/privacy/consent-management/onetrust-wrapper/) documentation. + +If you'd like to integrate with any other CMP, Segment requires you to build your own wrapper or use any mechanism provided it meets the following requirements for data and event generation: + - Reads the end user consent preference from your CMP and includes the [consent object](/docs/privacy/consent-management/consent-in-segment-connections/#consent-object) in every event + - If using Unify and Engage, generates the [Segment Consent Preference Updated](/docs/privacy/consent-management/consent-in-unify/#segment-consent-preference-updated-event) event every time a user provides or updates their consent preferences with their anonymousId and userId -If you'd like to integrate with any other CMP, Segment requires you to build your own wrapper or use any mechanism provided it meets the above requirements of data and event generation. To get started building your own wrapper, follow the instructions in the [@segment/analytics-consent-tools](https://github.com/segmentio/analytics-next/tree/master/packages/consent/consent-tools){:target="_blank"} repository. +To get started building your own wrapper, follow the instructions in the [@segment/analytics-consent-tools](https://github.com/segmentio/analytics-next/tree/master/packages/consent/consent-tools){:target="_blank"} repository. > warning "Consent Management is not backwards compatible with Segment's legacy iOS and Android libraries" > If you are using one of Segment's legacy mobile libraries (iOS or Android,) you will need to upgrade to [Swift](/docs/connections/sources/catalog/libraries/mobile/apple/migration/) or [Kotlin](/docs/connections/sources/catalog/libraries/mobile/kotlin-android/migration/) before using Consent Management. From 33498d777da5968f8728ab3efe0f23b07ef50169 Mon Sep 17 00:00:00 2001 From: stayseesong <83784848+stayseesong@users.noreply.github.com> Date: Wed, 16 Oct 2024 11:32:29 -0700 Subject: [PATCH 47/56] Update src/connections/destinations/actions.md --- src/connections/destinations/actions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/actions.md b/src/connections/destinations/actions.md index 375228e66c..b3e858ce86 100644 --- a/src/connections/destinations/actions.md +++ b/src/connections/destinations/actions.md @@ -38,7 +38,7 @@ A Destination Action contains a hierarchy of components, that work together to e | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Global Settings | Define authentication and connection-related information like API and Secret keys. | | Mappings | Handle the individual calls to the destination. In them, you define what type of call you want to make to the destination, and what Triggers that call. Individual Destination Actions may come enabled with some predefined mappings to handle common events like Screen calls, Identify calls, and Track calls. Mappings have two components that make this possible: **Triggers** and an **Action**. | -| Triggers | Enable you to define *when* the corresponding Action fires. As part of a Trigger, you can use condition-based filters to narrow the scope of the Trigger.

Self-service users can add a maximum of two conditions per Trigger.

Triggers do not currently support matching on event fields containing ‘.$’ or ‘.$.’, which reference an array type. +| Triggers | Enable you to define *when* the corresponding Action fires. As part of a Trigger, you can use condition-based filters to narrow the scope of the Trigger.

Self-service users can add a maximum of two conditions per Trigger. Triggers don't support matching on event fields containing ‘.$’ or ‘.$.’, which reference an array type. | | Actions | Determine the information sent to the destination. In the Configure action section, you map the fields that come from your source, to fields that the destination expects to find. Fields on the destination side depend on the type of action selected. | From c9d14095036aa49323e4c44faff0b3f939b70a7f Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Wed, 16 Oct 2024 14:33:06 -0400 Subject: [PATCH 48/56] Apply suggestions from code review --- src/protocols/faq.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/protocols/faq.md b/src/protocols/faq.md index e3925f54a9..d91b5cdb6e 100644 --- a/src/protocols/faq.md +++ b/src/protocols/faq.md @@ -209,6 +209,6 @@ Transformations are but one tool among many to help you improve data quality. Se Transformations are not applied to events sent through the [Event Tester](/docs/connections/test-connections/). The Event Tester operates independently from the Segment pipeline, focusing solely on testing specific connections to a destination. For a transformation to take effect, the event must be processed through the Segment pipeline. -### Why am I getting the error "rules must contain less than or equal to 200 items" when using the Public API and can this limit be increased? +### Why am I getting the error "rules must contain less than or equal to 200 items" when using the Public API? Can I increase this limit? -This error occurs because there is a limit of 200 rules per API update, which is by design to ensure stable API performance. Unfortunately, increasing this limit isn’t possible at the moment. To work around this, split your update into smaller batches with 200 or fewer rules each. +This error occurs because there is a limit of 200 rules per API update. This restriction is by design to ensure stable API performance. Segment is not able to increase this limit on your behalf. To work around this, split your update into smaller batches, each with 200 or fewer rules. From 33421a2c3c184bd9c2b4bd4e9c731725aeaea703 Mon Sep 17 00:00:00 2001 From: stayseesong <83784848+stayseesong@users.noreply.github.com> Date: Wed, 16 Oct 2024 11:33:45 -0700 Subject: [PATCH 49/56] Update src/connections/destinations/actions.md --- src/connections/destinations/actions.md | 1 - 1 file changed, 1 deletion(-) diff --git a/src/connections/destinations/actions.md b/src/connections/destinations/actions.md index b3e858ce86..351b43d955 100644 --- a/src/connections/destinations/actions.md +++ b/src/connections/destinations/actions.md @@ -39,7 +39,6 @@ A Destination Action contains a hierarchy of components, that work together to e | Global Settings | Define authentication and connection-related information like API and Secret keys. | | Mappings | Handle the individual calls to the destination. In them, you define what type of call you want to make to the destination, and what Triggers that call. Individual Destination Actions may come enabled with some predefined mappings to handle common events like Screen calls, Identify calls, and Track calls. Mappings have two components that make this possible: **Triggers** and an **Action**. | | Triggers | Enable you to define *when* the corresponding Action fires. As part of a Trigger, you can use condition-based filters to narrow the scope of the Trigger.

Self-service users can add a maximum of two conditions per Trigger. Triggers don't support matching on event fields containing ‘.$’ or ‘.$.’, which reference an array type. - | | Actions | Determine the information sent to the destination. In the Configure action section, you map the fields that come from your source, to fields that the destination expects to find. Fields on the destination side depend on the type of action selected. | For example, in the Amplitude (Actions) destination, you define your API and Secret keys in the destination's global settings. Then, the provided Page Calls mapping: From 87eea7c791beaa693904858ff573c45c0796838e Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Wed, 16 Oct 2024 14:34:53 -0400 Subject: [PATCH 50/56] Apply suggestions from code review --- .../destinations/catalog/actions-braze-web/index.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/src/connections/destinations/catalog/actions-braze-web/index.md b/src/connections/destinations/catalog/actions-braze-web/index.md index f4bb8aeba7..648a2d7f07 100644 --- a/src/connections/destinations/catalog/actions-braze-web/index.md +++ b/src/connections/destinations/catalog/actions-braze-web/index.md @@ -176,10 +176,12 @@ Keep the following in mind if you plan to move to Braze (Actions) from the class ## FAQ -### How Debounce Middleware works? +### How does the Debounce Middleware Action work? -The [Debounce Middleware](/docs/connections/destinations/catalog/actions-braze-web/#debounce-middleware) action is unique and behaves differently from the other actions. Debounce Middleware logic is executed at the source-level: +The following [Debounce Middleware](/docs/connections/destinations/catalog/actions-braze-web/#debounce-middleware) logic is executed at the source-level: -- When an Identify call is fired on a website, we will first cache and compare the user traits. If the user traits object differs from what has been cached previously, the data will be passed on to the destination flow (Destination Filters → Insert Functions → Destination Mappings). +When an Identify call is fired on a website, Segment first caches and compares the user traits object. -- Otherwise, if user traits are the same as what's cached, we assume that that data was already sent to Braze and a new request is not made to their system. +-If the user traits differ from what was previously cached, the data flows through destination filters, insert functions, and then through destination mappings. + +- If user traits are the same as what's cached, Segment assumes that that data was already sent to Braze and a does not make a new request to Braze. From 8f231be64fa17cfc05b24ee116c2c739324caef8 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Wed, 16 Oct 2024 14:35:34 -0400 Subject: [PATCH 51/56] Apply suggestions from code review --- .../destinations/catalog/actions-braze-web/index.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/connections/destinations/catalog/actions-braze-web/index.md b/src/connections/destinations/catalog/actions-braze-web/index.md index 648a2d7f07..d5a8d40aca 100644 --- a/src/connections/destinations/catalog/actions-braze-web/index.md +++ b/src/connections/destinations/catalog/actions-braze-web/index.md @@ -182,6 +182,5 @@ The following [Debounce Middleware](/docs/connections/destinations/catalog/actio When an Identify call is fired on a website, Segment first caches and compares the user traits object. --If the user traits differ from what was previously cached, the data flows through destination filters, insert functions, and then through destination mappings. - +- If the user traits differ from what was previously cached, the data flows through destination filters, insert functions, and then through destination mappings. - If user traits are the same as what's cached, Segment assumes that that data was already sent to Braze and a does not make a new request to Braze. From 280b7ef9805dac0beacb37bc899b5aba1be7ce0e Mon Sep 17 00:00:00 2001 From: stayseesong Date: Wed, 16 Oct 2024 12:45:58 -0700 Subject: [PATCH 52/56] edits --- src/connections/destinations/actions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/connections/destinations/actions.md b/src/connections/destinations/actions.md index 351b43d955..86cf93b6af 100644 --- a/src/connections/destinations/actions.md +++ b/src/connections/destinations/actions.md @@ -38,8 +38,8 @@ A Destination Action contains a hierarchy of components, that work together to e | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Global Settings | Define authentication and connection-related information like API and Secret keys. | | Mappings | Handle the individual calls to the destination. In them, you define what type of call you want to make to the destination, and what Triggers that call. Individual Destination Actions may come enabled with some predefined mappings to handle common events like Screen calls, Identify calls, and Track calls. Mappings have two components that make this possible: **Triggers** and an **Action**. | -| Triggers | Enable you to define *when* the corresponding Action fires. As part of a Trigger, you can use condition-based filters to narrow the scope of the Trigger.

Self-service users can add a maximum of two conditions per Trigger. Triggers don't support matching on event fields containing ‘.$’ or ‘.$.’, which reference an array type. -| Actions | Determine the information sent to the destination. In the Configure action section, you map the fields that come from your source, to fields that the destination expects to find. Fields on the destination side depend on the type of action selected. | +| Triggers | Enable you to define *when* the corresponding Action fires. As part of a Trigger, you can use condition-based filters to narrow the scope of the Trigger.

Self-service users can add a maximum of two conditions per Trigger. Triggers don't support matching on event fields containing `.$` or `.$.`, which reference an array type. | +| Actions | Determine the information sent to the destination. In the Configure action section, you map the fields that come from your source, to fields that the destination expects to find. Fields on the destination side depend on the type of action selected. | For example, in the Amplitude (Actions) destination, you define your API and Secret keys in the destination's global settings. Then, the provided Page Calls mapping: From ca51ec6a5313d77f12ca59f0b24b7a779b57a20e Mon Sep 17 00:00:00 2001 From: stayseesong Date: Wed, 16 Oct 2024 12:47:24 -0700 Subject: [PATCH 53/56] edits --- src/connections/destinations/actions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/actions.md b/src/connections/destinations/actions.md index 86cf93b6af..7f76703047 100644 --- a/src/connections/destinations/actions.md +++ b/src/connections/destinations/actions.md @@ -38,7 +38,7 @@ A Destination Action contains a hierarchy of components, that work together to e | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Global Settings | Define authentication and connection-related information like API and Secret keys. | | Mappings | Handle the individual calls to the destination. In them, you define what type of call you want to make to the destination, and what Triggers that call. Individual Destination Actions may come enabled with some predefined mappings to handle common events like Screen calls, Identify calls, and Track calls. Mappings have two components that make this possible: **Triggers** and an **Action**. | -| Triggers | Enable you to define *when* the corresponding Action fires. As part of a Trigger, you can use condition-based filters to narrow the scope of the Trigger.

Self-service users can add a maximum of two conditions per Trigger. Triggers don't support matching on event fields containing `.$` or `.$.`, which reference an array type. | +| Triggers | Enable you to define *when* the corresponding Action fires. As part of a Trigger, you can use condition-based filters to narrow the scope of the Trigger. Triggers don't support matching on event fields containing `.$` or `.$.`, which reference an array type.

Self-service users can add a maximum of two conditions per Trigger. | | Actions | Determine the information sent to the destination. In the Configure action section, you map the fields that come from your source, to fields that the destination expects to find. Fields on the destination side depend on the type of action selected. | For example, in the Amplitude (Actions) destination, you define your API and Secret keys in the destination's global settings. Then, the provided Page Calls mapping: From 64a3b65bee9ba9af752dfe947a0fa1c3b9d2dc3c Mon Sep 17 00:00:00 2001 From: Wally Tung Date: Thu, 17 Oct 2024 11:40:46 -0500 Subject: [PATCH 54/56] add event type --- .../sources/catalog/libraries/server/http-api/index.md | 1 + 1 file changed, 1 insertion(+) diff --git a/src/connections/sources/catalog/libraries/server/http-api/index.md b/src/connections/sources/catalog/libraries/server/http-api/index.md index fa6cca8ceb..15540f93f3 100644 --- a/src/connections/sources/catalog/libraries/server/http-api/index.md +++ b/src/connections/sources/catalog/libraries/server/http-api/index.md @@ -64,6 +64,7 @@ For example, to use the access token in the HTTP API Source, use `access_token` "email": "test@example.org", "messageId": "58524f3a-3b76-4eac-aa97-d88bccdf4f77", "userId": "123", + "type": "track", "writeKey": "DmBXIN4JnwqBnTqXccTF0wBnLXNQmFtk" } ``` From ac870218d9c8fa258536045917729f2529e65bcd Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 17 Oct 2024 12:41:14 -0400 Subject: [PATCH 55/56] Update destination-filters.md --- src/connections/destinations/destination-filters.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/destination-filters.md b/src/connections/destinations/destination-filters.md index 7f4a1ce5a3..61c30c7397 100644 --- a/src/connections/destinations/destination-filters.md +++ b/src/connections/destinations/destination-filters.md @@ -172,7 +172,7 @@ There are certain destinations to which you may not want to send the `userId`. T ## Filter conditional operators * `contains`: checks whether the field's value includes the provided substring -* `glob matches`: case sensitive, checks whether the value matches provided string +* `glob matches`: case sensitive, can accept wildcard characters, checks whether the value matches provided string * `is (number)`: checks whether the value is exactly the provided integer * `is (string)`: checks whether the value is exactly the provided string * `is false`: checks whether the value is type boolean and is `false` From 6cea365dc45f5833e4a3115950ab38c3fd18b353 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 17 Oct 2024 13:42:24 -0400 Subject: [PATCH 56/56] catalog --- src/_data/catalog/destination_categories.yml | 2 +- src/_data/catalog/destinations.yml | 3202 +++++++++++++++++- src/_data/catalog/destinations_private.yml | 2 +- src/_data/catalog/source_categories.yml | 2 +- src/_data/catalog/sources.yml | 2 +- 5 files changed, 3132 insertions(+), 78 deletions(-) diff --git a/src/_data/catalog/destination_categories.yml b/src/_data/catalog/destination_categories.yml index 919b6c895e..56c3981edb 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-15 +# destination categories last updated 2024-10-17 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 3a09377150..108a4a8b78 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-15 +# destination data last updated 2024-10-17 items: - id: 637e8d185e2dec264895ea89 display_name: 1Flow @@ -72317,7 +72317,7 @@ items: hidden: false defaultTrigger: type = "identify" fields: - - id: vAcobjNRnz7oxJNDtGrohV + - id: 68FBid2rPi3n7Cpjo4DG2x sortOrder: 0 fieldKey: email label: Email @@ -72333,7 +72333,7 @@ items: choices: null dynamic: false allowNull: false - - id: gb3YoK8j6e1A3VWwcKdwjd + - id: vZ23qZvLcN5qFJZbS9jWB9 sortOrder: 1 fieldKey: enable_batching label: Batch Data to Klaviyo @@ -72345,7 +72345,7 @@ items: choices: null dynamic: false allowNull: false - - id: icQU9B3rcCWA2LNfAt1KPA + - id: 7gRiZWQ4jf4LjiM8gqUHCZ sortOrder: 2 fieldKey: phone_number label: Phone Number @@ -72362,8 +72362,517 @@ items: choices: null dynamic: false allowNull: false - - id: cNYDe7gc1veHiWU3XD6Pe7 + - id: 97WYMaJHBi6t3SoZsm7iVZ sortOrder: 3 + fieldKey: country_code + label: Country Code + type: STRING + description: >- + Country Code in ISO 3166-1 alpha-2 format. If provided, this will be + used to validate and automatically format Phone Number field in E.164 + format accepted by Klaviyo. + placeholder: '' + required: false + multiple: false + choices: + - label: AD - Andorra + value: AD + - label: AE - United Arab Emirates + value: AE + - label: AF - Afghanistan + value: AF + - label: AG - Antigua and Barbuda + value: AG + - label: AI - Anguilla + value: AI + - label: AL - Albania + value: AL + - label: AM - Armenia + value: AM + - label: AO - Angola + value: AO + - label: AQ - Antarctica + value: AQ + - label: AR - Argentina + value: AR + - label: AS - American Samoa + value: AS + - label: AT - Austria + value: AT + - label: AU - Australia + value: AU + - label: AW - Aruba + value: AW + - label: AX - Åland Islands + value: AX + - label: AZ - Azerbaijan + value: AZ + - label: BA - Bosnia and Herzegovina + value: BA + - label: BB - Barbados + value: BB + - label: BD - Bangladesh + value: BD + - label: BE - Belgium + value: BE + - label: BF - Burkina Faso + value: BF + - label: BG - Bulgaria + value: BG + - label: BH - Bahrain + value: BH + - label: BI - Burundi + value: BI + - label: BJ - Benin + value: BJ + - label: BL - Saint Barthélemy + value: BL + - label: BM - Bermuda + value: BM + - label: BN - Brunei Darussalam + value: BN + - label: BO - Bolivia (Plurinational State of) + value: BO + - label: BQ - Bonaire, Sint Eustatius and Saba + value: BQ + - label: BR - Brazil + value: BR + - label: BS - Bahamas + value: BS + - label: BT - Bhutan + value: BT + - label: BV - Bouvet Island + value: BV + - label: BW - Botswana + value: BW + - label: BY - Belarus + value: BY + - label: BZ - Belize + value: BZ + - label: CA - Canada + value: CA + - label: CC - Cocos (Keeling) Islands + value: CC + - label: CD - Congo, Democratic Republic of the + value: CD + - label: CF - Central African Republic + value: CF + - label: CG - Congo + value: CG + - label: CH - Switzerland + value: CH + - label: CI - Côte d'Ivoire + value: CI + - label: CK - Cook Islands + value: CK + - label: CL - Chile + value: CL + - label: CM - Cameroon + value: CM + - label: CN - China + value: CN + - label: CO - Colombia + value: CO + - label: CR - Costa Rica + value: CR + - label: CU - Cuba + value: CU + - label: CV - Cabo Verde + value: CV + - label: CW - Curaçao + value: CW + - label: CX - Christmas Island + value: CX + - label: CY - Cyprus + value: CY + - label: CZ - Czechia + value: CZ + - label: DE - Germany + value: DE + - label: DJ - Djibouti + value: DJ + - label: DK - Denmark + value: DK + - label: DM - Dominica + value: DM + - label: DO - Dominican Republic + value: DO + - label: DZ - Algeria + value: DZ + - label: EC - Ecuador + value: EC + - label: EE - Estonia + value: EE + - label: EG - Egypt + value: EG + - label: EH - Western Sahara + value: EH + - label: ER - Eritrea + value: ER + - label: ES - Spain + value: ES + - label: ET - Ethiopia + value: ET + - label: FI - Finland + value: FI + - label: FJ - Fiji + value: FJ + - label: FK - Falkland Islands (Malvinas) + value: FK + - label: FM - Micronesia (Federated States of) + value: FM + - label: FO - Faroe Islands + value: FO + - label: FR - France + value: FR + - label: GA - Gabon + value: GA + - label: GB - United Kingdom of Great Britain and Northern Ireland + value: GB + - label: GD - Grenada + value: GD + - label: GE - Georgia + value: GE + - label: GF - French Guiana + value: GF + - label: GG - Guernsey + value: GG + - label: GH - Ghana + value: GH + - label: GI - Gibraltar + value: GI + - label: GL - Greenland + value: GL + - label: GM - Gambia + value: GM + - label: GN - Guinea + value: GN + - label: GP - Guadeloupe + value: GP + - label: GQ - Equatorial Guinea + value: GQ + - label: GR - Greece + value: GR + - label: GT - Guatemala + value: GT + - label: GU - Guam + value: GU + - label: GW - Guinea-Bissau + value: GW + - label: GY - Guyana + value: GY + - label: HK - Hong Kong + value: HK + - label: HM - Heard Island and McDonald Islands + value: HM + - label: HN - Honduras + value: HN + - label: HR - Croatia + value: HR + - label: HT - Haiti + value: HT + - label: HU - Hungary + value: HU + - label: ID - Indonesia + value: ID + - label: IE - Ireland + value: IE + - label: IL - Israel + value: IL + - label: IM - Isle of Man + value: IM + - label: IN - India + value: IN + - label: IO - British Indian Ocean Territory + value: IO + - label: IQ - Iraq + value: IQ + - label: IR - Iran (Islamic Republic of) + value: IR + - label: IS - Iceland + value: IS + - label: IT - Italy + value: IT + - label: JE - Jersey + value: JE + - label: JM - Jamaica + value: JM + - label: JO - Jordan + value: JO + - label: JP - Japan + value: JP + - label: KE - Kenya + value: KE + - label: KG - Kyrgyzstan + value: KG + - label: KH - Cambodia + value: KH + - label: KI - Kiribati + value: KI + - label: KM - Comoros + value: KM + - label: KN - Saint Kitts and Nevis + value: KN + - label: KP - Korea (Democratic People's Republic of) + value: KP + - label: KR - Korea, Republic of + value: KR + - label: KW - Kuwait + value: KW + - label: KY - Cayman Islands + value: KY + - label: KZ - Kazakhstan + value: KZ + - label: LA - Lao People's Democratic Republic + value: LA + - label: LB - Lebanon + value: LB + - label: LC - Saint Lucia + value: LC + - label: LI - Liechtenstein + value: LI + - label: LK - Sri Lanka + value: LK + - label: LR - Liberia + value: LR + - label: LS - Lesotho + value: LS + - label: LT - Lithuania + value: LT + - label: LU - Luxembourg + value: LU + - label: LV - Latvia + value: LV + - label: LY - Libya + value: LY + - label: MA - Morocco + value: MA + - label: MC - Monaco + value: MC + - label: MD - Moldova (Republic of) + value: MD + - label: ME - Montenegro + value: ME + - label: MF - Saint Martin (French part) + value: MF + - label: MG - Madagascar + value: MG + - label: MH - Marshall Islands + value: MH + - label: MK - North Macedonia + value: MK + - label: ML - Mali + value: ML + - label: MM - Myanmar + value: MM + - label: MN - Mongolia + value: MN + - label: MO - Macao + value: MO + - label: MP - Northern Mariana Islands + value: MP + - label: MQ - Martinique + value: MQ + - label: MR - Mauritania + value: MR + - label: MS - Montserrat + value: MS + - label: MT - Malta + value: MT + - label: MU - Mauritius + value: MU + - label: MV - Maldives + value: MV + - label: MW - Malawi + value: MW + - label: MX - Mexico + value: MX + - label: MY - Malaysia + value: MY + - label: MZ - Mozambique + value: MZ + - label: NA - Namibia + value: NA + - label: NC - New Caledonia + value: NC + - label: NE - Niger + value: NE + - label: NF - Norfolk Island + value: NF + - label: NG - Nigeria + value: NG + - label: NI - Nicaragua + value: NI + - label: NL - Netherlands + value: NL + - label: NO - Norway + value: 'NO' + - label: NP - Nepal + value: NP + - label: NR - Nauru + value: NR + - label: NU - Niue + value: NU + - label: NZ - New Zealand + value: NZ + - label: OM - Oman + value: OM + - label: PA - Panama + value: PA + - label: PE - Peru + value: PE + - label: PF - French Polynesia + value: PF + - label: PG - Papua New Guinea + value: PG + - label: PH - Philippines + value: PH + - label: PK - Pakistan + value: PK + - label: PL - Poland + value: PL + - label: PM - Saint Pierre and Miquelon + value: PM + - label: PN - Pitcairn + value: PN + - label: PR - Puerto Rico + value: PR + - label: PT - Portugal + value: PT + - label: PW - Palau + value: PW + - label: PY - Paraguay + value: PY + - label: QA - Qatar + value: QA + - label: RE - Réunion + value: RE + - label: RO - Romania + value: RO + - label: RS - Serbia + value: RS + - label: RU - Russian Federation + value: RU + - label: RW - Rwanda + value: RW + - label: SA - Saudi Arabia + value: SA + - label: SB - Solomon Islands + value: SB + - label: SC - Seychelles + value: SC + - label: SD - Sudan + value: SD + - label: SE - Sweden + value: SE + - label: SG - Singapore + value: SG + - label: SH - Saint Helena + value: SH + - label: SI - Slovenia + value: SI + - label: SJ - Svalbard and Jan Mayen + value: SJ + - label: SK - Slovakia + value: SK + - label: SL - Sierra Leone + value: SL + - label: SM - San Marino + value: SM + - label: SN - Senegal + value: SN + - label: SO - Somalia + value: SO + - label: SR - Suriname + value: SR + - label: SS - South Sudan + value: SS + - label: ST - São Tomé and Príncipe + value: ST + - label: SV - El Salvador + value: SV + - label: SX - Sint Maarten (Dutch part) + value: SX + - label: SY - Syrian Arab Republic + value: SY + - label: SZ - Eswatini + value: SZ + - label: TC - Turks and Caicos Islands + value: TC + - label: TD - Chad + value: TD + - label: TF - French Southern Territories + value: TF + - label: TG - Togo + value: TG + - label: TH - Thailand + value: TH + - label: TJ - Tajikistan + value: TJ + - label: TK - Tokelau + value: TK + - label: TL - Timor-Leste + value: TL + - label: TM - Turkmenistan + value: TM + - label: TN - Tunisia + value: TN + - label: TO - Tonga + value: TO + - label: TR - Turkey + value: TR + - label: TT - Trinidad and Tobago + value: TT + - label: TV - Tuvalu + value: TV + - label: TZ - Tanzania, United Republic of + value: TZ + - label: UA - Ukraine + value: UA + - label: UG - Uganda + value: UG + - label: UM - United States Minor Outlying Islands + value: UM + - label: UN - United Nations + value: UN + - label: US - United States of America + value: US + - label: UY - Uruguay + value: UY + - label: UZ - Uzbekistan + value: UZ + - label: VA - Holy See + value: VA + - label: VC - Saint Vincent and the Grenadines + value: VC + - label: VE - Venezuela (Bolivarian Republic of) + value: VE + - label: VG - Virgin Islands (British) + value: VG + - label: VI - Virgin Islands (U.S.) + value: VI + - label: VN - Viet Nam + value: VN + - label: VU - Vanuatu + value: VU + - label: WF - Wallis and Futuna + value: WF + - label: WS - Samoa + value: WS + - label: YE - Yemen + value: YE + - label: YT - Mayotte + value: YT + - label: ZA - South Africa + value: ZA + - label: ZM - Zambia + value: ZM + - label: ZW - Zimbabwe + value: ZW + dynamic: false + allowNull: false + - id: qA3F3PZMzXf4GGKH6DRzKi + sortOrder: 4 fieldKey: external_id label: External ID type: STRING @@ -72377,8 +72886,8 @@ items: choices: null dynamic: false allowNull: false - - id: 5JbbW8kfgNb5acdHhrnMyA - sortOrder: 4 + - id: kZyY6BYKJWvBdMAYh67jrL + sortOrder: 5 fieldKey: first_name label: First Name type: STRING @@ -72391,8 +72900,8 @@ items: choices: null dynamic: false allowNull: false - - id: qJxZAFRcsF37bxd4H8d96U - sortOrder: 5 + - id: mZRVkqdjRck47YzzD8ghXn + sortOrder: 6 fieldKey: last_name label: Last Name type: STRING @@ -72405,8 +72914,8 @@ items: choices: null dynamic: false allowNull: false - - id: s4pBnyW1DqiYV6ZD7mga1A - sortOrder: 6 + - id: 7Tw3DyF77ahgPvQh3yCSfx + sortOrder: 7 fieldKey: organization label: Organization type: STRING @@ -72421,8 +72930,8 @@ items: choices: null dynamic: false allowNull: false - - id: 66ZN5qf4omT1c7ViWVSeaA - sortOrder: 7 + - id: dtyo3TRL2Qz8McsTTZbwV8 + sortOrder: 8 fieldKey: title label: Title type: STRING @@ -72435,8 +72944,8 @@ items: choices: null dynamic: false allowNull: false - - id: t2GPUftXBGxYPwB3MMPsjJ - sortOrder: 8 + - id: 6PX89LVpJzJjJa4bEggJtt + sortOrder: 9 fieldKey: image label: Image type: STRING @@ -72449,8 +72958,8 @@ items: choices: null dynamic: false allowNull: false - - id: tgeYYTRxDREwYgWFVM1xDE - sortOrder: 9 + - id: bi2dxGC1moHZRxAQRrVeWB + sortOrder: 10 fieldKey: location label: Location type: OBJECT @@ -72472,8 +72981,8 @@ items: choices: null dynamic: false allowNull: false - - id: roMCy35iX8ckxWRXBCQ86m - sortOrder: 10 + - id: 5x6n5yCriDx8UFDEx38ngi + sortOrder: 11 fieldKey: properties label: Properties type: OBJECT @@ -72488,8 +72997,8 @@ items: choices: null dynamic: false allowNull: false - - id: mggzhXFkXkRfx4b7SWGMBh - sortOrder: 11 + - id: opW5joGcXYCYqZ5cXbxyZB + sortOrder: 12 fieldKey: list_id label: List type: STRING @@ -72500,8 +73009,8 @@ items: choices: null dynamic: true allowNull: false - - id: fmht3kz5YV1ffQGy4uof2W - sortOrder: 14 + - id: nze9jhdHc6n4XixYVJNDxT + sortOrder: 15 fieldKey: list_identifier label: Existing List ID type: STRING @@ -72514,8 +73023,8 @@ items: choices: null dynamic: true allowNull: false - - id: 6zCU2hQf9nSFQ34FAsv3ku - sortOrder: 15 + - id: 9p2LnkFvC9C31NzHjwoDJt + sortOrder: 16 fieldKey: list_name label: Name of list to create type: STRING @@ -72526,8 +73035,8 @@ items: choices: null dynamic: false allowNull: false - - id: i35QiPXZTBopYP2MvhunjH - sortOrder: 16 + - id: eEdR49Gxbd7sipRSfr5rDh + sortOrder: 17 fieldKey: retlOnMappingSave label: Connect to a static list in Klaviyo type: OBJECT @@ -72549,7 +73058,7 @@ items: hidden: false defaultTrigger: type = "track" fields: - - id: eZLGdFZqmx8CjP6xPCXNDT + - id: smazkEqG6V4GGY4EmmwVop sortOrder: 0 fieldKey: profile label: Profile @@ -72561,7 +73070,7 @@ items: choices: null dynamic: false allowNull: false - - id: qBbgNDSGdKk4XuNWytE5cK + - id: oetdfEmVMavFit4W6Gnxjj sortOrder: 1 fieldKey: properties label: Properties @@ -72575,7 +73084,7 @@ items: choices: null dynamic: false allowNull: false - - id: jUCqzXo6E98nPhZTM2r7J1 + - id: nLFKN2DuhUHNAHPWXmTrkg sortOrder: 2 fieldKey: time label: Time @@ -72594,7 +73103,7 @@ items: choices: null dynamic: false allowNull: false - - id: h7wzs8GMeFSwUkXSmmZJSG + - id: bu7YS48yF93yeLdJH3NT8f sortOrder: 3 fieldKey: value label: Value @@ -72608,7 +73117,7 @@ items: choices: null dynamic: false allowNull: false - - id: tSFnbtQVJzkSe1vXfRrtwk + - id: nWbiHTwXADaGkCn5W6g18Z sortOrder: 4 fieldKey: unique_id label: Unique ID @@ -72628,7 +73137,7 @@ items: choices: null dynamic: false allowNull: false - - id: taQFDAnjpCspZQTk9TfDRS + - id: 34iqZrmcJqbaftv19wxHTx sortOrder: 5 fieldKey: products label: Products @@ -72640,7 +73149,7 @@ items: choices: null dynamic: false allowNull: false - - id: kyZo5HXzDsefRgNaBUSUp7 + - id: p7Fk9F5hzS4K4zcjQ8c6Rp sortOrder: 6 fieldKey: event_name label: Event Name @@ -72661,7 +73170,7 @@ items: hidden: false defaultTrigger: type = "track" fields: - - id: brSapE9JV1KkcMUoXmpBeu + - id: iaTdtgovzkTisZe4j9MMjA sortOrder: 0 fieldKey: profile label: Profile @@ -72673,7 +73182,7 @@ items: choices: null dynamic: false allowNull: false - - id: tVjuh576LxU2HBqG4a1WuA + - id: 6V4k9tSxye23tjJgDossSw sortOrder: 1 fieldKey: metric_name label: Metric Name @@ -72687,7 +73196,7 @@ items: choices: null dynamic: false allowNull: false - - id: h4AQzuwiv2wJ8GAJ6qHyrP + - id: f5PY5fkSNAbrhcFCDdrCbg sortOrder: 2 fieldKey: properties label: Properties @@ -72701,7 +73210,7 @@ items: choices: null dynamic: false allowNull: false - - id: w45qaDiw18ss4izoZa9qPJ + - id: ufH8m2L9mDGkbTLr1T515b sortOrder: 3 fieldKey: time label: Time @@ -72720,7 +73229,7 @@ items: choices: null dynamic: false allowNull: false - - id: vnpG8HjMeJPBvh9jP4nxfR + - id: nkp2256PLGk7xNS2PMJ4C sortOrder: 4 fieldKey: value label: Value @@ -72734,7 +73243,7 @@ items: choices: null dynamic: false allowNull: false - - id: vx5FU2aiNQu1Fhcyiao6B8 + - id: kVGD5HvfGBbyKRL9YK5V4Z sortOrder: 5 fieldKey: unique_id label: Unique ID @@ -72762,7 +73271,7 @@ items: hidden: false defaultTrigger: event = "Audience Exited" fields: - - id: 42VHgKCMdmegBVpVWFa4UT + - id: nWmZxcSN21crLXND1vH26V sortOrder: 0 fieldKey: email label: Email @@ -72776,7 +73285,7 @@ items: choices: null dynamic: false allowNull: false - - id: kpTqRZ2f9717JL5J7vtG5a + - id: 4w4qAE75oWif34wsK8TNZC sortOrder: 1 fieldKey: external_id label: External ID @@ -72790,7 +73299,7 @@ items: choices: null dynamic: false allowNull: false - - id: wJeiVXAvMPQ17hvC9yhwH1 + - id: jnpcBUVGh6mxCXeyARtxFV sortOrder: 3 fieldKey: phone_number label: Phone Number @@ -72807,7 +73316,7 @@ items: choices: null dynamic: false allowNull: false - - id: p8w9XcMt1U8hcz8hihsFGS + - id: rh2dSD81THJhZWsVmq7HYE sortOrder: 4 fieldKey: enable_batching label: Batch Data to Klaviyo @@ -72820,6 +73329,515 @@ items: choices: null dynamic: false allowNull: false + - id: 2ZF8y45mrjJRPzNgAPTrh1 + sortOrder: 5 + fieldKey: country_code + label: Country Code + type: STRING + description: >- + Country Code in ISO 3166-1 alpha-2 format. If provided, this will be + used to validate and automatically format Phone Number field in E.164 + format accepted by Klaviyo. + placeholder: '' + required: false + multiple: false + choices: + - label: AD - Andorra + value: AD + - label: AE - United Arab Emirates + value: AE + - label: AF - Afghanistan + value: AF + - label: AG - Antigua and Barbuda + value: AG + - label: AI - Anguilla + value: AI + - label: AL - Albania + value: AL + - label: AM - Armenia + value: AM + - label: AO - Angola + value: AO + - label: AQ - Antarctica + value: AQ + - label: AR - Argentina + value: AR + - label: AS - American Samoa + value: AS + - label: AT - Austria + value: AT + - label: AU - Australia + value: AU + - label: AW - Aruba + value: AW + - label: AX - Åland Islands + value: AX + - label: AZ - Azerbaijan + value: AZ + - label: BA - Bosnia and Herzegovina + value: BA + - label: BB - Barbados + value: BB + - label: BD - Bangladesh + value: BD + - label: BE - Belgium + value: BE + - label: BF - Burkina Faso + value: BF + - label: BG - Bulgaria + value: BG + - label: BH - Bahrain + value: BH + - label: BI - Burundi + value: BI + - label: BJ - Benin + value: BJ + - label: BL - Saint Barthélemy + value: BL + - label: BM - Bermuda + value: BM + - label: BN - Brunei Darussalam + value: BN + - label: BO - Bolivia (Plurinational State of) + value: BO + - label: BQ - Bonaire, Sint Eustatius and Saba + value: BQ + - label: BR - Brazil + value: BR + - label: BS - Bahamas + value: BS + - label: BT - Bhutan + value: BT + - label: BV - Bouvet Island + value: BV + - label: BW - Botswana + value: BW + - label: BY - Belarus + value: BY + - label: BZ - Belize + value: BZ + - label: CA - Canada + value: CA + - label: CC - Cocos (Keeling) Islands + value: CC + - label: CD - Congo, Democratic Republic of the + value: CD + - label: CF - Central African Republic + value: CF + - label: CG - Congo + value: CG + - label: CH - Switzerland + value: CH + - label: CI - Côte d'Ivoire + value: CI + - label: CK - Cook Islands + value: CK + - label: CL - Chile + value: CL + - label: CM - Cameroon + value: CM + - label: CN - China + value: CN + - label: CO - Colombia + value: CO + - label: CR - Costa Rica + value: CR + - label: CU - Cuba + value: CU + - label: CV - Cabo Verde + value: CV + - label: CW - Curaçao + value: CW + - label: CX - Christmas Island + value: CX + - label: CY - Cyprus + value: CY + - label: CZ - Czechia + value: CZ + - label: DE - Germany + value: DE + - label: DJ - Djibouti + value: DJ + - label: DK - Denmark + value: DK + - label: DM - Dominica + value: DM + - label: DO - Dominican Republic + value: DO + - label: DZ - Algeria + value: DZ + - label: EC - Ecuador + value: EC + - label: EE - Estonia + value: EE + - label: EG - Egypt + value: EG + - label: EH - Western Sahara + value: EH + - label: ER - Eritrea + value: ER + - label: ES - Spain + value: ES + - label: ET - Ethiopia + value: ET + - label: FI - Finland + value: FI + - label: FJ - Fiji + value: FJ + - label: FK - Falkland Islands (Malvinas) + value: FK + - label: FM - Micronesia (Federated States of) + value: FM + - label: FO - Faroe Islands + value: FO + - label: FR - France + value: FR + - label: GA - Gabon + value: GA + - label: GB - United Kingdom of Great Britain and Northern Ireland + value: GB + - label: GD - Grenada + value: GD + - label: GE - Georgia + value: GE + - label: GF - French Guiana + value: GF + - label: GG - Guernsey + value: GG + - label: GH - Ghana + value: GH + - label: GI - Gibraltar + value: GI + - label: GL - Greenland + value: GL + - label: GM - Gambia + value: GM + - label: GN - Guinea + value: GN + - label: GP - Guadeloupe + value: GP + - label: GQ - Equatorial Guinea + value: GQ + - label: GR - Greece + value: GR + - label: GT - Guatemala + value: GT + - label: GU - Guam + value: GU + - label: GW - Guinea-Bissau + value: GW + - label: GY - Guyana + value: GY + - label: HK - Hong Kong + value: HK + - label: HM - Heard Island and McDonald Islands + value: HM + - label: HN - Honduras + value: HN + - label: HR - Croatia + value: HR + - label: HT - Haiti + value: HT + - label: HU - Hungary + value: HU + - label: ID - Indonesia + value: ID + - label: IE - Ireland + value: IE + - label: IL - Israel + value: IL + - label: IM - Isle of Man + value: IM + - label: IN - India + value: IN + - label: IO - British Indian Ocean Territory + value: IO + - label: IQ - Iraq + value: IQ + - label: IR - Iran (Islamic Republic of) + value: IR + - label: IS - Iceland + value: IS + - label: IT - Italy + value: IT + - label: JE - Jersey + value: JE + - label: JM - Jamaica + value: JM + - label: JO - Jordan + value: JO + - label: JP - Japan + value: JP + - label: KE - Kenya + value: KE + - label: KG - Kyrgyzstan + value: KG + - label: KH - Cambodia + value: KH + - label: KI - Kiribati + value: KI + - label: KM - Comoros + value: KM + - label: KN - Saint Kitts and Nevis + value: KN + - label: KP - Korea (Democratic People's Republic of) + value: KP + - label: KR - Korea, Republic of + value: KR + - label: KW - Kuwait + value: KW + - label: KY - Cayman Islands + value: KY + - label: KZ - Kazakhstan + value: KZ + - label: LA - Lao People's Democratic Republic + value: LA + - label: LB - Lebanon + value: LB + - label: LC - Saint Lucia + value: LC + - label: LI - Liechtenstein + value: LI + - label: LK - Sri Lanka + value: LK + - label: LR - Liberia + value: LR + - label: LS - Lesotho + value: LS + - label: LT - Lithuania + value: LT + - label: LU - Luxembourg + value: LU + - label: LV - Latvia + value: LV + - label: LY - Libya + value: LY + - label: MA - Morocco + value: MA + - label: MC - Monaco + value: MC + - label: MD - Moldova (Republic of) + value: MD + - label: ME - Montenegro + value: ME + - label: MF - Saint Martin (French part) + value: MF + - label: MG - Madagascar + value: MG + - label: MH - Marshall Islands + value: MH + - label: MK - North Macedonia + value: MK + - label: ML - Mali + value: ML + - label: MM - Myanmar + value: MM + - label: MN - Mongolia + value: MN + - label: MO - Macao + value: MO + - label: MP - Northern Mariana Islands + value: MP + - label: MQ - Martinique + value: MQ + - label: MR - Mauritania + value: MR + - label: MS - Montserrat + value: MS + - label: MT - Malta + value: MT + - label: MU - Mauritius + value: MU + - label: MV - Maldives + value: MV + - label: MW - Malawi + value: MW + - label: MX - Mexico + value: MX + - label: MY - Malaysia + value: MY + - label: MZ - Mozambique + value: MZ + - label: NA - Namibia + value: NA + - label: NC - New Caledonia + value: NC + - label: NE - Niger + value: NE + - label: NF - Norfolk Island + value: NF + - label: NG - Nigeria + value: NG + - label: NI - Nicaragua + value: NI + - label: NL - Netherlands + value: NL + - label: NO - Norway + value: 'NO' + - label: NP - Nepal + value: NP + - label: NR - Nauru + value: NR + - label: NU - Niue + value: NU + - label: NZ - New Zealand + value: NZ + - label: OM - Oman + value: OM + - label: PA - Panama + value: PA + - label: PE - Peru + value: PE + - label: PF - French Polynesia + value: PF + - label: PG - Papua New Guinea + value: PG + - label: PH - Philippines + value: PH + - label: PK - Pakistan + value: PK + - label: PL - Poland + value: PL + - label: PM - Saint Pierre and Miquelon + value: PM + - label: PN - Pitcairn + value: PN + - label: PR - Puerto Rico + value: PR + - label: PT - Portugal + value: PT + - label: PW - Palau + value: PW + - label: PY - Paraguay + value: PY + - label: QA - Qatar + value: QA + - label: RE - Réunion + value: RE + - label: RO - Romania + value: RO + - label: RS - Serbia + value: RS + - label: RU - Russian Federation + value: RU + - label: RW - Rwanda + value: RW + - label: SA - Saudi Arabia + value: SA + - label: SB - Solomon Islands + value: SB + - label: SC - Seychelles + value: SC + - label: SD - Sudan + value: SD + - label: SE - Sweden + value: SE + - label: SG - Singapore + value: SG + - label: SH - Saint Helena + value: SH + - label: SI - Slovenia + value: SI + - label: SJ - Svalbard and Jan Mayen + value: SJ + - label: SK - Slovakia + value: SK + - label: SL - Sierra Leone + value: SL + - label: SM - San Marino + value: SM + - label: SN - Senegal + value: SN + - label: SO - Somalia + value: SO + - label: SR - Suriname + value: SR + - label: SS - South Sudan + value: SS + - label: ST - São Tomé and Príncipe + value: ST + - label: SV - El Salvador + value: SV + - label: SX - Sint Maarten (Dutch part) + value: SX + - label: SY - Syrian Arab Republic + value: SY + - label: SZ - Eswatini + value: SZ + - label: TC - Turks and Caicos Islands + value: TC + - label: TD - Chad + value: TD + - label: TF - French Southern Territories + value: TF + - label: TG - Togo + value: TG + - label: TH - Thailand + value: TH + - label: TJ - Tajikistan + value: TJ + - label: TK - Tokelau + value: TK + - label: TL - Timor-Leste + value: TL + - label: TM - Turkmenistan + value: TM + - label: TN - Tunisia + value: TN + - label: TO - Tonga + value: TO + - label: TR - Turkey + value: TR + - label: TT - Trinidad and Tobago + value: TT + - label: TV - Tuvalu + value: TV + - label: TZ - Tanzania, United Republic of + value: TZ + - label: UA - Ukraine + value: UA + - label: UG - Uganda + value: UG + - label: UM - United States Minor Outlying Islands + value: UM + - label: UN - United Nations + value: UN + - label: US - United States of America + value: US + - label: UY - Uruguay + value: UY + - label: UZ - Uzbekistan + value: UZ + - label: VA - Holy See + value: VA + - label: VC - Saint Vincent and the Grenadines + value: VC + - label: VE - Venezuela (Bolivarian Republic of) + value: VE + - label: VG - Virgin Islands (British) + value: VG + - label: VI - Virgin Islands (U.S.) + value: VI + - label: VN - Viet Nam + value: VN + - label: VU - Vanuatu + value: VU + - label: WF - Wallis and Futuna + value: WF + - label: WS - Samoa + value: WS + - label: YE - Yemen + value: YE + - label: YT - Mayotte + value: YT + - label: ZA - South Africa + value: ZA + - label: ZM - Zambia + value: ZM + - label: ZW - Zimbabwe + value: ZW + dynamic: false + allowNull: false - id: 9XeQC7vecFTQE17eM1DeLN name: Add Profile to List (Engage) slug: addProfileToList @@ -72828,7 +73846,7 @@ items: hidden: false defaultTrigger: event = "Audience Entered" fields: - - id: 4WJXV7K5WGXghqrYiSUArJ + - id: qSQxJU5scAk76W36v8Yzos sortOrder: 0 fieldKey: email label: Email @@ -72842,7 +73860,7 @@ items: choices: null dynamic: false allowNull: false - - id: 2kJkKVHyrvGrwQKdiV8QNG + - id: sDSo5SakaAqtqsSch1uDmY sortOrder: 1 fieldKey: phone_number label: Phone Number @@ -72859,7 +73877,7 @@ items: choices: null dynamic: false allowNull: false - - id: kKUPDkZHv9JPFs7za865cc + - id: ihSdYb8w2GdsgAFEeWZyMF sortOrder: 3 fieldKey: external_id label: External ID @@ -72873,7 +73891,7 @@ items: choices: null dynamic: false allowNull: false - - id: 7rf1dsNQKfUDze8UMvixHA + - id: kh5JgqsyppgxU94dx53iZH sortOrder: 4 fieldKey: enable_batching label: Batch Data to Klaviyo @@ -72886,7 +73904,7 @@ items: choices: null dynamic: false allowNull: false - - id: vJuDMt3HfWMKoE4iKkrV4q + - id: t5ffT1QHY8jhPWbRTi3ntE sortOrder: 6 fieldKey: first_name label: First Name @@ -72900,7 +73918,7 @@ items: choices: null dynamic: false allowNull: false - - id: h1e8CgWWfFVYgnzgw8bcda + - id: 8debd22i2PYMYErtzFqPVw sortOrder: 7 fieldKey: last_name label: Last Name @@ -72914,7 +73932,7 @@ items: choices: null dynamic: false allowNull: false - - id: okSMqSN49wCA6cCajv6uxf + - id: qY9TSCbJNzu9CVP3w1gb74 sortOrder: 8 fieldKey: image label: Image @@ -72928,7 +73946,7 @@ items: choices: null dynamic: false allowNull: false - - id: rrFz4BTLHQUvUNUWZtp2q7 + - id: 3ZUE4a8K7QN98VXfJ8oZDF sortOrder: 9 fieldKey: title label: Title @@ -72942,7 +73960,7 @@ items: choices: null dynamic: false allowNull: false - - id: viDq9zZ5dfi4tC2xC6gGV4 + - id: 2vuJEZh9TP1Q8tZ5XQKN5D sortOrder: 10 fieldKey: organization label: Organization @@ -72958,7 +73976,7 @@ items: choices: null dynamic: false allowNull: false - - id: qgd7JNsHuWXo6BdpSgnAuU + - id: jMt6GVeo9j5p1twmZwwVMz sortOrder: 11 fieldKey: location label: Location @@ -72981,7 +73999,7 @@ items: choices: null dynamic: false allowNull: false - - id: nFyBJTmAkMU8S27BeZdxfH + - id: hWigQu4Cc44QPv476KL2id sortOrder: 12 fieldKey: properties label: Properties @@ -72997,6 +74015,515 @@ items: choices: null dynamic: false allowNull: false + - id: 5yz9x5ZQE5i1LrzTNbemsw + sortOrder: 13 + fieldKey: country_code + label: Country Code + type: STRING + description: >- + Country Code in ISO 3166-1 alpha-2 format. If provided, this will be + used to validate and automatically format Phone Number field in E.164 + format accepted by Klaviyo. + placeholder: '' + required: false + multiple: false + choices: + - label: AD - Andorra + value: AD + - label: AE - United Arab Emirates + value: AE + - label: AF - Afghanistan + value: AF + - label: AG - Antigua and Barbuda + value: AG + - label: AI - Anguilla + value: AI + - label: AL - Albania + value: AL + - label: AM - Armenia + value: AM + - label: AO - Angola + value: AO + - label: AQ - Antarctica + value: AQ + - label: AR - Argentina + value: AR + - label: AS - American Samoa + value: AS + - label: AT - Austria + value: AT + - label: AU - Australia + value: AU + - label: AW - Aruba + value: AW + - label: AX - Åland Islands + value: AX + - label: AZ - Azerbaijan + value: AZ + - label: BA - Bosnia and Herzegovina + value: BA + - label: BB - Barbados + value: BB + - label: BD - Bangladesh + value: BD + - label: BE - Belgium + value: BE + - label: BF - Burkina Faso + value: BF + - label: BG - Bulgaria + value: BG + - label: BH - Bahrain + value: BH + - label: BI - Burundi + value: BI + - label: BJ - Benin + value: BJ + - label: BL - Saint Barthélemy + value: BL + - label: BM - Bermuda + value: BM + - label: BN - Brunei Darussalam + value: BN + - label: BO - Bolivia (Plurinational State of) + value: BO + - label: BQ - Bonaire, Sint Eustatius and Saba + value: BQ + - label: BR - Brazil + value: BR + - label: BS - Bahamas + value: BS + - label: BT - Bhutan + value: BT + - label: BV - Bouvet Island + value: BV + - label: BW - Botswana + value: BW + - label: BY - Belarus + value: BY + - label: BZ - Belize + value: BZ + - label: CA - Canada + value: CA + - label: CC - Cocos (Keeling) Islands + value: CC + - label: CD - Congo, Democratic Republic of the + value: CD + - label: CF - Central African Republic + value: CF + - label: CG - Congo + value: CG + - label: CH - Switzerland + value: CH + - label: CI - Côte d'Ivoire + value: CI + - label: CK - Cook Islands + value: CK + - label: CL - Chile + value: CL + - label: CM - Cameroon + value: CM + - label: CN - China + value: CN + - label: CO - Colombia + value: CO + - label: CR - Costa Rica + value: CR + - label: CU - Cuba + value: CU + - label: CV - Cabo Verde + value: CV + - label: CW - Curaçao + value: CW + - label: CX - Christmas Island + value: CX + - label: CY - Cyprus + value: CY + - label: CZ - Czechia + value: CZ + - label: DE - Germany + value: DE + - label: DJ - Djibouti + value: DJ + - label: DK - Denmark + value: DK + - label: DM - Dominica + value: DM + - label: DO - Dominican Republic + value: DO + - label: DZ - Algeria + value: DZ + - label: EC - Ecuador + value: EC + - label: EE - Estonia + value: EE + - label: EG - Egypt + value: EG + - label: EH - Western Sahara + value: EH + - label: ER - Eritrea + value: ER + - label: ES - Spain + value: ES + - label: ET - Ethiopia + value: ET + - label: FI - Finland + value: FI + - label: FJ - Fiji + value: FJ + - label: FK - Falkland Islands (Malvinas) + value: FK + - label: FM - Micronesia (Federated States of) + value: FM + - label: FO - Faroe Islands + value: FO + - label: FR - France + value: FR + - label: GA - Gabon + value: GA + - label: GB - United Kingdom of Great Britain and Northern Ireland + value: GB + - label: GD - Grenada + value: GD + - label: GE - Georgia + value: GE + - label: GF - French Guiana + value: GF + - label: GG - Guernsey + value: GG + - label: GH - Ghana + value: GH + - label: GI - Gibraltar + value: GI + - label: GL - Greenland + value: GL + - label: GM - Gambia + value: GM + - label: GN - Guinea + value: GN + - label: GP - Guadeloupe + value: GP + - label: GQ - Equatorial Guinea + value: GQ + - label: GR - Greece + value: GR + - label: GT - Guatemala + value: GT + - label: GU - Guam + value: GU + - label: GW - Guinea-Bissau + value: GW + - label: GY - Guyana + value: GY + - label: HK - Hong Kong + value: HK + - label: HM - Heard Island and McDonald Islands + value: HM + - label: HN - Honduras + value: HN + - label: HR - Croatia + value: HR + - label: HT - Haiti + value: HT + - label: HU - Hungary + value: HU + - label: ID - Indonesia + value: ID + - label: IE - Ireland + value: IE + - label: IL - Israel + value: IL + - label: IM - Isle of Man + value: IM + - label: IN - India + value: IN + - label: IO - British Indian Ocean Territory + value: IO + - label: IQ - Iraq + value: IQ + - label: IR - Iran (Islamic Republic of) + value: IR + - label: IS - Iceland + value: IS + - label: IT - Italy + value: IT + - label: JE - Jersey + value: JE + - label: JM - Jamaica + value: JM + - label: JO - Jordan + value: JO + - label: JP - Japan + value: JP + - label: KE - Kenya + value: KE + - label: KG - Kyrgyzstan + value: KG + - label: KH - Cambodia + value: KH + - label: KI - Kiribati + value: KI + - label: KM - Comoros + value: KM + - label: KN - Saint Kitts and Nevis + value: KN + - label: KP - Korea (Democratic People's Republic of) + value: KP + - label: KR - Korea, Republic of + value: KR + - label: KW - Kuwait + value: KW + - label: KY - Cayman Islands + value: KY + - label: KZ - Kazakhstan + value: KZ + - label: LA - Lao People's Democratic Republic + value: LA + - label: LB - Lebanon + value: LB + - label: LC - Saint Lucia + value: LC + - label: LI - Liechtenstein + value: LI + - label: LK - Sri Lanka + value: LK + - label: LR - Liberia + value: LR + - label: LS - Lesotho + value: LS + - label: LT - Lithuania + value: LT + - label: LU - Luxembourg + value: LU + - label: LV - Latvia + value: LV + - label: LY - Libya + value: LY + - label: MA - Morocco + value: MA + - label: MC - Monaco + value: MC + - label: MD - Moldova (Republic of) + value: MD + - label: ME - Montenegro + value: ME + - label: MF - Saint Martin (French part) + value: MF + - label: MG - Madagascar + value: MG + - label: MH - Marshall Islands + value: MH + - label: MK - North Macedonia + value: MK + - label: ML - Mali + value: ML + - label: MM - Myanmar + value: MM + - label: MN - Mongolia + value: MN + - label: MO - Macao + value: MO + - label: MP - Northern Mariana Islands + value: MP + - label: MQ - Martinique + value: MQ + - label: MR - Mauritania + value: MR + - label: MS - Montserrat + value: MS + - label: MT - Malta + value: MT + - label: MU - Mauritius + value: MU + - label: MV - Maldives + value: MV + - label: MW - Malawi + value: MW + - label: MX - Mexico + value: MX + - label: MY - Malaysia + value: MY + - label: MZ - Mozambique + value: MZ + - label: NA - Namibia + value: NA + - label: NC - New Caledonia + value: NC + - label: NE - Niger + value: NE + - label: NF - Norfolk Island + value: NF + - label: NG - Nigeria + value: NG + - label: NI - Nicaragua + value: NI + - label: NL - Netherlands + value: NL + - label: NO - Norway + value: 'NO' + - label: NP - Nepal + value: NP + - label: NR - Nauru + value: NR + - label: NU - Niue + value: NU + - label: NZ - New Zealand + value: NZ + - label: OM - Oman + value: OM + - label: PA - Panama + value: PA + - label: PE - Peru + value: PE + - label: PF - French Polynesia + value: PF + - label: PG - Papua New Guinea + value: PG + - label: PH - Philippines + value: PH + - label: PK - Pakistan + value: PK + - label: PL - Poland + value: PL + - label: PM - Saint Pierre and Miquelon + value: PM + - label: PN - Pitcairn + value: PN + - label: PR - Puerto Rico + value: PR + - label: PT - Portugal + value: PT + - label: PW - Palau + value: PW + - label: PY - Paraguay + value: PY + - label: QA - Qatar + value: QA + - label: RE - Réunion + value: RE + - label: RO - Romania + value: RO + - label: RS - Serbia + value: RS + - label: RU - Russian Federation + value: RU + - label: RW - Rwanda + value: RW + - label: SA - Saudi Arabia + value: SA + - label: SB - Solomon Islands + value: SB + - label: SC - Seychelles + value: SC + - label: SD - Sudan + value: SD + - label: SE - Sweden + value: SE + - label: SG - Singapore + value: SG + - label: SH - Saint Helena + value: SH + - label: SI - Slovenia + value: SI + - label: SJ - Svalbard and Jan Mayen + value: SJ + - label: SK - Slovakia + value: SK + - label: SL - Sierra Leone + value: SL + - label: SM - San Marino + value: SM + - label: SN - Senegal + value: SN + - label: SO - Somalia + value: SO + - label: SR - Suriname + value: SR + - label: SS - South Sudan + value: SS + - label: ST - São Tomé and Príncipe + value: ST + - label: SV - El Salvador + value: SV + - label: SX - Sint Maarten (Dutch part) + value: SX + - label: SY - Syrian Arab Republic + value: SY + - label: SZ - Eswatini + value: SZ + - label: TC - Turks and Caicos Islands + value: TC + - label: TD - Chad + value: TD + - label: TF - French Southern Territories + value: TF + - label: TG - Togo + value: TG + - label: TH - Thailand + value: TH + - label: TJ - Tajikistan + value: TJ + - label: TK - Tokelau + value: TK + - label: TL - Timor-Leste + value: TL + - label: TM - Turkmenistan + value: TM + - label: TN - Tunisia + value: TN + - label: TO - Tonga + value: TO + - label: TR - Turkey + value: TR + - label: TT - Trinidad and Tobago + value: TT + - label: TV - Tuvalu + value: TV + - label: TZ - Tanzania, United Republic of + value: TZ + - label: UA - Ukraine + value: UA + - label: UG - Uganda + value: UG + - label: UM - United States Minor Outlying Islands + value: UM + - label: UN - United Nations + value: UN + - label: US - United States of America + value: US + - label: UY - Uruguay + value: UY + - label: UZ - Uzbekistan + value: UZ + - label: VA - Holy See + value: VA + - label: VC - Saint Vincent and the Grenadines + value: VC + - label: VE - Venezuela (Bolivarian Republic of) + value: VE + - label: VG - Virgin Islands (British) + value: VG + - label: VI - Virgin Islands (U.S.) + value: VI + - label: VN - Viet Nam + value: VN + - label: VU - Vanuatu + value: VU + - label: WF - Wallis and Futuna + value: WF + - label: WS - Samoa + value: WS + - label: YE - Yemen + value: YE + - label: YT - Mayotte + value: YT + - label: ZA - South Africa + value: ZA + - label: ZM - Zambia + value: ZM + - label: ZW - Zimbabwe + value: ZW + dynamic: false + allowNull: false - id: 5ceBBsjKrffLFBfX3HfpdY name: Remove Profile slug: removeProfile @@ -73005,7 +74532,7 @@ items: hidden: false defaultTrigger: event = "Identify" fields: - - id: dVEYLfkEc8WrPYjusUnSdX + - id: oU3NMii4hKHCQxaUU2p5sc sortOrder: 0 fieldKey: email label: Email @@ -73019,7 +74546,7 @@ items: choices: null dynamic: false allowNull: false - - id: 3HwM4fuJM7SKKFPooJGAM7 + - id: bSA7r4qDqLLjM3bsbZBNJJ sortOrder: 1 fieldKey: external_id label: External ID @@ -73034,7 +74561,7 @@ items: choices: null dynamic: false allowNull: false - - id: eoJEaP391BqfWuPg16DCfz + - id: xavDoBTTjHEtrfuBL2xmJj sortOrder: 2 fieldKey: list_id label: List @@ -73046,7 +74573,7 @@ items: choices: null dynamic: true allowNull: false - - id: rAcD3mxdE6n1mY69978NJ3 + - id: hWxJwCyDfscZc7SV6ze2iW sortOrder: 3 fieldKey: enable_batching label: Batch Data to Klaviyo @@ -73059,7 +74586,7 @@ items: choices: null dynamic: false allowNull: false - - id: m6mzLLvSnuMyfoWF8GBRSF + - id: ncQJYob45f4Bcz74NzJ3NJ sortOrder: 4 fieldKey: phone_number label: Phone Number @@ -73076,6 +74603,515 @@ items: choices: null dynamic: false allowNull: false + - id: jT9doAFnoUHqXHrGgTELoX + sortOrder: 5 + fieldKey: country_code + label: Country Code + type: STRING + description: >- + Country Code in ISO 3166-1 alpha-2 format. If provided, this will be + used to validate and automatically format Phone Number field in E.164 + format accepted by Klaviyo. + placeholder: '' + required: false + multiple: false + choices: + - label: AD - Andorra + value: AD + - label: AE - United Arab Emirates + value: AE + - label: AF - Afghanistan + value: AF + - label: AG - Antigua and Barbuda + value: AG + - label: AI - Anguilla + value: AI + - label: AL - Albania + value: AL + - label: AM - Armenia + value: AM + - label: AO - Angola + value: AO + - label: AQ - Antarctica + value: AQ + - label: AR - Argentina + value: AR + - label: AS - American Samoa + value: AS + - label: AT - Austria + value: AT + - label: AU - Australia + value: AU + - label: AW - Aruba + value: AW + - label: AX - Åland Islands + value: AX + - label: AZ - Azerbaijan + value: AZ + - label: BA - Bosnia and Herzegovina + value: BA + - label: BB - Barbados + value: BB + - label: BD - Bangladesh + value: BD + - label: BE - Belgium + value: BE + - label: BF - Burkina Faso + value: BF + - label: BG - Bulgaria + value: BG + - label: BH - Bahrain + value: BH + - label: BI - Burundi + value: BI + - label: BJ - Benin + value: BJ + - label: BL - Saint Barthélemy + value: BL + - label: BM - Bermuda + value: BM + - label: BN - Brunei Darussalam + value: BN + - label: BO - Bolivia (Plurinational State of) + value: BO + - label: BQ - Bonaire, Sint Eustatius and Saba + value: BQ + - label: BR - Brazil + value: BR + - label: BS - Bahamas + value: BS + - label: BT - Bhutan + value: BT + - label: BV - Bouvet Island + value: BV + - label: BW - Botswana + value: BW + - label: BY - Belarus + value: BY + - label: BZ - Belize + value: BZ + - label: CA - Canada + value: CA + - label: CC - Cocos (Keeling) Islands + value: CC + - label: CD - Congo, Democratic Republic of the + value: CD + - label: CF - Central African Republic + value: CF + - label: CG - Congo + value: CG + - label: CH - Switzerland + value: CH + - label: CI - Côte d'Ivoire + value: CI + - label: CK - Cook Islands + value: CK + - label: CL - Chile + value: CL + - label: CM - Cameroon + value: CM + - label: CN - China + value: CN + - label: CO - Colombia + value: CO + - label: CR - Costa Rica + value: CR + - label: CU - Cuba + value: CU + - label: CV - Cabo Verde + value: CV + - label: CW - Curaçao + value: CW + - label: CX - Christmas Island + value: CX + - label: CY - Cyprus + value: CY + - label: CZ - Czechia + value: CZ + - label: DE - Germany + value: DE + - label: DJ - Djibouti + value: DJ + - label: DK - Denmark + value: DK + - label: DM - Dominica + value: DM + - label: DO - Dominican Republic + value: DO + - label: DZ - Algeria + value: DZ + - label: EC - Ecuador + value: EC + - label: EE - Estonia + value: EE + - label: EG - Egypt + value: EG + - label: EH - Western Sahara + value: EH + - label: ER - Eritrea + value: ER + - label: ES - Spain + value: ES + - label: ET - Ethiopia + value: ET + - label: FI - Finland + value: FI + - label: FJ - Fiji + value: FJ + - label: FK - Falkland Islands (Malvinas) + value: FK + - label: FM - Micronesia (Federated States of) + value: FM + - label: FO - Faroe Islands + value: FO + - label: FR - France + value: FR + - label: GA - Gabon + value: GA + - label: GB - United Kingdom of Great Britain and Northern Ireland + value: GB + - label: GD - Grenada + value: GD + - label: GE - Georgia + value: GE + - label: GF - French Guiana + value: GF + - label: GG - Guernsey + value: GG + - label: GH - Ghana + value: GH + - label: GI - Gibraltar + value: GI + - label: GL - Greenland + value: GL + - label: GM - Gambia + value: GM + - label: GN - Guinea + value: GN + - label: GP - Guadeloupe + value: GP + - label: GQ - Equatorial Guinea + value: GQ + - label: GR - Greece + value: GR + - label: GT - Guatemala + value: GT + - label: GU - Guam + value: GU + - label: GW - Guinea-Bissau + value: GW + - label: GY - Guyana + value: GY + - label: HK - Hong Kong + value: HK + - label: HM - Heard Island and McDonald Islands + value: HM + - label: HN - Honduras + value: HN + - label: HR - Croatia + value: HR + - label: HT - Haiti + value: HT + - label: HU - Hungary + value: HU + - label: ID - Indonesia + value: ID + - label: IE - Ireland + value: IE + - label: IL - Israel + value: IL + - label: IM - Isle of Man + value: IM + - label: IN - India + value: IN + - label: IO - British Indian Ocean Territory + value: IO + - label: IQ - Iraq + value: IQ + - label: IR - Iran (Islamic Republic of) + value: IR + - label: IS - Iceland + value: IS + - label: IT - Italy + value: IT + - label: JE - Jersey + value: JE + - label: JM - Jamaica + value: JM + - label: JO - Jordan + value: JO + - label: JP - Japan + value: JP + - label: KE - Kenya + value: KE + - label: KG - Kyrgyzstan + value: KG + - label: KH - Cambodia + value: KH + - label: KI - Kiribati + value: KI + - label: KM - Comoros + value: KM + - label: KN - Saint Kitts and Nevis + value: KN + - label: KP - Korea (Democratic People's Republic of) + value: KP + - label: KR - Korea, Republic of + value: KR + - label: KW - Kuwait + value: KW + - label: KY - Cayman Islands + value: KY + - label: KZ - Kazakhstan + value: KZ + - label: LA - Lao People's Democratic Republic + value: LA + - label: LB - Lebanon + value: LB + - label: LC - Saint Lucia + value: LC + - label: LI - Liechtenstein + value: LI + - label: LK - Sri Lanka + value: LK + - label: LR - Liberia + value: LR + - label: LS - Lesotho + value: LS + - label: LT - Lithuania + value: LT + - label: LU - Luxembourg + value: LU + - label: LV - Latvia + value: LV + - label: LY - Libya + value: LY + - label: MA - Morocco + value: MA + - label: MC - Monaco + value: MC + - label: MD - Moldova (Republic of) + value: MD + - label: ME - Montenegro + value: ME + - label: MF - Saint Martin (French part) + value: MF + - label: MG - Madagascar + value: MG + - label: MH - Marshall Islands + value: MH + - label: MK - North Macedonia + value: MK + - label: ML - Mali + value: ML + - label: MM - Myanmar + value: MM + - label: MN - Mongolia + value: MN + - label: MO - Macao + value: MO + - label: MP - Northern Mariana Islands + value: MP + - label: MQ - Martinique + value: MQ + - label: MR - Mauritania + value: MR + - label: MS - Montserrat + value: MS + - label: MT - Malta + value: MT + - label: MU - Mauritius + value: MU + - label: MV - Maldives + value: MV + - label: MW - Malawi + value: MW + - label: MX - Mexico + value: MX + - label: MY - Malaysia + value: MY + - label: MZ - Mozambique + value: MZ + - label: NA - Namibia + value: NA + - label: NC - New Caledonia + value: NC + - label: NE - Niger + value: NE + - label: NF - Norfolk Island + value: NF + - label: NG - Nigeria + value: NG + - label: NI - Nicaragua + value: NI + - label: NL - Netherlands + value: NL + - label: NO - Norway + value: 'NO' + - label: NP - Nepal + value: NP + - label: NR - Nauru + value: NR + - label: NU - Niue + value: NU + - label: NZ - New Zealand + value: NZ + - label: OM - Oman + value: OM + - label: PA - Panama + value: PA + - label: PE - Peru + value: PE + - label: PF - French Polynesia + value: PF + - label: PG - Papua New Guinea + value: PG + - label: PH - Philippines + value: PH + - label: PK - Pakistan + value: PK + - label: PL - Poland + value: PL + - label: PM - Saint Pierre and Miquelon + value: PM + - label: PN - Pitcairn + value: PN + - label: PR - Puerto Rico + value: PR + - label: PT - Portugal + value: PT + - label: PW - Palau + value: PW + - label: PY - Paraguay + value: PY + - label: QA - Qatar + value: QA + - label: RE - Réunion + value: RE + - label: RO - Romania + value: RO + - label: RS - Serbia + value: RS + - label: RU - Russian Federation + value: RU + - label: RW - Rwanda + value: RW + - label: SA - Saudi Arabia + value: SA + - label: SB - Solomon Islands + value: SB + - label: SC - Seychelles + value: SC + - label: SD - Sudan + value: SD + - label: SE - Sweden + value: SE + - label: SG - Singapore + value: SG + - label: SH - Saint Helena + value: SH + - label: SI - Slovenia + value: SI + - label: SJ - Svalbard and Jan Mayen + value: SJ + - label: SK - Slovakia + value: SK + - label: SL - Sierra Leone + value: SL + - label: SM - San Marino + value: SM + - label: SN - Senegal + value: SN + - label: SO - Somalia + value: SO + - label: SR - Suriname + value: SR + - label: SS - South Sudan + value: SS + - label: ST - São Tomé and Príncipe + value: ST + - label: SV - El Salvador + value: SV + - label: SX - Sint Maarten (Dutch part) + value: SX + - label: SY - Syrian Arab Republic + value: SY + - label: SZ - Eswatini + value: SZ + - label: TC - Turks and Caicos Islands + value: TC + - label: TD - Chad + value: TD + - label: TF - French Southern Territories + value: TF + - label: TG - Togo + value: TG + - label: TH - Thailand + value: TH + - label: TJ - Tajikistan + value: TJ + - label: TK - Tokelau + value: TK + - label: TL - Timor-Leste + value: TL + - label: TM - Turkmenistan + value: TM + - label: TN - Tunisia + value: TN + - label: TO - Tonga + value: TO + - label: TR - Turkey + value: TR + - label: TT - Trinidad and Tobago + value: TT + - label: TV - Tuvalu + value: TV + - label: TZ - Tanzania, United Republic of + value: TZ + - label: UA - Ukraine + value: UA + - label: UG - Uganda + value: UG + - label: UM - United States Minor Outlying Islands + value: UM + - label: UN - United Nations + value: UN + - label: US - United States of America + value: US + - label: UY - Uruguay + value: UY + - label: UZ - Uzbekistan + value: UZ + - label: VA - Holy See + value: VA + - label: VC - Saint Vincent and the Grenadines + value: VC + - label: VE - Venezuela (Bolivarian Republic of) + value: VE + - label: VG - Virgin Islands (British) + value: VG + - label: VI - Virgin Islands (U.S.) + value: VI + - label: VN - Viet Nam + value: VN + - label: VU - Vanuatu + value: VU + - label: WF - Wallis and Futuna + value: WF + - label: WS - Samoa + value: WS + - label: YE - Yemen + value: YE + - label: YT - Mayotte + value: YT + - label: ZA - South Africa + value: ZA + - label: ZM - Zambia + value: ZM + - label: ZW - Zimbabwe + value: ZW + dynamic: false + allowNull: false - id: hrZ9JVS64P91hUzaT6wLPm name: Subscribe Profile slug: subscribeProfile @@ -73084,7 +75120,7 @@ items: hidden: false defaultTrigger: type = "track" and event = "User Subscribed" fields: - - id: cXh4qBrcNrkUghGrbm6fjw + - id: 468uEMHQbwXUpWJjFaqfXV sortOrder: 0 fieldKey: email label: Email @@ -73106,7 +75142,7 @@ items: choices: null dynamic: false allowNull: false - - id: qUUZb9fRyMtiJBFqbHP42n + - id: 23UPBYyT3JnyNBQFSptp6d sortOrder: 1 fieldKey: phone_number label: Phone Number @@ -73128,8 +75164,517 @@ items: choices: null dynamic: false allowNull: false - - id: fbVUAM2c9rd1WhTye384rE + - id: jddAMiuqeGP9V3G3CNVvrh sortOrder: 2 + fieldKey: country_code + label: Country Code + type: STRING + description: >- + Country Code in ISO 3166-1 alpha-2 format. If provided, this will be + used to validate and automatically format Phone Number field in E.164 + format accepted by Klaviyo. + placeholder: '' + required: false + multiple: false + choices: + - label: AD - Andorra + value: AD + - label: AE - United Arab Emirates + value: AE + - label: AF - Afghanistan + value: AF + - label: AG - Antigua and Barbuda + value: AG + - label: AI - Anguilla + value: AI + - label: AL - Albania + value: AL + - label: AM - Armenia + value: AM + - label: AO - Angola + value: AO + - label: AQ - Antarctica + value: AQ + - label: AR - Argentina + value: AR + - label: AS - American Samoa + value: AS + - label: AT - Austria + value: AT + - label: AU - Australia + value: AU + - label: AW - Aruba + value: AW + - label: AX - Åland Islands + value: AX + - label: AZ - Azerbaijan + value: AZ + - label: BA - Bosnia and Herzegovina + value: BA + - label: BB - Barbados + value: BB + - label: BD - Bangladesh + value: BD + - label: BE - Belgium + value: BE + - label: BF - Burkina Faso + value: BF + - label: BG - Bulgaria + value: BG + - label: BH - Bahrain + value: BH + - label: BI - Burundi + value: BI + - label: BJ - Benin + value: BJ + - label: BL - Saint Barthélemy + value: BL + - label: BM - Bermuda + value: BM + - label: BN - Brunei Darussalam + value: BN + - label: BO - Bolivia (Plurinational State of) + value: BO + - label: BQ - Bonaire, Sint Eustatius and Saba + value: BQ + - label: BR - Brazil + value: BR + - label: BS - Bahamas + value: BS + - label: BT - Bhutan + value: BT + - label: BV - Bouvet Island + value: BV + - label: BW - Botswana + value: BW + - label: BY - Belarus + value: BY + - label: BZ - Belize + value: BZ + - label: CA - Canada + value: CA + - label: CC - Cocos (Keeling) Islands + value: CC + - label: CD - Congo, Democratic Republic of the + value: CD + - label: CF - Central African Republic + value: CF + - label: CG - Congo + value: CG + - label: CH - Switzerland + value: CH + - label: CI - Côte d'Ivoire + value: CI + - label: CK - Cook Islands + value: CK + - label: CL - Chile + value: CL + - label: CM - Cameroon + value: CM + - label: CN - China + value: CN + - label: CO - Colombia + value: CO + - label: CR - Costa Rica + value: CR + - label: CU - Cuba + value: CU + - label: CV - Cabo Verde + value: CV + - label: CW - Curaçao + value: CW + - label: CX - Christmas Island + value: CX + - label: CY - Cyprus + value: CY + - label: CZ - Czechia + value: CZ + - label: DE - Germany + value: DE + - label: DJ - Djibouti + value: DJ + - label: DK - Denmark + value: DK + - label: DM - Dominica + value: DM + - label: DO - Dominican Republic + value: DO + - label: DZ - Algeria + value: DZ + - label: EC - Ecuador + value: EC + - label: EE - Estonia + value: EE + - label: EG - Egypt + value: EG + - label: EH - Western Sahara + value: EH + - label: ER - Eritrea + value: ER + - label: ES - Spain + value: ES + - label: ET - Ethiopia + value: ET + - label: FI - Finland + value: FI + - label: FJ - Fiji + value: FJ + - label: FK - Falkland Islands (Malvinas) + value: FK + - label: FM - Micronesia (Federated States of) + value: FM + - label: FO - Faroe Islands + value: FO + - label: FR - France + value: FR + - label: GA - Gabon + value: GA + - label: GB - United Kingdom of Great Britain and Northern Ireland + value: GB + - label: GD - Grenada + value: GD + - label: GE - Georgia + value: GE + - label: GF - French Guiana + value: GF + - label: GG - Guernsey + value: GG + - label: GH - Ghana + value: GH + - label: GI - Gibraltar + value: GI + - label: GL - Greenland + value: GL + - label: GM - Gambia + value: GM + - label: GN - Guinea + value: GN + - label: GP - Guadeloupe + value: GP + - label: GQ - Equatorial Guinea + value: GQ + - label: GR - Greece + value: GR + - label: GT - Guatemala + value: GT + - label: GU - Guam + value: GU + - label: GW - Guinea-Bissau + value: GW + - label: GY - Guyana + value: GY + - label: HK - Hong Kong + value: HK + - label: HM - Heard Island and McDonald Islands + value: HM + - label: HN - Honduras + value: HN + - label: HR - Croatia + value: HR + - label: HT - Haiti + value: HT + - label: HU - Hungary + value: HU + - label: ID - Indonesia + value: ID + - label: IE - Ireland + value: IE + - label: IL - Israel + value: IL + - label: IM - Isle of Man + value: IM + - label: IN - India + value: IN + - label: IO - British Indian Ocean Territory + value: IO + - label: IQ - Iraq + value: IQ + - label: IR - Iran (Islamic Republic of) + value: IR + - label: IS - Iceland + value: IS + - label: IT - Italy + value: IT + - label: JE - Jersey + value: JE + - label: JM - Jamaica + value: JM + - label: JO - Jordan + value: JO + - label: JP - Japan + value: JP + - label: KE - Kenya + value: KE + - label: KG - Kyrgyzstan + value: KG + - label: KH - Cambodia + value: KH + - label: KI - Kiribati + value: KI + - label: KM - Comoros + value: KM + - label: KN - Saint Kitts and Nevis + value: KN + - label: KP - Korea (Democratic People's Republic of) + value: KP + - label: KR - Korea, Republic of + value: KR + - label: KW - Kuwait + value: KW + - label: KY - Cayman Islands + value: KY + - label: KZ - Kazakhstan + value: KZ + - label: LA - Lao People's Democratic Republic + value: LA + - label: LB - Lebanon + value: LB + - label: LC - Saint Lucia + value: LC + - label: LI - Liechtenstein + value: LI + - label: LK - Sri Lanka + value: LK + - label: LR - Liberia + value: LR + - label: LS - Lesotho + value: LS + - label: LT - Lithuania + value: LT + - label: LU - Luxembourg + value: LU + - label: LV - Latvia + value: LV + - label: LY - Libya + value: LY + - label: MA - Morocco + value: MA + - label: MC - Monaco + value: MC + - label: MD - Moldova (Republic of) + value: MD + - label: ME - Montenegro + value: ME + - label: MF - Saint Martin (French part) + value: MF + - label: MG - Madagascar + value: MG + - label: MH - Marshall Islands + value: MH + - label: MK - North Macedonia + value: MK + - label: ML - Mali + value: ML + - label: MM - Myanmar + value: MM + - label: MN - Mongolia + value: MN + - label: MO - Macao + value: MO + - label: MP - Northern Mariana Islands + value: MP + - label: MQ - Martinique + value: MQ + - label: MR - Mauritania + value: MR + - label: MS - Montserrat + value: MS + - label: MT - Malta + value: MT + - label: MU - Mauritius + value: MU + - label: MV - Maldives + value: MV + - label: MW - Malawi + value: MW + - label: MX - Mexico + value: MX + - label: MY - Malaysia + value: MY + - label: MZ - Mozambique + value: MZ + - label: NA - Namibia + value: NA + - label: NC - New Caledonia + value: NC + - label: NE - Niger + value: NE + - label: NF - Norfolk Island + value: NF + - label: NG - Nigeria + value: NG + - label: NI - Nicaragua + value: NI + - label: NL - Netherlands + value: NL + - label: NO - Norway + value: 'NO' + - label: NP - Nepal + value: NP + - label: NR - Nauru + value: NR + - label: NU - Niue + value: NU + - label: NZ - New Zealand + value: NZ + - label: OM - Oman + value: OM + - label: PA - Panama + value: PA + - label: PE - Peru + value: PE + - label: PF - French Polynesia + value: PF + - label: PG - Papua New Guinea + value: PG + - label: PH - Philippines + value: PH + - label: PK - Pakistan + value: PK + - label: PL - Poland + value: PL + - label: PM - Saint Pierre and Miquelon + value: PM + - label: PN - Pitcairn + value: PN + - label: PR - Puerto Rico + value: PR + - label: PT - Portugal + value: PT + - label: PW - Palau + value: PW + - label: PY - Paraguay + value: PY + - label: QA - Qatar + value: QA + - label: RE - Réunion + value: RE + - label: RO - Romania + value: RO + - label: RS - Serbia + value: RS + - label: RU - Russian Federation + value: RU + - label: RW - Rwanda + value: RW + - label: SA - Saudi Arabia + value: SA + - label: SB - Solomon Islands + value: SB + - label: SC - Seychelles + value: SC + - label: SD - Sudan + value: SD + - label: SE - Sweden + value: SE + - label: SG - Singapore + value: SG + - label: SH - Saint Helena + value: SH + - label: SI - Slovenia + value: SI + - label: SJ - Svalbard and Jan Mayen + value: SJ + - label: SK - Slovakia + value: SK + - label: SL - Sierra Leone + value: SL + - label: SM - San Marino + value: SM + - label: SN - Senegal + value: SN + - label: SO - Somalia + value: SO + - label: SR - Suriname + value: SR + - label: SS - South Sudan + value: SS + - label: ST - São Tomé and Príncipe + value: ST + - label: SV - El Salvador + value: SV + - label: SX - Sint Maarten (Dutch part) + value: SX + - label: SY - Syrian Arab Republic + value: SY + - label: SZ - Eswatini + value: SZ + - label: TC - Turks and Caicos Islands + value: TC + - label: TD - Chad + value: TD + - label: TF - French Southern Territories + value: TF + - label: TG - Togo + value: TG + - label: TH - Thailand + value: TH + - label: TJ - Tajikistan + value: TJ + - label: TK - Tokelau + value: TK + - label: TL - Timor-Leste + value: TL + - label: TM - Turkmenistan + value: TM + - label: TN - Tunisia + value: TN + - label: TO - Tonga + value: TO + - label: TR - Turkey + value: TR + - label: TT - Trinidad and Tobago + value: TT + - label: TV - Tuvalu + value: TV + - label: TZ - Tanzania, United Republic of + value: TZ + - label: UA - Ukraine + value: UA + - label: UG - Uganda + value: UG + - label: UM - United States Minor Outlying Islands + value: UM + - label: UN - United Nations + value: UN + - label: US - United States of America + value: US + - label: UY - Uruguay + value: UY + - label: UZ - Uzbekistan + value: UZ + - label: VA - Holy See + value: VA + - label: VC - Saint Vincent and the Grenadines + value: VC + - label: VE - Venezuela (Bolivarian Republic of) + value: VE + - label: VG - Virgin Islands (British) + value: VG + - label: VI - Virgin Islands (U.S.) + value: VI + - label: VN - Viet Nam + value: VN + - label: VU - Vanuatu + value: VU + - label: WF - Wallis and Futuna + value: WF + - label: WS - Samoa + value: WS + - label: YE - Yemen + value: YE + - label: YT - Mayotte + value: YT + - label: ZA - South Africa + value: ZA + - label: ZM - Zambia + value: ZM + - label: ZW - Zimbabwe + value: ZW + dynamic: false + allowNull: false + - id: fsQMbYbLWxAtaMSFMY7UGT + sortOrder: 3 fieldKey: list_id label: List Id type: STRING @@ -73143,8 +75688,8 @@ items: choices: null dynamic: true allowNull: false - - id: rEZP8ZyXpmNgKLCfcvdm3P - sortOrder: 3 + - id: 6ZfTK2ttVtufFwYcSHbj3T + sortOrder: 4 fieldKey: custom_source label: Custom Source ($source) type: STRING @@ -73160,8 +75705,8 @@ items: choices: null dynamic: false allowNull: false - - id: aydPxs2JrMACHD1eprXbRk - sortOrder: 4 + - id: oLmftsz74RfbS2npxXrtY4 + sortOrder: 5 fieldKey: consented_at label: Consented At type: DATETIME @@ -73174,8 +75719,8 @@ items: choices: null dynamic: false allowNull: false - - id: q9gY8Gxe8MabGkppwMs9Tc - sortOrder: 5 + - id: h9bgqTxptCs19KhM6PweZE + sortOrder: 6 fieldKey: enable_batching label: Batch Data to Klaviyo type: BOOLEAN @@ -73194,7 +75739,7 @@ items: hidden: false defaultTrigger: type = "track" and event = "User Unsubscribed" fields: - - id: szbs93n8S99Ex68gzeqTVL + - id: ixZopyzvgufMrhm5PQ85tx sortOrder: 0 fieldKey: email label: Email @@ -73216,7 +75761,7 @@ items: choices: null dynamic: false allowNull: false - - id: uhpV1TTjvFXut4NiqEL1rQ + - id: 9YVEG1w2pzqBBRsx3AaAL4 sortOrder: 1 fieldKey: phone_number label: Phone Number @@ -73238,8 +75783,517 @@ items: choices: null dynamic: false allowNull: false - - id: 28xYoRn1FkkpRmYmNNtmu5 + - id: tj66mNN8MvTWBXztJVrFAj sortOrder: 2 + fieldKey: country_code + label: Country Code + type: STRING + description: >- + Country Code in ISO 3166-1 alpha-2 format. If provided, this will be + used to validate and automatically format Phone Number field in E.164 + format accepted by Klaviyo. + placeholder: '' + required: false + multiple: false + choices: + - label: AD - Andorra + value: AD + - label: AE - United Arab Emirates + value: AE + - label: AF - Afghanistan + value: AF + - label: AG - Antigua and Barbuda + value: AG + - label: AI - Anguilla + value: AI + - label: AL - Albania + value: AL + - label: AM - Armenia + value: AM + - label: AO - Angola + value: AO + - label: AQ - Antarctica + value: AQ + - label: AR - Argentina + value: AR + - label: AS - American Samoa + value: AS + - label: AT - Austria + value: AT + - label: AU - Australia + value: AU + - label: AW - Aruba + value: AW + - label: AX - Åland Islands + value: AX + - label: AZ - Azerbaijan + value: AZ + - label: BA - Bosnia and Herzegovina + value: BA + - label: BB - Barbados + value: BB + - label: BD - Bangladesh + value: BD + - label: BE - Belgium + value: BE + - label: BF - Burkina Faso + value: BF + - label: BG - Bulgaria + value: BG + - label: BH - Bahrain + value: BH + - label: BI - Burundi + value: BI + - label: BJ - Benin + value: BJ + - label: BL - Saint Barthélemy + value: BL + - label: BM - Bermuda + value: BM + - label: BN - Brunei Darussalam + value: BN + - label: BO - Bolivia (Plurinational State of) + value: BO + - label: BQ - Bonaire, Sint Eustatius and Saba + value: BQ + - label: BR - Brazil + value: BR + - label: BS - Bahamas + value: BS + - label: BT - Bhutan + value: BT + - label: BV - Bouvet Island + value: BV + - label: BW - Botswana + value: BW + - label: BY - Belarus + value: BY + - label: BZ - Belize + value: BZ + - label: CA - Canada + value: CA + - label: CC - Cocos (Keeling) Islands + value: CC + - label: CD - Congo, Democratic Republic of the + value: CD + - label: CF - Central African Republic + value: CF + - label: CG - Congo + value: CG + - label: CH - Switzerland + value: CH + - label: CI - Côte d'Ivoire + value: CI + - label: CK - Cook Islands + value: CK + - label: CL - Chile + value: CL + - label: CM - Cameroon + value: CM + - label: CN - China + value: CN + - label: CO - Colombia + value: CO + - label: CR - Costa Rica + value: CR + - label: CU - Cuba + value: CU + - label: CV - Cabo Verde + value: CV + - label: CW - Curaçao + value: CW + - label: CX - Christmas Island + value: CX + - label: CY - Cyprus + value: CY + - label: CZ - Czechia + value: CZ + - label: DE - Germany + value: DE + - label: DJ - Djibouti + value: DJ + - label: DK - Denmark + value: DK + - label: DM - Dominica + value: DM + - label: DO - Dominican Republic + value: DO + - label: DZ - Algeria + value: DZ + - label: EC - Ecuador + value: EC + - label: EE - Estonia + value: EE + - label: EG - Egypt + value: EG + - label: EH - Western Sahara + value: EH + - label: ER - Eritrea + value: ER + - label: ES - Spain + value: ES + - label: ET - Ethiopia + value: ET + - label: FI - Finland + value: FI + - label: FJ - Fiji + value: FJ + - label: FK - Falkland Islands (Malvinas) + value: FK + - label: FM - Micronesia (Federated States of) + value: FM + - label: FO - Faroe Islands + value: FO + - label: FR - France + value: FR + - label: GA - Gabon + value: GA + - label: GB - United Kingdom of Great Britain and Northern Ireland + value: GB + - label: GD - Grenada + value: GD + - label: GE - Georgia + value: GE + - label: GF - French Guiana + value: GF + - label: GG - Guernsey + value: GG + - label: GH - Ghana + value: GH + - label: GI - Gibraltar + value: GI + - label: GL - Greenland + value: GL + - label: GM - Gambia + value: GM + - label: GN - Guinea + value: GN + - label: GP - Guadeloupe + value: GP + - label: GQ - Equatorial Guinea + value: GQ + - label: GR - Greece + value: GR + - label: GT - Guatemala + value: GT + - label: GU - Guam + value: GU + - label: GW - Guinea-Bissau + value: GW + - label: GY - Guyana + value: GY + - label: HK - Hong Kong + value: HK + - label: HM - Heard Island and McDonald Islands + value: HM + - label: HN - Honduras + value: HN + - label: HR - Croatia + value: HR + - label: HT - Haiti + value: HT + - label: HU - Hungary + value: HU + - label: ID - Indonesia + value: ID + - label: IE - Ireland + value: IE + - label: IL - Israel + value: IL + - label: IM - Isle of Man + value: IM + - label: IN - India + value: IN + - label: IO - British Indian Ocean Territory + value: IO + - label: IQ - Iraq + value: IQ + - label: IR - Iran (Islamic Republic of) + value: IR + - label: IS - Iceland + value: IS + - label: IT - Italy + value: IT + - label: JE - Jersey + value: JE + - label: JM - Jamaica + value: JM + - label: JO - Jordan + value: JO + - label: JP - Japan + value: JP + - label: KE - Kenya + value: KE + - label: KG - Kyrgyzstan + value: KG + - label: KH - Cambodia + value: KH + - label: KI - Kiribati + value: KI + - label: KM - Comoros + value: KM + - label: KN - Saint Kitts and Nevis + value: KN + - label: KP - Korea (Democratic People's Republic of) + value: KP + - label: KR - Korea, Republic of + value: KR + - label: KW - Kuwait + value: KW + - label: KY - Cayman Islands + value: KY + - label: KZ - Kazakhstan + value: KZ + - label: LA - Lao People's Democratic Republic + value: LA + - label: LB - Lebanon + value: LB + - label: LC - Saint Lucia + value: LC + - label: LI - Liechtenstein + value: LI + - label: LK - Sri Lanka + value: LK + - label: LR - Liberia + value: LR + - label: LS - Lesotho + value: LS + - label: LT - Lithuania + value: LT + - label: LU - Luxembourg + value: LU + - label: LV - Latvia + value: LV + - label: LY - Libya + value: LY + - label: MA - Morocco + value: MA + - label: MC - Monaco + value: MC + - label: MD - Moldova (Republic of) + value: MD + - label: ME - Montenegro + value: ME + - label: MF - Saint Martin (French part) + value: MF + - label: MG - Madagascar + value: MG + - label: MH - Marshall Islands + value: MH + - label: MK - North Macedonia + value: MK + - label: ML - Mali + value: ML + - label: MM - Myanmar + value: MM + - label: MN - Mongolia + value: MN + - label: MO - Macao + value: MO + - label: MP - Northern Mariana Islands + value: MP + - label: MQ - Martinique + value: MQ + - label: MR - Mauritania + value: MR + - label: MS - Montserrat + value: MS + - label: MT - Malta + value: MT + - label: MU - Mauritius + value: MU + - label: MV - Maldives + value: MV + - label: MW - Malawi + value: MW + - label: MX - Mexico + value: MX + - label: MY - Malaysia + value: MY + - label: MZ - Mozambique + value: MZ + - label: NA - Namibia + value: NA + - label: NC - New Caledonia + value: NC + - label: NE - Niger + value: NE + - label: NF - Norfolk Island + value: NF + - label: NG - Nigeria + value: NG + - label: NI - Nicaragua + value: NI + - label: NL - Netherlands + value: NL + - label: NO - Norway + value: 'NO' + - label: NP - Nepal + value: NP + - label: NR - Nauru + value: NR + - label: NU - Niue + value: NU + - label: NZ - New Zealand + value: NZ + - label: OM - Oman + value: OM + - label: PA - Panama + value: PA + - label: PE - Peru + value: PE + - label: PF - French Polynesia + value: PF + - label: PG - Papua New Guinea + value: PG + - label: PH - Philippines + value: PH + - label: PK - Pakistan + value: PK + - label: PL - Poland + value: PL + - label: PM - Saint Pierre and Miquelon + value: PM + - label: PN - Pitcairn + value: PN + - label: PR - Puerto Rico + value: PR + - label: PT - Portugal + value: PT + - label: PW - Palau + value: PW + - label: PY - Paraguay + value: PY + - label: QA - Qatar + value: QA + - label: RE - Réunion + value: RE + - label: RO - Romania + value: RO + - label: RS - Serbia + value: RS + - label: RU - Russian Federation + value: RU + - label: RW - Rwanda + value: RW + - label: SA - Saudi Arabia + value: SA + - label: SB - Solomon Islands + value: SB + - label: SC - Seychelles + value: SC + - label: SD - Sudan + value: SD + - label: SE - Sweden + value: SE + - label: SG - Singapore + value: SG + - label: SH - Saint Helena + value: SH + - label: SI - Slovenia + value: SI + - label: SJ - Svalbard and Jan Mayen + value: SJ + - label: SK - Slovakia + value: SK + - label: SL - Sierra Leone + value: SL + - label: SM - San Marino + value: SM + - label: SN - Senegal + value: SN + - label: SO - Somalia + value: SO + - label: SR - Suriname + value: SR + - label: SS - South Sudan + value: SS + - label: ST - São Tomé and Príncipe + value: ST + - label: SV - El Salvador + value: SV + - label: SX - Sint Maarten (Dutch part) + value: SX + - label: SY - Syrian Arab Republic + value: SY + - label: SZ - Eswatini + value: SZ + - label: TC - Turks and Caicos Islands + value: TC + - label: TD - Chad + value: TD + - label: TF - French Southern Territories + value: TF + - label: TG - Togo + value: TG + - label: TH - Thailand + value: TH + - label: TJ - Tajikistan + value: TJ + - label: TK - Tokelau + value: TK + - label: TL - Timor-Leste + value: TL + - label: TM - Turkmenistan + value: TM + - label: TN - Tunisia + value: TN + - label: TO - Tonga + value: TO + - label: TR - Turkey + value: TR + - label: TT - Trinidad and Tobago + value: TT + - label: TV - Tuvalu + value: TV + - label: TZ - Tanzania, United Republic of + value: TZ + - label: UA - Ukraine + value: UA + - label: UG - Uganda + value: UG + - label: UM - United States Minor Outlying Islands + value: UM + - label: UN - United Nations + value: UN + - label: US - United States of America + value: US + - label: UY - Uruguay + value: UY + - label: UZ - Uzbekistan + value: UZ + - label: VA - Holy See + value: VA + - label: VC - Saint Vincent and the Grenadines + value: VC + - label: VE - Venezuela (Bolivarian Republic of) + value: VE + - label: VG - Virgin Islands (British) + value: VG + - label: VI - Virgin Islands (U.S.) + value: VI + - label: VN - Viet Nam + value: VN + - label: VU - Vanuatu + value: VU + - label: WF - Wallis and Futuna + value: WF + - label: WS - Samoa + value: WS + - label: YE - Yemen + value: YE + - label: YT - Mayotte + value: YT + - label: ZA - South Africa + value: ZA + - label: ZM - Zambia + value: ZM + - label: ZW - Zimbabwe + value: ZW + dynamic: false + allowNull: false + - id: sUo41fnvoZWkDHA1TiDDqa + sortOrder: 3 fieldKey: list_id label: List Id type: STRING @@ -73252,8 +76306,8 @@ items: choices: null dynamic: true allowNull: false - - id: cMbHiQqpaqTDqt53LYkc48 - sortOrder: 3 + - id: vnCA1kazvNt4E8NH4PPqcr + sortOrder: 4 fieldKey: enable_batching label: Batch Data to Klaviyo type: BOOLEAN diff --git a/src/_data/catalog/destinations_private.yml b/src/_data/catalog/destinations_private.yml index 97398405ff..4869e4029e 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-15 +# destination data last updated 2024-10-17 items: - id: 54521fd925e721e32a72eee1 display_name: Pardot diff --git a/src/_data/catalog/source_categories.yml b/src/_data/catalog/source_categories.yml index c219c8848f..b81a003531 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-15 +# source categories last updated 2024-10-17 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 1e0f1fefb2..67d447c702 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-15 +# sources last updated 2024-10-17 items: - id: 8HWbgPTt3k display_name: .NET