69 docs tagged with "api"

Let's set up Braze to give loyalty points to a customer when Talon.One receives a specific Braze event.

Let's create a promotion rule that always provides a 10% discount to every customer.

Effects are set in your rules. They represent what happened inside the Rule Engine so that you can apply the right action in your integration layer, if needed.

The API will return all errors as JSON objects with a message property and optionally an

Use the API tester to visually compose an Update customer session, Update customer profile, or Track event CURL request using the Campaign Manager.

Every request to the Integration API comes from your integrated webshop. Typically,

Applications are the environment where you create and manage your campaigns. Each Application can contain one or more campaigns and API keys to send integration data to Talon.One.

Learn how to integrate with Talon.One with a basic example.

Let's create a promotion rule that awards customers with one loyalty point per dollar they spend on accessories.

In this tutorial, let's create a coupon dispenser button for our Salesforce

Create an achievement to check if a customer has reached a defined target within a specified period of time.

Create an Application to:

To integrate Talon.One with MoEngage, you can create a Content API in MoEngage for each of the following supported generic CEP integration endpoints:

In this tutorial, let's set up Braze to automatically generate coupons inside Talon.One and deliver the coupon codes to specific customer segments.

In this tutorial, let's set up Iterable to automatically generate

In this tutorial, let's set up Klaviyo to automatically generate

A number of use cases may require creating custom coupons using the Management API. Custom coupons are coupons with custom attributes that we can leverage to tweak the coupons' behaviour.

Create a batch of loyalty cards to allow your customers to collect and spend loyalty points on them.

You can create notifications for each of your loyalty programs.

In this tutorial, let's set up Iterable to automatically generate referral

A referral program is defined by an advocate, a friend and a referral code.

In this tutorial, let's set up Braze to automatically generate referrals inside Talon.One and deliver the referral codes to specific customer segments.

A customer profile is Talon.One's internal representation of your customer.

Certain endpoints allow you to customize the response to get additional data from one call. Use this to increase performance in your integration layer.

The Audit logs section displays all changes made to the Management API.

An event represents a single occurrence of an individual customer action. Each customer session contains one or more events.

Use the Integration API logs to see the Integration API requests received by the Application of your choice.

A store is an entity in Talon.One used to represent all the physical and digital sales channels of an organization. Each store contains data created and updated through the Management API.

A dry request is a test request that is checked by Talon.One but that is not executed.

This guide is for companies operating ecommerce businesses. It shows how Talon.One can be used to provide loyalty programs and discounts. There are two steps to using Talon.One:

Events are a type of entity. An event represents a single occurrence of a specific customer action related to a customer session or a customer profile.

You can export data from Talon.One to use it in other marketing tools, run reports or analyze it as part of your BI strategy in case your integration landscape includes an existing data warehouse.

Let's set up Braze to retrieve the loyalty ledger information of a customer from Talon.One.

Let's set up CleverTap to retrieve the loyalty ledger information of a customer from Talon.One.

In this tutorial, let's set up Iterable to retrieve the loyalty ledger

In this tutorial, let's set up Emarsys to retrieve existing coupons

Let's set up Emarsys to retrieve the loyalty balance of a customer from Talon.One.

This guide is for companies operating gambling or wagering businesses. It shows how

You can integrate with any customer data platform (CDP) using Talon.One's endpoints for third-party tools.

You can integrate with any customer engagement platform (CEP) using Talon.One's endpoints for third-party tools.

If you are replacing an existing loyalty system with Talon.One, you can import all loyalty points and loyalty cards from the old system into Talon.One.

Talon.One supports commercetools integration via the open-source commercetools accelerator on GitHub.

This tutorial shows you the basic steps to integrate Talon.One with mParticle.

This tutorial shows you the basic steps to integrate Talon.One with Segment.

Use the Integration API to send external information to the Talon.One Rule Engine or to retrieve data in high-load environments. It's the main API for all integration use-cases.

Every integration is unique, but keep in mind the following points.

Take your first integration steps with a basic integration example.

Integrating with Talon.One revolves around two main concepts: sending customer session updates and processing rule effects.

Use the Management API to programmatically do most of what the Campaign Manager's UI allows. It's the API for management purposes and back-office systems.

Create additional costs to add extra costs to the customer's cart or to specific items. For example, shipping costs or transaction fees.

You can edit the details of an Application or delete an Application at any time.

When the default effects do not match your use case, you can create a custom effect.

The API key contained in an Application allows you to authenticate with the Integration API to send data to and retrieve it from a specific Application.

You can create and manage the API keys used to interact with the Management API.

A Third-party API key allows you to authenticate with the Third-party API to exchange data between Talon.One and a supported technology partner.

When you are building a new integration or making changes to an existing one, you may want to monitor the requests sent via the Integration API.

This guide is for businesses in the on-demand space. It shows how Talon.One can be used to provide loyalty programs and discounts. There are always two steps to using Talon.One:

This tutorial describes how to set up provisioning and deprovisioning of Talon.One users with single sign-on (SSO) using Okta.

Let's return some items from a given customer session.

Talon.One offers SDKs for the following languages. Use them

This guide is for businesses in the telecommunications area. It shows how Talon.One can be used to provide loyalty programs and discounts. Regardless of the industry you work in, there are two steps to using Talon.One:

In the Campaign Manager, in Account > Tools, you can create and manage many entities related to your Talon.One account.

Sometimes, a campaign might not trigger the effects you expect. Here are a few

Cart item flattening is a process consisting in splitting each cart item whose quantity is greater than 1 into individual cart items.

After you create an audience in Talon.One,

You can use Talon.One to manage coupon wallets. Coupon wallets enable customers to collect

The Update customer session endpoint of the Integration API allows you to add custom identifiers in addition to the session identifier. To add custom identifiers, use the identifiers property in the body.

You can create campaigns that only trigger if your customer is in a specific location.

In this tutorial, we set up Braze to use universal coupons with reservations.