Talon.One (Actions) Destination

Create flexible and targeted promotional and loyalty campaigns with Talon.One. Campaigns can be created and managed by non-technical users like marketers. There is no need to get your development team involved. Features include coupons, discounts, loyalty programs, referral tracking, geofencing, and bundling.

This destination is maintained by Talon.One. For any issues with the destination, contact the Talon.One Support team or refer to Talon.One’s documentation.

Benefits of Talon.One (Actions) vs Talon.One Classic

Talon.One (Actions) allows you to share more data than the classic destination. The classic version only shares customer profile data. The Action version supports sharing the following data:

• Customer profile data
• Audience data
• Tracking events

Getting started

Creating an API key in Talon.One

Segment needs a Talon.One-generated API key to be able to send data to your Talon.One Application. To generate an API key specific to Segment:

1. Open your Talon.One Application in the Campaign Manager and click Settings > Developer settings.
2. Click Create API Key.
3. For Do you want to use this API Key with a 3rd party service, select Yes.
4. Select Segment from the dropdown.
5. Select an expiry date and click Create API Key.
6. Copy it for later use.

Adding a Talon.One destination

To start sending data to Talon.One from Segment, create a Talon.One destination in Segment.

1. In Segment, click Destinations > Add Destination. The Destination catalog opens.
2. Search for Talon.one and configure the destination.
3. Enter the details:
   • In Name, type a name, for example Talon.One destination.
   • In API key, paste the API key generated in the previous section.
   • In Deployment, type the URI of your Talon.One deployment, for example https://mycompany.europe-west1.talon.one/.
4. (Optional) Set up your filters.
5. Configure the mapping:
   1. Click New Mapping and select the type of action to perform in Talon.One. For example When a new audience is created in Segment, also create it in Talon.One.
   2. Configure the trigger and action fields.
6. Click Event Tester and test if you received the data in Talon.One.

Once you receive data, you can start creating rules that rely on that data.

Testing the integration

You can use the following payloads to test and fine-tune your requests.

{
  "messageId": "segment-test-message-t1kx8e",
  "timestamp": "2022-03-22T12:41:20.918Z",
  "type": "track", // or any other type in Segment
  "userId": "test-user-z65zqk",
  "event": "track-event", // or any other event in Segment
  "email": "test@example.org",
  "projectId": "qR6APLKpCBB3ue8pHkBLpo",
  "properties": {
    "eventType": "mySegmentEvent",
    "type": "boolean",
    "customerProfileId": "a_customer_id",
    "attributes": {
      "language": "English" // depends your custom attributes in Talon.One
    }
  }
}

Next steps

Once you receive data from Segment inside Talon.One, start creating your rules in the Campaign Manager. See the Talon.One documentation.

Destination Settings

Available Actions

Build your own Mappings. Combine supported triggers with the following Talon.One-supported actions:

• Create Audience

• [Deprecated] Track event

• [Deprecated] Upsert customer profile

• Delete Audience

• Update Multiple Customer Profiles’ Attributes

• Update Audience Name

• Update Multiple Customer Profiles’ Audiences

• [Deprecated] Update customer session

• [Deprecated] Upsert customer profile V2

• Track event

• Update customer profile

• Update customer session

Create Audience

This creates a new audience entity in Talon.One.

Create Audience is a Cloud action.

Click to show / hide fields

[Deprecated] Track event

This records a custom event in Talon.One. Important: This Action is deprecated. Use the Track event Action instead.

[Deprecated] Track event is a Cloud action.

Click to show / hide fields

[Deprecated] Upsert customer profile

This updates attributes and audiences for a single customer profile. Important: This Action is deprecated. Use the Update customer profile Action instead.

[Deprecated] Upsert customer profile is a Cloud action.

Click to show / hide fields

Delete Audience

This deletes the audience entity in Talon.One.

Delete Audience is a Cloud action.

Click to show / hide fields

Update Multiple Customer Profiles’ Attributes

This updates attributes for multiple customer profiles.

Update Multiple Customer Profiles’ Attributes is a Cloud action.

Click to show / hide fields

Update Audience Name

This updates the audience name if there is an existing audience entity.

Update Audience Name is a Cloud action.

Click to show / hide fields

Update Multiple Customer Profiles’ Audiences

This updates audiences for multiple customer profiles.

Update Multiple Customer Profiles’ Audiences is a Cloud action.

Click to show / hide fields

[Deprecated] Update customer session

This updates a customer session. Important: This Action is deprecated. Use the Update customer session Action instead.

[Deprecated] Update customer session is a Cloud action.

Click to show / hide fields

[Deprecated] Upsert customer profile V2

You do not have to create attributes or audiences before using this Action. Important: This Action is deprecated. Use the Update customer profile Action instead.

[Deprecated] Upsert customer profile V2 is a Cloud action.

Click to show / hide fields

Track event

This records a custom event in Talon.One. Create the event and all the required attributes before using this Action.

Track event is a Cloud action.

Click to show / hide fields

Update customer profile

This updates attributes and audiences for a single customer profile. Create all the required attributes and audiences before using this Action.

Update customer profile is a Cloud action.

Click to show / hide fields

Update customer session

This updates a customer session. Create all the required attributes before using this Action.

Update customer session is a Cloud action.

Click to show / hide fields

Migration from the classic Talon.One destination

To prevent duplicate events being created in Talon.One, ensure that for each Segment source, this destination and the classic Talon.One destination are not both enabled at the same time.