--- "@context": https://schema.org "@type": TechArticle "@id": https://www.twilio.com/docs/segment/connections/destinations/catalog/actions-taguchi#article headline: Taguchi (Actions) Destination description: Connect the Taguchi (Actions) destination to sync user profiles and events from Twilio Segment to Taguchi for customer engagement and marketing automation. url: https://www.twilio.com/docs/segment/connections/destinations/catalog/actions-taguchi inLanguage: en dateModified: 2026-06-09T02:36:11.000Z author: "@type": Organization name: Twilio Developer Education Team publisher: "@type": Organization name: Twilio --- # Taguchi (Actions) Destination > \[!IMPORTANT] > > This feature is in active development and may change before general availability. ## Destination Info * Accepts [Page](/docs/segment/connections/spec/page), [Alias](/docs/segment/connections/spec/alias), [Group](/docs/segment/connections/spec/group), [Identify](/docs/segment/connections/spec/identify), [Track](/docs/segment/connections/spec/track) calls. * Refer to it as **Taguchi** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object) * This integration is **partner owned.** Please reach out to the partner's support for any issues. * This destination is **Beta.** [Taguchi](https://taguchi.com.au) 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). ## Getting started 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). 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) and create a new integration. 7. Configure the integration: * 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. * 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). ## Destination Settings | Field | Description | Required | Type | | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | -------- | | API Key | Taguchi API Key used to authenticate requests to the Taguchi platform. | Yes | password | | Integration URL | The Taguchi URL Segment will send data to. This should be created in the Taguchi User Interface by navigating to 'Taguchi Integrations' then 'Integrations Setup.' | Yes | string | | Organization ID | The Taguchi ID of the organization to which this Subscriber belongs. | Yes | string | ## Available Actions Build your own Mappings. Combine supported [triggers](/docs/segment/connections/destinations/actions/#components-of-a-destination-action) with the following Taguchi-supported actions: > \[!NOTE] > > Individual destination instances support a maximum of 5 mappings. * [Sync Event](#sync-event) * [Sync User Profile](#sync-user-profile) ### Sync Event Sync ecommerce events to Taguchi. Sync Event is a **Cloud** action. | Field | Description | Required | Type | | ---------------- | --------------------------------------------------------------------------------------- | -------- | ------- | | Event Target | Target identifier / user identifier for the event. At least one identifier is required. | Yes | OBJECT | | Event Type | Type of event being sent. | Yes | STRING | | Event Data | Ecommerce event data including total and products. | No | OBJECT | | Products | Array of products in the transaction. | No | OBJECT | | Enable Batching? | When enabled, Segment will send events in batches. | No | BOOLEAN | ### Sync User Profile Sync user profile details to Taguchi, and add / remove users from Taguchi Lists. Sync User Profile is a **Cloud** action. | Field | Description | Required | Type | | ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | | Subscriber Identifiers | At least one identifier is required. Any identifiers sent will then become required for future updates to that Subscriber. | Yes | OBJECT | | Traits | Standard traits for the Subscriber. All text fields. No specific formats for any of them. | No | OBJECT | | Timestamp | The timestamp of the event in ISO 8601 format (YYYY-MM-DDTHH:mm:ssZ). Defaults to the current time if not provided. | Yes | STRING | | Lists to subscribe to | An array of numeric Taguchi List IDs to subscribe the Subscriber to. Leave this field empty if syncing an Audience from Engage. | No | NUMBER | | Lists to unsubscribe from | An array of numeric Taguchi List IDs to unsubscribe the Subscriber from. Leave this field empty if syncing an Audience from Engage. | No | NUMBER | | Enable Batching? | When enabled, Segment will send events in batches. | No | BOOLEAN | ## Identify (Sync User Profile) Use [Identify](/docs/segment/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**. Segment maps user traits to corresponding Taguchi fields, sending them to Taguchi as a subscriber profile. ## Track (Sync Event) Use [Track](/docs/segment/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**. Segment maps user actions to corresponding Taguchi fields, sending them to Taguchi as subscriber events. ## Engage You can send computed traits and audiences generated using [Engage](/docs/segment/engage) to this destination as a **user property**. To learn more about Engage, schedule a [demo](https://segment.com/contact/demo). For user-property destinations, an [identify](/docs/segment/connections/spec/identify/) call is sent to the destination for each user being added and removed. The property name is the snake\_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property `order_completed_last_30days: true`. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to `false`. When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync. ## Settings Segment lets you change these destination settings from the Segment app without having to touch any code. | Field | Description | Required | Type | | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | -------- | | API Key | Taguchi API Key used to authenticate requests to the Taguchi platform. | Yes | password | | Integration URL | The Taguchi URL Segment will send data to. This should be created in the Taguchi User Interface by navigating to 'Taguchi Integrations' then 'Integrations Setup.' | Yes | string | | Organization ID | The Taguchi ID of the organization to which this Subscriber belongs. | Yes | string |