Skip to content

Commit 6380a40

Browse files
authored
preening
1 parent efc1828 commit 6380a40

File tree

1 file changed

+2
-2
lines changed
  • src/connections/destinations/catalog/actions-taguchi

1 file changed

+2
-2
lines changed

src/connections/destinations/catalog/actions-taguchi/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ This destination is maintained by Taguchi. For any issues with the destination,
1919
5. In Segment, paste the **API Key** in the Taguchi destination settings.
2020
6. Next, go to the [Taguchi integration dashboard](https://login.taguchi.com.au/<organization>/settings/integration){:target="_blank”} and create a new integration.
2121
7. Configure the integration:
22-
- Give it an appropriate `IntegrationName`.
22+
- Give it an appropriate Integration name.
2323
- Select API: **V5 endpoint (authenticated)** type.
2424
- Select the credential in Step 4 from the credential dropdown.
2525
- 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
4444
Use [Track](docs/connections/spec/track/) calls to sync event data to Taguchi. When configuring mappings in the destination setup:
4545

4646
1. Select **Sync Event**.
47-
2. Define the **Event type*** as **Track**.
47+
2. Define the **Event type** as **Track**.
4848

4949
Segment maps user actions to corresponding Taguchi fields, sending them to Taguchi as subscriber events.

0 commit comments

Comments
 (0)