# Overview The TallyMarks platform supports the recording, assessing and incentivising of customer behavior. The platform is **EVENT DRIVEN** and is integrated into your existing platforms with the Tallymarks API to capture your customer events. To assess events it supports the quick configuration of **CUSTOMISABLE RULES** to target and incentivise your customer's behaviour. Build simple to complex promotions by combining rules and outcomes. Execute your own points-based and/or non-points based loyalty platform. The platform supports a range of **FULFILMENT OPTIONS** such a rewarding points which enable you to execute your own points-based loyalty platform as well as providing with the flexibility to support a range of non-points based customer inventive activity. The platform has a three phase process for assessing events and rewarding customers: ## :writing\_hand: Record (Events) Capture customer events such as registration, unsubscribe, accessing a page, completion of surveys or game, purchase on eCommerce shopping carts or online transactions. ## :dart: Target (Assessment) Target customers' behavior using a range of parameters relating to their current and past activity, be it time, value, frequency, repeat business or your own custom parameters. ## :trophy: Respond and Reward (Fulfil) Reward customers for their behavior. Score activity and reward points, rebates or discounts. Add customers to lists for specific offers. Export lists for targetted campaigns. Send SMS's or Emails. Initiate events on your own platform. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.tallymarks.io/master.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.