> 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/cafe-24/cafe24-faq.md).

# Cafe24 FAQ

Frequently asked questions about Cafe24 integration, event collection, and In-App Message setup.

Frequently asked questions after integrating your Cafe24 store with Hackle.

#### How can I integrate?

Install the Hackle app on your store.\
The integration is complete once you finish permission consent, Workspace creation, and script installation.

See [Cafe24 Integration](/en/cafe-24/integration.md) for the installation steps.

***

#### What does In-App Message Targetable mean?

Due to structural constraints of how Cafe24 stores operate, some events have an `In-App Message Targetable` value of X.

We recommend using events that start with `view_`.

{% hint style="danger" %}
The following events cannot be set as In-App Message targeting conditions.

* Events that occur on the server, not in the browser
* Events where Cafe24 navigates to a new page after the event fires
  {% endhint %}

***

#### The scroll event fires too frequently.

The scroll event installed via the Hackle app fires every 5% of the total scroll height of the page.\\

See [Cafe24 Scroll Event Adjustment](/en/cafe-24/events/cafe24-event-management.md) for how to adjust the frequency.

***

#### A property I want is not being collected.

The Hackle app collects properties from the Cafe24 environment. Depending on your store settings, some properties may not be collected.

* If a User Property is missing, check whether the sign-up field is set as **required**.
* If an Event Property is missing, check your design and module settings.

{% hint style="info" %}
When a property is not being collected, please contact the Hackle team with information about the design or modules you are using.
{% endhint %}


---

# 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/cafe-24/cafe24-faq.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.