Skip to contentSkip to navigationSkip to topbar
On this page
Looking for more inspiration?Visit the
(information)
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

Talon.One (Actions) Destination


Destination Info
  • Accepts Page, Alias, Group, Identify and Track calls.
  • Refer to it as Talon.One (Actions) in the Integrations object
  • This integration is partner owned. Please reach out to the partner's support for any issues.

Create flexible and targeted promotional and loyalty campaigns with Talon.One(link takes you to an external page). 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(link takes you to an external page).

(success)

Success!

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

benefits-of-talonone-actions-vs-talonone-classic page anchor

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

Creating an API key in Talon.One

creating-an-api-key-in-talonone page anchor

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.
(information)

Talon.One API Rate Limit

Talon.One limits integrations with Segment to 60 requests per second for any given client, regardless of the endpoint. To increase this limit, contact Talon.One.

Adding a Talon.One destination

adding-a-talonone-destination page anchor

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.

(warning)

Warning

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(link takes you to an external page).

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

1
{
2
"messageId": "segment-test-message-t1kx8e",
3
"timestamp": "2022-03-22T12:41:20.918Z",
4
"type": "track", // or any other type in Segment
5
"userId": "test-user-z65zqk",
6
"event": "track-event", // or any other event in Segment
7
"email": "test@example.org",
8
"projectId": "qR6APLKpCBB3ue8pHkBLpo",
9
"properties": {
10
"eventType": "mySegmentEvent",
11
"type": "boolean",
12
"customerProfileId": "a_customer_id",
13
"attributes": {
14
"language": "English" // depends your custom attributes in Talon.One
15
}
16
}
17
}

Once you receive data from Segment inside Talon.One, start creating your rules in the Campaign Manager. See the Talon.One documentation(link takes you to an external page).


Property nameTypeRequiredDescription
API Keystring
required

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


Deploymentstring
required

The base URL of your Talon.One deployment.


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

(information)

Mapping limits per destination

Individual destination instances have support a maximum of 50 mappings.

This creates a new audience entity in Talon.One.

Create Audience is a Cloud action.

Property nameTypeRequiredDescription
Segment Audience IDSTRING
required

You should get this audience ID from Segment.


Audience NameSTRING
required

You should get this audience name from Segment.

[Deprecated] Track event

deprecated-track-event page anchor

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.

Property nameTypeRequiredDescription
Customer Profile IDSTRING
required

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


Event TypeSTRING
required

The name of the event sent to Talon.One.


TypeSTRING
required

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


Attribute-Value pairsOBJECT

Optional

Extra attributes associated with the event. See more info(link takes you to an external page).


Attributes infoOBJECT

Optional

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

[Deprecated] Upsert customer profile

deprecated-upsert-customer-profile page anchor

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.

Property nameTypeRequiredDescription
Attribute-Value pairsOBJECT

Optional

Extra attributes associated with the customer profile. See more info(link takes you to an external page).


Customer Profile IDSTRING
required

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


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

Optional

You should get these audience IDs from Talon.One.


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

Optional

You should get these audience IDs from Talon.One.


Run rule engineBOOLEAN

Optional

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 typesOBJECT

Optional

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

This deletes the audience entity in Talon.One.

Delete Audience is a Cloud action.

Property nameTypeRequiredDescription
Segment Audience IDSTRING
required

You should get this audience ID from Segment.

Update Multiple Customer Profiles’ Attributes

update-multiple-customer-profiles-attributes page anchor

This updates attributes for multiple customer profiles.

Update Multiple Customer Profiles’ Attributes is a Cloud action.

Property nameTypeRequiredDescription
Data item to change customer profile attributesOBJECT
required

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 pairsOBJECT

Optional

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


Attributes with typesOBJECT

Optional

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

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

Update Audience Name is a Cloud action.

Property nameTypeRequiredDescription
Segment Audience IDSTRING
required

You should get this audience ID from Segment.


Audience NameSTRING
required

You should get this audience name from Segment.

Update Multiple Customer Profiles’ Audiences

update-multiple-customer-profiles-audiences page anchor

This updates audiences for multiple customer profiles.

