> For the complete documentation index, see [llms.txt](https://help.sesami.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sesami.co/zh-cn/apps-integrations/shopify/customers.md).

# 客户

客户数据的流转取决于所使用的预订方式。

## Shopify 结账

当客户通过 Shopify 结账预订时，系统会自动创建 Shopify 订单和客户记录。这让您可以全面使用 Shopify 的客户管理工具。

## Sesami 即时预订

使用 [Sesami 即时预订](https://help.sesami.co/zh-cn/yu-ding/booking-features/instant-booking.md)，客户会完全跳过 Shopify 结账——因此不会自动创建 Shopify 客户记录。

要通过 Sesami 即时预订捕获和管理客户数据，请使用 [Klaviyo 集成](https://help.sesami.co/zh-cn/apps-integrations/klaviyo.md) 来跟踪预订事件并构建客户档案。

## 使用 Shopify Flow 自动为客户添加标签

对于通过 Shopify 结账的客户，您可以使用 Shopify Flow 自动为他们添加标签。这适用于：

* **细分** — 识别已预订与未预订的客户
* **营销** — 在 Klaviyo 或其他工具中创建定向活动
* **报告** — 在 Shopify 中筛选并跟踪预订客户

### 如何设置

1. 前往 **Shopify > 应用 > Shopify Flow**
2. 创建新的工作流
3. 将 **触发器** 设置为“订单已创建”
4. 添加一个 **条件** 以检查订单是否包含 Sesami 预订商品（例如，检查特定商品标签或“时长”行项目属性）
5. 添加一个 **操作** 为客户添加标签（例如，“已预约”）
6. **保存并启用** 该工作流

{% hint style="info" %}
客户被添加标签后，您可以在 Klaviyo、Shopify Email 或其他营销工具中使用这些标签创建定向细分。
{% endhint %}

## Sesami 中的客户数据

Sesami 仅存储运行所需的最少客户数据：

* 客户姓名
* 电子邮件地址
* 订单 ID

有关 Sesami 如何处理数据的更多信息，请参阅我们的 [隐私政策](https://sesami.co/privacy-policy).

## 相关

* [Klaviyo](https://help.sesami.co/zh-cn/apps-integrations/klaviyo.md) — 根据预订数据发送定向电子邮件
* [Sesami 即时预订](https://help.sesami.co/zh-cn/yu-ding/booking-features/instant-booking.md) — 无需 Shopify 结账的预订
* [订单](https://help.sesami.co/zh-cn/apps-integrations/shopify/orders.md) — 预订在 Shopify 订单中的显示方式


---

# 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://help.sesami.co/zh-cn/apps-integrations/shopify/customers.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.
