Talon.One is a promotion and loyalty engine that lets you reward participants with coupons, discounts, loyalty points and referral perks. This integration sends game and registration data from your Playable campaign into Talon.One, where your own rules decide which reward each participant receives.

What does the integration do?

With the Talon.One integration, you can:

Send an event to Talon.One when a participant registers, completes a game or wins a prize
Pass game data such as score, rounds played and game outcome into Talon.One as event attributes
Trigger coupons, discounts, loyalty points or referral rewards from your existing Talon.One campaigns
Reward participants based on how they played, not just the fact that they took part

Watch this short video explainer on how data flows from Playable to Talon.One.

Before you start

You will need a few things from your Talon.One account before you set up the integration in Playable:

What you need	Why
Your deployment URL	Talon.One accounts sit on their own deployment address, so Playable needs to know where to send events
A Management API key	Used to read the list of event attributes available in your account, so you can map Playable data to them
An App Integration API key	Determines which Talon.One app receives the events. This key is scoped to a single app
An event type	The event your Talon.One campaign listens for, for example "game_played". This must already exist in your Talon.One app
Custom event attributes	Any game data you want to use in your rules needs a matching attribute in Talon.One first

If an attribute does not exist in Talon.One, you will not be able to map data to it. You may need to create additional attributes in your Talon.One app before you can finish the setup.

Add the Talon.One integration

To add the integration:

Go to the Integrations tab in your campaign
Click Add Integration
Select Email Provider
Scroll through the list and select Talon.One

If you have previously set up a Talon.One integration in Playable, you can reuse that configuration instead of entering your credentials again.

Configure the Talon.One integration

Once you have added the integration, you will land on General integration settings. This is where you connect Playable to your Talon.One app.

Setting	What to enter
Deployment base URL	Your Talon.One deployment URL, without a trailing path
Management API key	Your account-level Management API key. Playable uses this to read the event attributes available in your account
App Integration API key	The app-scoped Integration API key from Talon.One. Events are sent to this app
Integration Name	A name to identify this configuration, for example "Talon.One Loyalty App". Useful if you connect to more than one Talon.One app
Only transfer registration once per unique identity	Tick this to send only one event per participant. The unique identity is based on the registration limit field, which you set in the general campaign settings

Once your keys are saved they are masked. Use Reset if you need to replace a key.

Because the App Integration API key is scoped to a single Talon.One app, add a separate integration for each app you want to send events to.

Select trigger and conditions

The trigger decides when Playable sends an event to Talon.One.

Triggers

The triggers available depend on the placement of your registration form(s) and whether you have included prizes in the campaign.

Trigger Name	Event that Triggers Data Transfer
Primary registration form submitted	Data is sent every time the primary registration form (containing the email field) is submitted
Game completed	Data is sent as soon as the game status is known (winner or loser), only if the primary registration form has already been submitted. Note: this option is only available if registration form is placed BEFORE the game.
Prize won	Data is sent when a regular prize has a winner assigned (whether or not the game has been completed)
Bulk prize won	Data is sent when a bulk prize has a winner assigned (whether or not the game has been completed)

Conditions

It is possible to add additional conditions to the trigger. Together with the trigger, these must be met in order for the data to be transferred.

Using the form field option you can define a specific field in the registration form(s) that must be filled out.

With the advanced option you have the option to set up a data flow based on more complex conditions. For example, the trigger could be based on performance in the game or a specific selection or data input in the registration form.

Set the event type

Every event sent to Talon.One must carry an event type. This is how your Talon.One campaign knows which rule to run, so it is a required field.

The event type is added through the Static information section at the bottom of the field mapping:

Scroll to Static information
In the Static value field, type the event type exactly as it appears in your Talon.One app, for example "Game Played"
Click Add
Using the drop-down beneath the value you just added, map it to Event type

The value must match the event type in Talon.One exactly. If it does not match, the event will be sent but no rule will fire.

You can use static information for other fixed values too. For example, you might add "Playable" as a static value so you can identify the source of the event in Talon.One.

Map data fields

Mapping is how you decide which Playable data ends up in Talon.One. For each Playable field, use the drop-down to select the Talon.One destination, or leave it as Don't map this field if you do not need it.

Profile ID (required)

You must map one field to profileId. This is Talon.One's only unique identifier for a customer profile, so without it Talon.One cannot connect the event to the right person.

Map this to whichever field holds the identifier your Talon.One profiles are keyed on. This is often the email address or a customer ID passed into the campaign URL.

Event attributes

Everything else you map is sent as an event attribute. The available options come from the custom event attributes in your Talon.One account, which Playable reads using the Management API key.

Fields commonly mapped as attributes include:

Score and rounds, for rewarding based on performance
Gameflow status, to distinguish winners from other participants
Campaign ID or campaign name, to identify which campaign the event came from
Registration form fields, such as name or customer segment

Missing an attribute? If the attribute you need is not in the list, create it in your Talon.One app first, then return to the integration.

Notification email

At the bottom of the mapping section you can add an email address to be notified when an error occurs. We recommend filling this in, so you know straight away if data stops reaching Talon.One.

Test the Talon.One integration

We always advise that you test the integration by going through the actual campaign.

Open the campaign and submit the registration form
Play through the game so the trigger you selected is met
Open the Activity tab in Playable and confirm the data was transferred
In Talon.One, check that the event arrived on the expected customer profile with the attributes you mapped
Confirm that your Talon.One campaign rule fired and the reward was issued

To learn more about how to test integrations in general, please read this Help Center article.

Talon.One Integration

In this article