Skip to main content

Segment

You can integrate Segment with Talon.One. Typically, this consists in receiving customer profile data from Segment.

Installing a Talon.One destination#

To receive customer profile attributes from Segment, create a Talon.One destination in Segment. With it, you can use the customer data stored in Segment with any BI tools and target our promotions more effectively based on audiences created in Segment.

  1. In Segment, open the Destinations page and click Add Destination.
  2. Search for Talon.One within the Destinations Catalog and confirm the destination.
  3. Get your Talon.One application's API key, select an application, and click Settings > Developer Settings > Create a New API Key.
  4. Add the API Key into the Segment Settings.
  5. Add your Talon.One application domain name, for example <https://demo.talon.one>.
  6. Add at least one custom attribute. These are Segment's Custom Traits that link to Talon.One's Customer Profile Attributes.

Setting up custom attributes in Talon.One#

There are 3 types of traits relating to a Customer Profile in Segment:

  1. Custom Traits
  2. Audiences (Customer Segments)
  3. Computed Traits

For each trait type, set up a corresponding customer attribute in Talon.One. Any communication from Segment to Talon.One containing unknown customer attributes will be rejected.

Ensure you respect the following rules:

  • When creating a customer attribute in Talon.One, ensure it has the same name as the trait name in Segment. The name is case sensitive.
  • Custom traits and computed traits in Talon.One should be set as the same data type as in Segment. Audience Data should be set up as a Boolean data type.

To create the attributes:

  1. In the Campaign Manager, click Home > See Developer Section > Create Attributes

  2. In Associated Entity, select Customer Profile.

  3. Select the corresponding Attribute Type. It's always Boolean for audiences created in Segment.

  4. Enter the API Name (Internal). This must be the same as the trait name that will be sent from Segment.

    Create attribute

  5. Add the same name to the Talon.One Destination, on the Segment Dashboard, click Destinations > Talon_One > Custom Attributes > Add Row > [YOUR_CUSTOM_ATTRIBUTE] > Save.

    Use custom attribute

Parent and child objects#

Parent/child objects received from Segment are supported. The data will be flattened with an underscore between the parent and child's name. For example:

{  address:{    city: 'Berlin'  }}

Becomes address_city.

Transferring data#

When the Talon.One destination has been set up and the custom attribute are added to the Campaign Manager, data is transferred automatically.

Custom traits#

When a Custom Trait is gathered from a source and fed into Segment, the Talon.One destination app will check the app settings. If it exists it will automatically send the data to Talon.One.

Audiences#

When an Audience is created and linked to the Talon.One destination, Segment will check which users belong to this Audience and which do not.

The audience name and a true or false value is automatically sent to Talon.One for each user that Segment knows about.

When a user enters or leaves an audience, depending on the audience settings in Segment, this data is updated in real-time or on an hourly basis.

Computed traits#

When a computed trait is created and linked to the Talon.One destination, Segment will first complete the calculation. Then, the computed trait name and computed trait value are automatically sent to Talon.One for each user Segment knows about.

When a user's computed trait change, it is automatically updated in Talon.One.

Using data from Segment in Talon.One#

When creating a condition for a campaign rule, you can now create constraints based on the imported attributes from Segment.

The imported attributes are under the Profile tab in the attribute palette.

Use in condition