Skip to main content

Running promotions for Segment audiences

The Personas Audiences feature in Segment enables you to group users or accounts based on event behavior and traits that Segment tracks.

In Segment, you can build an audience from a core tracking event and synchronize it with a destination. By configuring Talon.One as a destination, you can reference the audience in your Talon.One campaigns.

For example, in Segment, you can group all users who abandoned their cart before checkout into an audience. Then, in Talon.One, you can create a campaign to offer them a convincing discount by issuing a coupon code for their checkout.

Let's configure Talon.One as a destination and define an audience in Segment.

Prerequisites​

  • You are an Admin user in Talon.One and Segment.
  • In Segment, you configured a data source. Segment requires this data source to track events.
  • In Talon.One, you created a Segment-specific API key.

Configuring Talon.One as a Segment destination​

Segment tracks event data coming from the data source and passes it to a valid destination. You can configure Talon.One as a destination.

To configure Talon.One as a Segment destination:

  1. In the Segment dashboard, click Connections > Destinations > Add Destination.
  2. On the Catalog page, select the Actions-enabled destination named Talon.One (Actions).
  3. On the catalog summary page, review the selected destination and click Configure.
  4. Select the data source you configured as a prerequisite and click Confirm Source.
  5. On the Basic Settings page, enter the following information:
    1. In Name, type the name of your destination.
    2. In API Key, type the API key you created as a prerequisite.
    3. In Deployment, type the base URL of your Talon.One deployment.
    4. Select Enable Destination and click Save Changes.

Defining the Segment audience​

Using Segment's Audience Builder, define the audience based on your business requirements. In this tutorial, the event of users abandoning their cart before checking out is marked by Product Removed.

To define the Segment audience:

  1. In the Segment dashboard, click Personas > Audiences > Create > Audience.
  2. On the Configure and Preview Your Audience page, click Add Condition > Performed an Event.
    1. In ...performed, select Product Removed, at least, and type 1 time.
    2. Click Next.
  3. On the Select Destinations page, select the destination you created in the previous step.
    1. In Connection settings, select Send Identify and Send Track.
    2. In Enter Event, type the name of the event to send to the destination when a user enters the audience, for example, Product Removed.
    3. Click Save and Next.
  4. On the Review & Create page, type a name and optional description for the audience and click Done.

Configuring the data mapping for the Segment destination​

An explicit data mapping allows you transform the incoming data into a Talon.One-readable format before passing it to the destination. Configure this mapping in the destination you created earlier for Talon.One.

To configure the data mapping for the Segment destination:

  1. In the Segment dashboard, click Connections > Destinations, and open the destination you created earlier for this audience.
  2. In the Mappings tab, click New Mapping and select the action you want to map, for example, Update Customer Profile V2.
  3. In Define event trigger > Event Name > is, type the name of the event you specified while defining the audience and test it, for example, Product Removed.
  4. In Define mappings > The audiences for the customer to join, enter:
    • context.personas
      • name = computation_key
      • integrationid = computation_id
  5. (Optional) In the last step, click Test Mapping.
  6. Click Save.
  7. In the Mappings table, under Status, enable the mapping.

Building the rule in Talon.One​

In your Talon.One campaign, you can now reference the audience you defined in Segment. In your rule, use the Is member of an audience condition to act on the members of the audience.

tip

You can also use the other available audience conditions in the Rule Builder.