> 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/adaptivecx/getting-started/core.md).

# Core

The Core section contains the fundamental building blocks of AdaptiveCX. Use these features to create predictions, define audiences, track events, and capture visitor affinities and attributes.

## What you'll find here <a href="#what-youll-find-here" id="what-youll-find-here"></a>

* **Predictions** - Create AI models that predict visitor behavior
* **Audiences** - Define segments of visitors based on criteria
* **Events** - Track specific visitor actions on your site
* **Affinities** - Capture visitor interests in categories, brands, and products
* **Attributes** - Store visitor characteristics and session data

## Recommended order <a href="#recommended-order" id="recommended-order"></a>

If you're new to AdaptiveCX, explore these features in order:

1. Events - Define what actions you want to track
2. Attributes - Understand available visitor characteristics
3. Affinities - Set up interest categories
4. Audiences - Create visitor segments
5. Predictions - Build predictive models

## Key concepts <a href="#key-concepts" id="key-concepts"></a>

#### Active vs suggested items <a href="#active-vs-suggested-items" id="active-vs-suggested-items"></a>

Many Core features show both active and suggested items:

* **Active** - Items you've created or confirmed
* **Suggested** - Items AdaptiveCX automatically detected from your data

Suggested items help you discover valuable events, audiences, and affinities you might have missed.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.abtasty.com/adaptivecx/getting-started/core.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
