From 99af894cbf8db6e98f1a823f968f9803e3abb178 Mon Sep 17 00:00:00 2001 From: KC Ong Date: Thu, 30 Oct 2025 16:38:29 +0800 Subject: [PATCH 1/5] add taguchi action destination docs --- .../catalog/actions-taguchi/index.md | 37 +++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 src/connections/destinations/catalog/actions-taguchi/index.md diff --git a/src/connections/destinations/catalog/actions-taguchi/index.md b/src/connections/destinations/catalog/actions-taguchi/index.md new file mode 100644 index 0000000000..27443e95a5 --- /dev/null +++ b/src/connections/destinations/catalog/actions-taguchi/index.md @@ -0,0 +1,37 @@ +--- +title: Taguchi (Actions)Destination +--- + +{% include content/plan-grid.md name="actions" %} + +[Taguchi](https://taguchi.com.au){:target="_blank”} is a distributed customer engagement platform that allows you to communicate with your customers the way you’ve always wanted, but never thought you could. We offer advanced solutions across various industries, including digital marketing, customer engagement, loyalty, marketing automation, customer re-targeting campaigns, and local area digital marketing + +This destination is maintained by Taguchi. For any issues with the destination, [contact their Support team](mailto:support@taguchi.com). + + +## Getting started + +1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog) search for "taguchi". +2. Select taguchi and click **Add Destination**. +3. Select an existing Source to connect to Taguchi (Actions). +4. Go to the [Taguchi credential dashboard](https://login.taguchi.com.au//settings/credentials), add and copy this new credential **API key** to be used in APIv5 integration for Segment. +5. Enter the **API Key** in the Taguchi destination settings in Segment. +6. Go to the [Taguchi integration dashboard](https://login.taguchi.com.au//settings/integration), and proceed to create a new integration. +- Fill in appropriate IntegrationName +- select API: V5 endpoint(authenticated) type +- Select the newly created credential in step 4 in the credential to use drop down +- Select the External ID (ref) in the identify profiles by drop down +- Tick the required and appropriate checkboxes +- Once the above steps are completed, proceed to save and activate this newly created integration +7. Copy the ***Production Endpoint URL*** in the integration created in the previous step to the Taguchi destination settings in Segment +8. Fill in the organization ID found in taguchi dashboard to the ***Organization ID*** field in the Taguchi destination settings in Segment. + +{% include components/actions-fields.html settings="true" %} + +## Identify (Sync User Profile) +1. To sync identify profiles from segment to Taguchi, we will select ***Sync User Profile*** in the set up mapping. +2. Select ***event type*** is ***Identify*** in the define event trigger section where each of the user recorded traits on Segment will be mapped to the corresponding Taguchi fields and send to Taguchi as subscriber profile. + +## Track (Sync Event) +1. To sync identify profiles actions from segment to Taguchi, we will select ***Sync Event*** in the set up mapping. +2. Select ***event type*** is ***Track*** in the define event trigger section where each of the user recorded action on Segment will be mapped to the corresponding Taguchi fields and send to Taguchi as subscriber event. \ No newline at end of file From 2b8392b7080baf78e1b56d3372ccbc0f1a88cb84 Mon Sep 17 00:00:00 2001 From: Sharon Adewusi Date: Thu, 30 Oct 2025 12:45:25 +0000 Subject: [PATCH 2/5] Revisions to fit Seg style Updated the Taguchi (Actions) destination documentation for clarity and consistency. Revised text and formatting for better readability. --- .../catalog/actions-taguchi/index.md | 56 +++++++++++-------- 1 file changed, 34 insertions(+), 22 deletions(-) diff --git a/src/connections/destinations/catalog/actions-taguchi/index.md b/src/connections/destinations/catalog/actions-taguchi/index.md index 27443e95a5..1a24856be1 100644 --- a/src/connections/destinations/catalog/actions-taguchi/index.md +++ b/src/connections/destinations/catalog/actions-taguchi/index.md @@ -1,37 +1,49 @@ --- -title: Taguchi (Actions)Destination +title: Taguchi (Actions) Destination +id: 68b6ddcd033b3f6d006d8e1f +beta: true --- {% include content/plan-grid.md name="actions" %} -[Taguchi](https://taguchi.com.au){:target="_blank”} is a distributed customer engagement platform that allows you to communicate with your customers the way you’ve always wanted, but never thought you could. We offer advanced solutions across various industries, including digital marketing, customer engagement, loyalty, marketing automation, customer re-targeting campaigns, and local area digital marketing - -This destination is maintained by Taguchi. For any issues with the destination, [contact their Support team](mailto:support@taguchi.com). +[Taguchi](https://taguchi.com.au){:target="_blank”} is a distributed customer engagement platform designed to help you communicate with customers. Taguchi provides tools for digital marketing, customer engagement, loyalty, marketing automation, targeting campaigns, and localized digital marketing. +This destination is maintained by Taguchi. For any issues with the destination, [contact the Taguchi support team](mailto:support@taguchi.com){:target="_blank”}. ## Getting started -1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog) search for "taguchi". -2. Select taguchi and click **Add Destination**. -3. Select an existing Source to connect to Taguchi (Actions). -4. Go to the [Taguchi credential dashboard](https://login.taguchi.com.au//settings/credentials), add and copy this new credential **API key** to be used in APIv5 integration for Segment. -5. Enter the **API Key** in the Taguchi destination settings in Segment. -6. Go to the [Taguchi integration dashboard](https://login.taguchi.com.au//settings/integration), and proceed to create a new integration. -- Fill in appropriate IntegrationName -- select API: V5 endpoint(authenticated) type -- Select the newly created credential in step 4 in the credential to use drop down -- Select the External ID (ref) in the identify profiles by drop down -- Tick the required and appropriate checkboxes -- Once the above steps are completed, proceed to save and activate this newly created integration -7. Copy the ***Production Endpoint URL*** in the integration created in the previous step to the Taguchi destination settings in Segment -8. Fill in the organization ID found in taguchi dashboard to the ***Organization ID*** field in the Taguchi destination settings in Segment. +1. In your Segment workspace, go to the [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog) and search for "Taguchi". +2. Select the Taguchi (Actions) destination and click **Add Destination**. +3. Select an existing source to connect to Taguchi (Actions). +4. Go to the [Taguchi credential dashboard](https://login.taguchi.com.au//settings/credentials){:target="_blank”}. Create a new credential and copy the **API key**. +5. In Segment, paste the **API Key** in the Taguchi destination settings. +6. Next, go to the [Taguchi integration dashboard](https://login.taguchi.com.au//settings/integration){:target="_blank”} and create a new integration. +7. Configure the integration: +- Give it an appropriate `IntegrationName`. +- Select API: **V5 endpoint (authenticated)** type. +- Select the credential in Step 4 from the credential dropdown. +- Select the **External ID (ref)** option in the Identify Profiles dropdown. +- Enable the required checkboxes. +8. Save and activate the integration. +9. Copy the **Production Endpoint URL** from Taguchi. Return to Segment and paste the **Production Endpoint URL** in the Taguchi destination settings. +10. Enter the **Organization ID** (found in the Taguchi dashboard). {% include components/actions-fields.html settings="true" %} ## Identify (Sync User Profile) -1. To sync identify profiles from segment to Taguchi, we will select ***Sync User Profile*** in the set up mapping. -2. Select ***event type*** is ***Identify*** in the define event trigger section where each of the user recorded traits on Segment will be mapped to the corresponding Taguchi fields and send to Taguchi as subscriber profile. + +Use [Identify](docs/connections/spec/identify) calls to sync user profile data toTaguchi. When configuring mappings in the destination setup: + +1. Select **Sync User Profile**. +2. Define the **Event type** as **Identify**. + +Segment maps user traits to corresponding Taguchi fields, sending them to Taguchi as a subscriber profile. ## Track (Sync Event) -1. To sync identify profiles actions from segment to Taguchi, we will select ***Sync Event*** in the set up mapping. -2. Select ***event type*** is ***Track*** in the define event trigger section where each of the user recorded action on Segment will be mapped to the corresponding Taguchi fields and send to Taguchi as subscriber event. \ No newline at end of file + +Use [Track](docs/connections/spec/track/) call to sync event data to Taguchi. When configuring mappings in the destination setup: + +1. Select **Sync Event**. +2. Define the **Event type*** as **Track**. + +Segment maps user actions to corresponding Taguchi fields, sending them to Taguchi as subscriber events. From 57b659c6d620d9c9a089914449d9ca9543d4c742 Mon Sep 17 00:00:00 2001 From: Sharon Adewusi Date: Thu, 30 Oct 2025 12:46:05 +0000 Subject: [PATCH 3/5] Fix typo --- src/connections/destinations/catalog/actions-taguchi/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/actions-taguchi/index.md b/src/connections/destinations/catalog/actions-taguchi/index.md index 1a24856be1..642b6a38f8 100644 --- a/src/connections/destinations/catalog/actions-taguchi/index.md +++ b/src/connections/destinations/catalog/actions-taguchi/index.md @@ -41,7 +41,7 @@ Segment maps user traits to corresponding Taguchi fields, sending them to Taguch ## Track (Sync Event) -Use [Track](docs/connections/spec/track/) call to sync event data to Taguchi. When configuring mappings in the destination setup: +Use [Track](docs/connections/spec/track/) calls to sync event data to Taguchi. When configuring mappings in the destination setup: 1. Select **Sync Event**. 2. Define the **Event type*** as **Track**. From efc18282fc9e3df0d99c86dd1b9d52adad584f9b Mon Sep 17 00:00:00 2001 From: Sharon Adewusi Date: Thu, 30 Oct 2025 12:47:16 +0000 Subject: [PATCH 4/5] Fix typo [netlify-build] --- src/connections/destinations/catalog/actions-taguchi/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/actions-taguchi/index.md b/src/connections/destinations/catalog/actions-taguchi/index.md index 642b6a38f8..dad4f2209b 100644 --- a/src/connections/destinations/catalog/actions-taguchi/index.md +++ b/src/connections/destinations/catalog/actions-taguchi/index.md @@ -32,7 +32,7 @@ This destination is maintained by Taguchi. For any issues with the destination, ## Identify (Sync User Profile) -Use [Identify](docs/connections/spec/identify) calls to sync user profile data toTaguchi. When configuring mappings in the destination setup: +Use [Identify](docs/connections/spec/identify) calls to sync user profile data to Taguchi. When configuring mappings in the destination setup: 1. Select **Sync User Profile**. 2. Define the **Event type** as **Identify**. From 6380a4004dcd1584822509682f243737b3f72a24 Mon Sep 17 00:00:00 2001 From: Sharon Adewusi Date: Thu, 30 Oct 2025 12:54:39 +0000 Subject: [PATCH 5/5] preening --- src/connections/destinations/catalog/actions-taguchi/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/connections/destinations/catalog/actions-taguchi/index.md b/src/connections/destinations/catalog/actions-taguchi/index.md index dad4f2209b..d53bc753a8 100644 --- a/src/connections/destinations/catalog/actions-taguchi/index.md +++ b/src/connections/destinations/catalog/actions-taguchi/index.md @@ -19,7 +19,7 @@ This destination is maintained by Taguchi. For any issues with the destination, 5. In Segment, paste the **API Key** in the Taguchi destination settings. 6. Next, go to the [Taguchi integration dashboard](https://login.taguchi.com.au//settings/integration){:target="_blank”} and create a new integration. 7. Configure the integration: -- Give it an appropriate `IntegrationName`. +- Give it an appropriate Integration name. - Select API: **V5 endpoint (authenticated)** type. - Select the credential in Step 4 from the credential dropdown. - Select the **External ID (ref)** option in the Identify Profiles dropdown. @@ -44,6 +44,6 @@ Segment maps user traits to corresponding Taguchi fields, sending them to Taguch Use [Track](docs/connections/spec/track/) calls to sync event data to Taguchi. When configuring mappings in the destination setup: 1. Select **Sync Event**. -2. Define the **Event type*** as **Track**. +2. Define the **Event type** as **Track**. Segment maps user actions to corresponding Taguchi fields, sending them to Taguchi as subscriber events.