> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/assets-library/creating-and-managing-segments/list-of-segment-criteria/action-tracker-criterion.md). # Action & Custom Tracker criterion The Action Tracker criterion is a segmentation criterion that enables defining a [segment](/assets-library/creating-and-managing-segments.md). To learn how to create a segment, please refer to this [article](/web-experimentation-and-personalization/targeting-step/how-to-create-a-segment-who-section.md). ## 📖 Definition The Action Tracker criterion enables you to create a segment of visitors who have (or haven't) completed an **Action Tracker** or **Custom Tracker** in the current or previous session(s) during the last 13 months. ## 🔎 How Does It Work? With the tag, we created an object called `ABTastyData` **in Local Storage** that contains information about your visitors’ journey. Once a visitor has completed an Action Tracker or a Custom Tracker on your website, the information will be stored there under ActionTracker. You can refer to the [***technical documentation***](https://developers.abtasty.com/docs/tag/tag-window#abtastyclicktracking-) to have more information.

Note that since this information is stored in the local storage and thus historicized, the Action & Custom Tracker criterion is to be used as a segment and not a trigger. ## ⚙️ Configuration To use this criterion, drag and drop the **Action & Custom Tracker** label inside the middle column of the segment builder. You will have to choose from the following operators to configure your segment, which will determine the operation behind the value you will declare: * **`is`:** will include visitors who match the declared value. Here we are referring to users who interacted with a specific element during their navigation. * **`is not`:** will exclude visitors who do not match the declared value. Here we are referring to users who did not interact with a specific element during their navigation. Then enter the required value inside the number field. You have to enter the exact name (string) of the Tracker. You can select one action tracker per line. To add another action tracker, you can click **`+Add condition`** and choose the action to be added from the dropdown. By choosing `some`, you will target all visitors who converted one or the other of the selected action trackers. By choosing `all`, you will target the visitors who converted both action trackers.

## 💡 Use case On certain websites, to join a loyalty program or confirm a newsletter subscription, visitors are asked to click a confirm button on a specific page. You can then choose this click tracking to create a new “subscriber” or “VIP member” segment. **Need additional information?** Submit your request at Always happy to help!

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.abtasty.com/assets-library/creating-and-managing-segments/list-of-segment-criteria/action-tracker-criterion.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.