Skip to content

Commit 24ec035

Browse files
forstisabellaforstisabella
authored
Merge pull request #2633 from talon-one/sc-6056-segment-integ-docs
Add: Talon.One (Action) Destination
2 parents 0592647 + 29a25e8 commit 24ec035

File tree

2 files changed

+109
-0
lines changed

2 files changed

+109
-0
lines changed

‎src/connections/destinations/catalog/actions-talon-one/index.md

Lines changed: 105 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,105 @@
1+
---
2+
title: Talon.One (Action) Destination
3+
hide-boilerplate: true
4+
hide-dossier: false
5+
hidden: true
6+
---
7+
8+
<!-- In the section above, edit the `title` field. For example, Slack (Actions) Destination -->
9+
10+
{% include content/plan-grid.md name="actions" %}
11+
12+
Create flexible and targeted promotional and loyalty campaigns with [Talon.One](https://www.talon.one/){:target="_blank"}.
13+
Campaigns can be created and managed by non-technical users like marketers. There is no need to
14+
get your development team involved. Features include coupons, discounts, loyalty
15+
programs, referral tracking, geofencing, and bundling.
16+
17+
This destination is maintained by Talon.One. For any issues with the destination, [contact the Talon.One Support team](mailto:[email protected]) or refer to [Talon.One's documentation](https://docs.talon.one/docs/dev/technology-partners/segment){:target="_blank"}.
18+
<!-- In the section below, add your destination name where indicated. If you have a classic version of the destination, ensure that its documentation is linked as well. If you don't have a classic version of the destination, remove the second and third sentences. -->
19+
20+
> success ""
21+
> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Talon.One Segment destination. There's also a page about the [non-Actions Talon.One destination](/docs/connections/destinations/catalog/talonone/). Both of these destinations receive data from Segment.
22+
23+
## Benefits of Talon.One (Actions) vs Talon.One Classic
24+
25+
Talon.One (Actions) allows you to share more data than the classic destination.
26+
The classic version only shares customer profile data. The Action version supports sharing the following data:
27+
28+
- Customer profile data
29+
- Audience data
30+
- Tracking events
31+
32+
<!-- The section below explains how to enable and configure the destination. Include any configuration steps not captured below. For example, obtaining an API key from your platform and any configuration steps required to connect to the destination. -->
33+
34+
## Getting started
35+
36+
### Creating an API key in Talon.One
37+
38+
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:
39+
40+
1. Open your Talon.One Application in the Campaign Manager and click **Settings > Developer settings**.
41+
1. Click **Create API Key**.
42+
1. For **Do you want to use this API Key with a 3rd party service**, select **Yes**.
43+
1. Select **Segment** from the dropdown.
44+
1. Select an expiry date and click **Create API Key**.
45+
1. Copy it for later use.
46+
47+
### Adding a Talon.One destination
48+
49+
To start sending data to Talon.One from Segment, create a Talon.One
50+
[destination](/docs/connections/destinations/) in Segment.
51+
52+
1. In Segment, click **Destinations** > **Add Destination**. The **Destination catalog** opens.
53+
1. Search for **Talon.one** and configure the destination.
54+
1. Enter the details:
55+
- In **Name**, type a name, for example `Talon.One destination`.
56+
- In **API key**, paste the API key generated in the previous section.
57+
- In **Deployment**, type the URI of your Talon.One deployment, for example
58+
`https://mycompany.europe-west1.talon.one/`.
59+
1. (Optional) Set up your filters.
60+
1. Configure the mapping:
61+
1. Click **New Mapping** and select the type of action to perform in Talon.One.
62+
For example _When a new audience is created in Segment, also create it in Talon.One._
63+
1. Configure the trigger and action fields.
64+
1. Click **Event Tester** and test if you received the data in Talon.One.
65+
66+
Once you receive data, you can start creating rules that rely on that data.
67+
68+
> warning ""
69+
> **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](https://docs.talon.one/docs/product/account/dev-tools/managing-attributes#creating-custom-attributes){:target="_blank"}.
70+
71+
### Testing the integration
72+
73+
You can use the following payloads to test and fine-tune your requests.
74+
75+
```json
76+
{
77+
"messageId": "segment-test-message-t1kx8e",
78+
"timestamp": "2022-03-22T12:41:20.918Z",
79+
"type": "track", // or any other type in Segment
80+
"userId": "test-user-z65zqk",
81+
"event": "track-event", // or any other event in Segment
82+
"email": "[email protected]",
83+
"projectId": "qR6APLKpCBB3ue8pHkBLpo",
84+
"properties": {
85+
"eventType": "mySegmentEvent",
86+
"type": "boolean",
87+
"customerProfileId": "a_customer_id",
88+
"attributes": {
89+
"language": "English" // depends your custom attributes in Talon.One
90+
}
91+
}
92+
}
93+
```
94+
95+
### Next steps
96+
97+
Once you receive data from Segment inside Talon.One, start creating your rules in the Campaign Manager. See the [Talon.One documentation](https://docs.talon.one/docs/product/rules/overview){:target="_blank"}.
98+
<!-- The line below renders a table of connection settings (if applicable), Pre-built Mappings, and available actions. -->
99+
100+
{% include components/actions-fields.html %}
101+
<!-- If applicable, add information regarding the migration from a classic destination to an Actions-based version below -->
102+
103+
## Migration from the classic Talon.One destination
104+
105+
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.

‎src/connections/destinations/catalog/talonone/index.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,10 @@ title: Talon.One Destination
44
beta: true
55
id: 5de7c705e7d93d5e24742a04
66
---
7+
8+
> warning ""
9+
> Segment and Talon.One recommend you use the [Talon.One (Action) Destination](/docs/connections/destinations/catalog/slack/) instead.
10+
711
Create flexible and targeted promotional & loyalty campaigns with [Talon.One](https://Talon.One/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners).
812
Campaigns can be created and managed by non-technical users such as marketeers. There is no need to get your development team involved. Features include coupons, discounts, loyalty programs, referral tracking, geo-fencing, and bundling.
913

0 commit comments

Comments
 (0)