Taguchi (Actions) Destination
Beta
This feature is in active development and may change before general availability.
Taguchi 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.
- In your Segment workspace, go to the Destination catalog page and search for "Taguchi".
- Select the Taguchi (Actions) destination and click Add Destination.
- Select an existing source to connect to Taguchi (Actions).
- Go to the Taguchi credential dashboard. Create a new credential and copy the API key.
- In Segment, paste the API Key in the Taguchi destination settings.
- Next, go to the Taguchi integration dashboard and create a new integration.
- 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.
- Save and activate the integration.
- Copy the Production Endpoint URL from Taguchi. Return to Segment and paste the Production Endpoint URL in the Taguchi destination settings.
- Enter the Organization ID (found in the Taguchi dashboard).
Taguchi API Key used to authenticate requests to the Taguchi platform.
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.'
The Taguchi ID of the organization to which this Subscriber belongs.
Build your own Mappings. Combine supported triggers with the following Taguchi-supported actions:
Mapping limits per destination
Individual destination instances support a maximum of 5 mappings.
Sync ecommerce events to Taguchi.
Sync Event is a Cloud action.
Target identifier / user identifier for the event. At least one identifier is required.
Type of event being sent.
Optional
Ecommerce event data including total and products.
Optional
Array of products in the transaction.
Optional
When enabled, Segment will send events in batches.
Sync user profile details to Taguchi, and add / remove users from Taguchi Lists.
Sync User Profile is a Cloud action.
At least one identifier is required. Any identifiers sent will then become required for future updates to that Subscriber.
Optional
Standard traits for the Subscriber. All text fields. No specific formats for any of them.
The timestamp of the event in ISO 8601 format (YYYY-MM-DDTHH:mm:ssZ). Defaults to the current time if not provided.
Optional
An array of numeric Taguchi List IDs to subscribe the Subscriber to. Leave this field empty if syncing an Audience from Engage.
Optional
An array of numeric Taguchi List IDs to unsubscribe the Subscriber from. Leave this field empty if syncing an Audience from Engage.
Optional
When enabled, Segment will send events in batches.
Use Identify calls to sync user profile data to Taguchi. When configuring mappings in the destination setup:
- Select Sync User Profile.
- Define the Event type as Identify.
Segment maps user traits to corresponding Taguchi fields, sending them to Taguchi as a subscriber profile.
Use Track calls to sync event data to Taguchi. When configuring mappings in the destination setup:
- Select Sync Event.
- Define the Event type as Track.
Segment maps user actions to corresponding Taguchi fields, sending them to Taguchi as subscriber events.
You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.
For user-property destinations, an 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.
Segment lets you change these destination settings from the Segment app without having to touch any code.
Taguchi API Key used to authenticate requests to the Taguchi platform.
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.'
The Taguchi ID of the organization to which this Subscriber belongs.