Talon.One (Actions) Destination

Destination Info

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.

Good to know: This page is about the Actions-framework Talon.One Segment destination. There’s also a page about the non-Actions Talon.One destination. Both of these destinations receive data from Segment.

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.

Important: You might need to create custom attributes in Talon.One to be able to map the data from Segment in Talon.One. See the Talon.One docs.

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

Setting Description
API Key Required.

Created under Developer Settings in the Talon.One Campaign Manager.

Deployment Required.

The base URL of your Talon.One deployment.

Available Actions

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

Mapping limits per destination

Individual destination instances have support a maximum of 50 mappings.

Update Customer Sessions

This updates a customer session.

Update Customer Sessions is a Cloud action.

Click to show / hide fields

Field Description
Customer Session ID* Type: STRING

The customer session integration identifier to use in Talon.One.

Callback Destination URI Type: STRING

This specifies the address of the service and its endpoint to do callback request.

Callback API Key Type: STRING

This specifies API key and relative header. The header is specified optionally

Content Fields Type: STRING

This specifies a list of the fields from the response you need to receive. Comma character is separator. If omitted, all the fields will be forwarded from the response to the callback destination.

Correlation ID Type: STRING

This specifies ID of the request that will be forwarded to the destination URI with the callback request with the same header name. If omitted, the X-Correlation-ID will not be in the callback request.

Customer Session Data* Type: OBJECT

This contains all the data related to customer session.

Session Attributes info Type: OBJECT

Use this field if you want to identify a session attribute with a specific type

Cart Items Attributes info Type: OBJECT

Use this field if you want to identify a cart item attribute with a specific type

Create Audience

This creates a new audience entity in Talon.One.

Create Audience is a Cloud action.

Click to show / hide fields

Field Description
Segment Audience ID* Type: STRING

You should get this audience ID from Segment.

Audience Name* Type: STRING

You should get this audience name from Segment.

Track Event

This records a custom event in Talon.One.

Track Event is a Cloud action.

Click to show / hide fields

Field Description
Customer Profile ID* Type: STRING

The customer profile integration ID to use in Talon.One. It is the identifier of the customer profile associated to the event.

Event Type* Type: STRING

The name of the event sent to Talon.One.

Type* Type: STRING

Type of event. Can be only string, time, number, boolean, location

Attribute-Value pairs Type: OBJECT

Extra attributes associated with the event. See more info.

Attributes info Type: OBJECT

Use this field if you want to identify an attribute with a specific type

Update Customer Profile

This updates attributes and audiences for a single customer profile.

Update Customer Profile is a Cloud action.

Click to show / hide fields

Field Description
Attribute-Value pairs Type: OBJECT

Extra attributes associated with the customer profile. See more info.

Customer Profile ID* Type: STRING

The customer profile integration identifier to use in Talon.One.

List of audience ID to dissociate with the customer profile. Type: INTEGER

You should get these audience IDs from Talon.One.

List of audience ID to associate with the customer profile. Type: INTEGER

You should get these audience IDs from Talon.One.

Run rule engine Type: BOOLEAN

This runs rule engine in Talon.One upon updating customer profile. Set to true to trigger rules. Setting this property to false improves response times. For audiences changes the runRuleEngine should be true. Default value is false.

Attributes with types Type: OBJECT

Use this field if you want to identify an attribute with a specific type

Delete Audience

This deletes the audience entity in Talon.One.

Delete Audience is a Cloud action.

Click to show / hide fields

Field Description
Segment Audience ID* Type: STRING

You should get this audience ID from Segment.

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

Field Description
Data item to change customer profile attributes* Type: OBJECT

An array of JSON objects that contains customer profile identifier and list of attributes and their values. Customer profile ID is required.

Mutual Attribute-Value pairs Type: OBJECT

This may contain mutual list of attributes and their values for every customer profile in the “data” array.

Attributes with types Type: OBJECT

Use this field if you want to identify an attribute with a specific type

Update Customer Profile V2

You do not have to create attributes or audiences before using this endpoint.

Update Customer Profile V2 is a Cloud action.

Click to show / hide fields

Field Description
Customer Profile ID* Type: STRING

The customer profile integration identifier to use in Talon.One.

The audiences for the customer to join. Type: OBJECT

Audience name and integration ID

The audiences for the customer to leave. Type: OBJECT

Audience name and integration ID

Run rule engine Type: BOOLEAN

This runs rule engine in Talon.One upon updating customer profile. Set to true to trigger rules.

Attribute-Value pairs Type: OBJECT

Extra attributes associated with the customer profile. See more info.

Attributes info Type: OBJECT

Use this field if you want to identify an attribute with a specific type

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

Field Description
Segment Audience ID* Type: STRING

You should get this audience ID from Segment.

Audience Name* Type: STRING

You should get this audience name from Segment.

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

Field Description
Data item to change customer profile audiences* Type: OBJECT

An array of JSON objects that contains customer profile identifier and list of audiences to associate and dissociate with the indicated customer profile. Customer profile ID and at least one audience ID are required.

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.

This page was last modified: 10 May 2022



Get started with Segment

Segment is the easiest way to integrate your websites & mobile apps data to over 300 analytics and growth tools.
or
Create free account