Skip to main content

15 docs tagged with "session"

View all tags

Attributes

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

Customizing responses

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

Displaying customer sessions

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.

Displaying events

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

Displaying the Application dashboard

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.

Importing customer data

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

Integration with Talon.One

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

Using custom identifiers to prevent fraud

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.