15 docs tagged with "session"

An attribute represents a characteristic of a given entity, and you can use it in your rules.

One of the things we can expect when cancelling a session

A customer session is a finite container of customer activity within an Application.

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

Let's create a customer session custom attribute referring to the customer's shipping city and use it in a promotion rule to discount the session total.

A customer profile contains data created and updated by the Campaign Manager as well as

Customer sessions contain customer activity within a given Application. For example, a customer session can represent a shopping cart or a completed order for a given customer.

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

The Application dashboard provides you with detailed data about the influence of your campaigns on sessions, generated revenue, discounts, and coupons. You can view this data for all the campaigns in your Application or filter it by campaign.

When you first integrate with Talon.One, ensure you import information about your existing customers to maximize the use of targeted campaigns immediately.

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

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

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

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

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.