> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/partner/zh/ni-xiang-liao-jie-shen-me/platform-features/marketing-content/newsletters/view-all-brand-newsletters.md).

# 查看所有品牌新闻简报

查看品牌的应用内新闻简报可让你随时了解更新、销售、佣金和合作机会，确保你始终保持同步并随时把握机会。

1. 从 [*待办事项列表*](/partner/zh/ni-xiang-liao-jie-shen-me/platform-features/dashboard/manage-your-to-do-list.md) 在仪表板上的小组件中，前往已列出的 *新闻简报* 任务。
2. 选择 **查看新闻简报**.
3. 在 *新闻简报* 屏幕，选择你要查看的新闻简报。
   * 也可选择 **品牌** ![](https://1152657667-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fb2rE79d9UhOKZQLgzSqx%2Fuploads%2FcPa68OltbIaD3QiiS0J4%2FDrop-down.svg?alt=media\&token=db083c4f-c5aa-47e3-91ab-9a2b9a2152ea) **\[下拉菜单]** 以按特定品牌筛选新闻简报。


---

# 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.impact.com/partner/zh/ni-xiang-liao-jie-shen-me/platform-features/marketing-content/newsletters/view-all-brand-newsletters.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.