> For the complete documentation index, see [llms.txt](https://docs.hackle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackle.io/en/ab-test/data-analysis/sa-trouble-shooting.md).

# Troubleshooting When There Is No Data

![](/files/q6sw17v2ShPSlioBy8Ep)

If you encounter a message saying **there is no data** or **no Segment Criteria are available for selection** while conducting Data Segment Analytics in the Hackle Dashboard, please check the following items in order.

## Step 1. SDK Type

Check that you have selected an SDK that supports properties.

![You can verify this in the A/B Test - Data Analysis tab.](/files/Z3YvZxcXNMQp7kISo57T)

## Step 2. SDK Integration

Check that the SDK integration process has been completed.\
You can visually confirm the SDK integration status in the SDK Integration Info menu on the left side of the Dashboard.

!["SDK Integration Complete" should be displayed.](/files/kk4VwpmCDcVFB3EZpYFT)

## Step 3. A/B Test Execution

Check that the A/B Test was run correctly.\
You can verify that Variation Distribution worked properly through the Data Analysis tab or the Real-time Exposure Status tab at the bottom of the A/B Test detail page.

## Step 4. When Using Custom Properties

### 1. Was the user object created correctly?

* When creating the user object, check that both the User Identifier and user properties were entered in the correct format.
* Check that no property values (Value) are missing from the user properties.
* Check that the values are entered according to the property value type. For example, verify that string values are processed according to the language syntax.

### 2. Were the user properties added and sent?

* Check that the user object was included in the parameters when calling Hackle SDK methods.\
  (e.g., Variation Distribution, user event tracking)
* Check if there are any cases where only the User Identifier was sent without adding user properties.


---

# 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.hackle.io/en/ab-test/data-analysis/sa-trouble-shooting.md?ask=<question>&goal=<endgoal>
```

`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.