# Talon.One Destination

## About this integration

Talon.One helps you design customized and effective promotional and loyalty campaigns without significant development resources. The Talon.One destination leverages leverage your source data to identify your customers and gather event activity so you can support your customers through coupons, discounts, loyalty programs, referral tracking, geo-fencing, and bundling.

[Mode How we forward source data to the destination: through Customer.io's servers or directly from our JavaScript client.](/cdp/destinations/getting-started/#connection-mode)

[Web sources Indicates whether or not this integration supports our the JavaScript client.](/cdp/sources/getting-started/#types-of-sources)

[API sources Indicates whether or not this integration supports our server libraries (Go, NodeJS, Python), API, Mobile SDK, and other data sources.](/cdp/sources/getting-started/#types-of-sources)

[Supported calls The API methods this integration supports.](/cdp/sources/source-spec/source-events/)

[Integration name The name of this integration if you want to enable or disable it in the `integrations` object.](/cdp/sources/source-spec/common-fields/#the-integrations-object)

Standard

N/A

Talon.One (Actions)

## Getting started[](#getting-started)

1.  Go to **[Data & Integrations > Integrations](https://fly.customer.io/workspaces/last/journeys/integrations/all/directory)** and select the **Talon.One** entry in the *Directory* tab.
    
2.  (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration.
    
3.  Configure your integration.
    
    1.  **Api Key**: Created under Developer Settings in the Talon.One Campaign Manager.
        
    2.  **Deployment**: The base URL of your Talon.One deployment.
        
4.  Click **Enable Destination**.
    

## Actions[](#actions)

When you’re done setting things up, you can go to the *Actions* tab to see how we map incoming data to your integration.

You may need to add actions for this integration

While we often have default triggers for actions, we don't always add those actions as defaults. You may need to add actions to make sure that you're sending all the data that you want to send to your integration. See our [actions](/integrations/data-out/actions/) page for help setting up actions.

Action

Default Trigger

Description

Update Customer Profile

This updates attributes and audiences for a single customer profile.

Track Event

This records a custom event in Talon.One.

Update Customer Profile V2

You do not have to create attributes or audiences before using this endpoint.

Update Customer Sessions

This updates a customer session.