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.
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.
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
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:
- Open your Talon.One Application in the Campaign Manager and click Settings > Developer settings.
- Click Create API Key.
- For Do you want to use this API Key with a 3rd party service, select Yes.
- Select Segment from the dropdown.
- Select an expiry date and click Create API Key.
- Copy it for later use.
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.
To start sending data to Talon.One from Segment, create a Talon.One destination in Segment.
- In Segment, click Destinations > Add Destination. The Destination catalog opens.
- Search for Talon.one and configure the destination.
- 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/.
- In Name, type a name, for example
- (Optional) Set up your filters.
- Configure the mapping:
- 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.
- Configure the trigger and action fields.
- 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
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.
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 Segment5"userId": "test-user-z65zqk",6"event": "track-event", // or any other event in Segment7"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.One15}16}17}
Once you receive data from Segment inside Talon.One, start creating your rules in the Campaign Manager. See the Talon.One documentation.
Created under Developer Settings in the Talon.One Campaign Manager.
The base URL of your Talon.One deployment.
Build your own Mappings. Combine supported triggers with the following Talon.One-supported actions:
Mapping limits per destination
- 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
This creates a new audience entity in Talon.One.
Create Audience is a Cloud action.
You should get this audience ID from Segment.
You should get this audience name from Segment.
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.
The customer profile integration ID to use in Talon.One. It is the identifier of the customer profile associated to the event.
The name of the event sent to Talon.One.
Type of event. Can be only string, time, number, boolean, location
Optional
Use this field if you want to identify an attribute with a specific type
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.
Optional
Extra attributes associated with the customer profile. See more info.
The customer profile integration identifier to use in Talon.One.
Optional
You should get these audience IDs from Talon.One.
Optional
You should get these audience IDs from Talon.One.
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.
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.
You should get this audience ID from Segment.
This updates attributes for multiple customer profiles.
Update Multiple Customer Profiles’ Attributes is a Cloud action.
An array of JSON objects that contains customer profile identifier and list of attributes and their values. Customer profile ID is required.
Optional
This may contain mutual list of attributes and their values for every customer profile in the "data" array.
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.
You should get this audience ID from Segment.
You should get this audience name from Segment.
This updates audiences for multiple customer profiles.
Update Multiple Customer Profiles’ Audiences is a Cloud action.
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.
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.
The customer session integration identifier to use in Talon.One.
Optional
This specifies the address of the service and its endpoint to do callback request.
Optional
This specifies API key and relative header. The header is specified optionally
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.
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.
This contains all the data related to customer session.
Optional
Use this field if you want to identify a session attribute with a specific type
Optional
Use this field if you want to identify a cart item attribute with a specific type
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.
The customer profile integration identifier to use in Talon.One.
Optional
Audience name and integration ID
Optional
Audience name and integration ID
Optional
This runs rule engine in Talon.One upon updating customer profile. Set to true to trigger rules.
Optional
Extra attributes associated with the customer profile. See more info.
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.
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.
The customer profile integration ID to use in Talon.One. It is the identifier of the customer profile associated to the event.
The name of the event sent to Talon.One.
Optional
Extra attributes associated with the event. See more info.
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.
The customer profile integration identifier to use in Talon.One.
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.
Optional
You should get these audience IDs from Talon.One.
Optional
You should get these audience IDs from Talon.One.
Optional
This runs rule engine in Talon.One upon updating customer profile. Set to true to trigger rules.
Optional
Extra attributes associated with the customer profile. See more info.
This updates a customer session. Create all the required attributes before using this Action.
Update customer session is a Cloud action.
The customer session integration identifier to use in Talon.One.
Optional
This specifies the address of the service and its endpoint to do callback request.
Optional
This specifies API key and relative header. The header is specified optionally
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.
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.
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.
Optional
The customer profile integration identifier to use in Talon.One.
Optional
Any coupon codes entered. Up to 100 coupons.`
Optional
Any referral code entered.`
Optional
Any loyalty cards used. Up to 1 loyalty cards.`
Optional
Indicates the current state of the session. `
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.`
Optional
Use this property to set a value for the additional costs of this session, such as a shipping cost.`
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.
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.
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.