Update Multiple Customer Profiles’ Audiences is a Cloud action.

Property nameTypeRequiredDescription
Data item to change customer profile audiencesOBJECT
required

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.

[Deprecated] Update customer session

deprecated-update-customer-session page anchor

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.

Property nameTypeRequiredDescription
Customer Session IDSTRING
required

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


Callback Destination URISTRING

Optional

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


Callback API KeySTRING

Optional

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


Content FieldsSTRING

Optional

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 IDSTRING

Optional

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 DataOBJECT
required

This contains all the data related to customer session.


Session Attributes infoOBJECT

Optional

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


Cart Items Attributes infoOBJECT

Optional

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

[Deprecated] Upsert customer profile V2

deprecated-upsert-customer-profile-v2 page anchor

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.

Property nameTypeRequiredDescription
Customer Profile IDSTRING
required

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


The audiences for the customer to join.OBJECT

Optional

Audience name and integration ID


The audiences for the customer to leave.OBJECT

Optional

Audience name and integration ID


Run rule engineBOOLEAN

Optional

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


Attribute-Value pairsOBJECT

Optional

Extra attributes associated with the customer profile. See more info(link takes you to an external page).


Attributes infoOBJECT

Optional

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

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.

Property nameTypeRequiredDescription
Skip Non-existing Attributes FlagBOOLEAN

Optional

Indicates whether to skip non-existing attributes. If Yes, the non-existing attributes are skipped and a 400 error is not returned. If No, a 400 error is returned in case of non-existing attributes.


Customer Profile IDSTRING
required

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


Event TypeSTRING
required

The name of the event sent to Talon.One.


Attribute-Value pairsOBJECT

Optional

Extra attributes associated with the event. See more info(link takes you to an external page).

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.

Property nameTypeRequiredDescription
Customer Profile IDSTRING
required

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


Skip Non-existing Attributes FlagBOOLEAN

Optional

Indicates whether to skip non-existing attributes. If Yes, the non-existing attributes are skipped and a 400 error is not returned. If No, a 400 error is returned in case of non-existing attributes.


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

Optional

You should get these audience IDs from Talon.One.


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

Optional

You should get these audience IDs from Talon.One.


Run rule engineBOOLEAN

Optional

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


Attribute-Value pairsOBJECT

Optional

Extra attributes associated with the customer profile. See more info(link takes you to an external page).

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

Update customer session is a Cloud action.

Property nameTypeRequiredDescription
Customer Session IDSTRING
required

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


Callback Destination URISTRING

Optional

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


Callback API KeySTRING

Optional

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


Content FieldsSTRING

Optional

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 IDSTRING

Optional

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.


Skip Non-existing Attributes FlagBOOLEAN

Optional

Indicates whether to skip non-existing attributes. If Yes, the non-existing attributes are skipped and a 400 error is not returned. If No, a 400 error is returned in case of non-existing attributes.


Customer Profile IDSTRING

Optional

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


Coupon CodesSTRING

Optional

Any coupon codes entered. Up to 100 coupons.`


Referral CodesSTRING

Optional

Any referral code entered.`


Loyalty CardsSTRING

Optional

Any loyalty cards used. Up to 1 loyalty cards.`


StateSTRING

Optional

Indicates the current state of the session. `


Card ItemsOBJECT

Optional

The items to add to this sessions.

If cart item flattening is disabled: Do not exceed 1000 items (regardless of their quantity) per request. If cart item flattening is enabled: Do not exceed 1000 items and ensure the sum of all cart item's quantity does not exceed 10.000 per request.`


Additional CostsOBJECT

Optional

Use this property to set a value for the additional costs of this session, such as a shipping cost.`


IdentifiersSTRING

Optional

Session custom identifier that you can set limits on or use inside your rules. For example, you can use IP addresses as identifiers to potentially identify devices and limit discounts abuse in case of customers creating multiple accounts.


Attribute-Value pairsOBJECT

Optional

Use this property to set a value for the attributes of your choice. Attributes represent any information to attach to your session, like the shipping city. See more info(link takes you to an external page).


Migration from the classic Talon.One destination

migration-from-the-classic-talonone-destination page anchor

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.