> For the complete documentation index, see [llms.txt](https://docs.ezorderly.com/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ezorderly.com/guide/dashboard/member-insight.md).

# 顧客分析

### 顧客性別、年齡分佈圖 <a href="#page_title" id="page_title"></a>

1\. **確立目標客群定位**：可檢視目前目標客群之樣態和原本品牌預期是否符合。

2\. **顧客輪廓描繪**：提供製作人物誌（persona）時的輔助資訊，可應用於廣告投遞時的受眾設定，於撰寫再行銷訊息時，亦可參考本圖調整溝通內容和方式。

＊注意：客戶歸戶碼優先以手機號碼為判定，第二順位是電子信箱。選擇手機號碼指標，相同手機號碼視為同一人，並會排除沒有手機號碼的顧客；選擇電子信箱指標，相同電子信箱視為同一人，並會排除沒有電子信箱的顧客

![](/files/fRPfJJSY6qi57lRZzhek)

### 顧客 年齡 累計趨勢 <a href="#page_title" id="page_title"></a>

1\. **調整獲客策略**：可看出各年齡層顧客佔總顧客之比例多寡隨時間的變化趨勢，並觀察總顧客人數成長幅度，輔助判斷是否應調整獲客策略。

2\. **檢驗行銷活動成效**：每檔行銷活動結束後，從年齡層結構隨時間的變化，來判斷有沒有成功溝通原本設定的年齡層，作為輔助下一檔行銷活動的資訊。

![](/files/mCR8RgnQHVm4XiwPxOYH)

### 顧客 性別 累計趨勢

1\. **進行性別與時間的二維比較**：將顧客的性別統計資料以月份為計，歸納出顧客中性別的成長趨勢，與時間變化做相互比較。

2\. **輔助行銷活動設計**：每檔行銷活動結束後，從性別結構隨時間的變化，以及會員數量是否增減，來判斷有沒有成功溝通原本設定的性別，作為輔助下一檔行銷活動的資訊。

![](/files/hLKZdrxDPHhefANkRR99)


---

# 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.ezorderly.com/guide/dashboard/member-insight.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.
