Skip to main content

​
What this is

The Talon.One : Trigger Custom Events destination sends custom event data out of Zeotap CDP to Talon.One, so that activity captured in a journey can drive your promotion and loyalty rules. Events leave Zeotap CDP from the Send to Destinations node of a Journeys workflow. Talon.One is an API-first promotion and loyalty engine. Marketers build rules without coding and trigger discounts, coupons, loyalty points and gamified rewards from customer data, across online, in-store and mobile channels. This destination gives those rules a live event feed from Zeotap CDP.
Talon.One also has a batch destination. Talon.One Audience adds customer profiles to, and removes them from, Talon.One audiences in a batch. Use that integration for audience membership, and this one for events.

​
Supported identifiers and actions

  • Direction — Zeotap CDP to Talon.One, from a Journeys workflow.
  • Action — Trigger Custom Events in Talon.One.
  • Mandatory fields — Profile Id and Custom Event Name. Both are mapped from a Catalogue attribute, and the mapping cannot be saved until both are populated.
  • Event attributes — you can map further event attributes alongside the mandatory fields, each from a Catalogue attribute, and set the data type for each one. You can edit, add or remove entries in the list.

​
Prerequisites

  1. An active Talon.One account and Application.
  2. Your Talon.One Base URL — the URL of your Talon.One instance, for example https://retailstore.talon.one.
  3. A Talon.One Integration API Key. See Get your Talon.One base URL and API key below.
  4. The custom events and attributes you want to send, defined in Talon.One. See Creating a custom event in the Talon.One documentation.
  5. A workflow in Journeys to send the events from, with your filters and conditions already applied. See Create a Workflow.

​
Get your Talon.One base URL and API key

Both values come from Talon.One, not from Zeotap CDP.
  • Base URL — the URL of your Talon.One instance.
  • Integration API Key — in Talon.One, open the Application you want to use and go to Settings > Integration API Keys > Create API Key. Give the key a name and an expiration date.
Copy the API key as soon as Talon.One generates it. It is shown only once and cannot be retrieved afterwards.
For a step-by-step walkthrough of the same Talon.One screens, with screenshots, see the Retrieving the Talon.One API Key section of Talon.One Audience.

​
Create the Talon.One destination

1
Log in to the Zeotap CDP app and go to Integrate > Destinations.
2
Click + Create Destination.
3
Under All Destinations, search for Talon.One : Trigger Custom Events and select it.
4
On the Enter Destination Details screen, the left panel describes the integration. Enter the following on the right:a. Destination Name — a name that identifies this destination in Zeotap CDP.
b. Base URL — the base URL of your Talon.One instance.
c. API Key — the Integration API Key you generated in Talon.One.
The Enter Destination Details screen for the Talon.One : Trigger Custom Events destination, with empty Destination Name, Base URL and API Key fields and a two-step Destination Details to Mapping progress bar above them.
5
Click Next to move to the Mapping step.
6
Under Choose your Action, select Trigger Custom Events in Talon.One.Under Map the Fields, map a Catalogue attribute to each destination field. Profile Id and Custom Event Name are mandatory; add, edit or remove the optional event attribute rows beneath them as needed.
The Mapping step with Trigger Custom Events in Talon.One selected under Choose your Action, and Map the Fields showing the required Profile Id and Custom Event Name destination fields above an event attribute row with a data-type selector.
7
Click Save Mapping.
The destination sends events only once it is attached to a workflow. After you have applied your filters and conditions in Journeys, link the destination in the Send to Destinations node.
1
In the workflow, click + and choose Send to Destinations.
The Choose an action menu in a Journeys workflow, with Send to Destinations highlighted below Add a Condition, Add a Delay, Create a Multi-branch Split and Create a True/False Split.
2
Choose your Talon.One destination from the list of available destinations, using the search box if the list is long. You can also create a new one here with + Add New Destination.
The Send to Destinations panel listing the destinations already configured in the workspace as cards, with a highlighted search box above them and the Add New Destination link in the corner.
3
Under the Destination Details tab, the Base URL and API Key fields are automatically populated from the values you entered when you created the destination.
4
Under the Destination Settings tab, choose the Action and mapping you want this node to use.
5
Click Save Destination.

​
Verify the destination is attached

The Talon.One destination appears as a card in the Send to Destinations node, showing its name and the mapping action it will run.
A Talon.One : Trigger Custom Events destination attached in the Send to Destinations node, its card showing the destination name above the Trigger Custom Events in Talon.One mapping, with the remaining available destinations listed underneath.
Name the workflow and publish it before you expect events to reach Talon.One. For the full activation sequence, including re-entry conditions and publishing, see Activate your real-time audiences.

​
Next steps

Last modified on October 6, 2026