Talon.One's Rule Engine allows you to use data from a wide variety of sources in your campaign rules.
At the center of this data model is your customer, represented in Talon.One by a Customer Profile.
This data can be anonymized, or simply not collected if you prefer, but it's typically where you store profile information such as the customer details, the date their account was created, and any other information you need to collect from your customers to deliver your product or service.
Campaign rules are often based on the past activity of a customer, common examples are targeting customers who have completed an order in the past year but not the last 90 days, or customers who are purchasing items that match certain criteria.
This activity is stored in Customer Sessions. A customer session is normally an "order/transaction" or any other interaction with your platform/website.
For example, an e-commerce shop with no need for user profiles would start a new customer session every time the customer completes or cancels an order. But a car-sharing app would start a new session as soon as a customer logs in to your platform and begins to interact with your service.
Finally, it's common to target customers based on activity that is specific to your business. Maybe you want to target customers that have opened support tickets containing certain keywords or have updated their payment info in the last 60 days. You can also store this information to use in your Talon.One Campaigns with Custom Events.
You can find more information on how to import past customer session data into Talon.One in our Developer Docs.