> 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/brand/zh/what-would-you-like-to-learn-about/platform-features/ads/manage-ads/deep-link-an-asset.md).
# 为资产添加深度链接
如果您已为您的计划启用了深度链接，则您上传的每个素材都可以配置为将访问者深度链接到特定的着陆页 URL。例如，如果您为某个特定产品创建了一个素材，您可以将该素材指定为直接将访问者发送到该产品的特定 URL。
#### 设置深度链接允许域名
要使深度链接生效，您必须提供允许域名。提交这些域名可使流量落地到您网站上的深度链接页面。了解有关 [允许域名及其设置方法](/brand/zh/what-would-you-like-to-learn-about/account-administration/program-settings/tracking-settings/set-up-permitted-domains-for-deep-linking.md).
#### 为特定素材设置深度链接
1. 在左侧导航栏中，选择  **\[Engage]** → **内容** → **广告**.
2. 在右上角，选择 **创建广告**  **\[下拉菜单]**，然后选择您要创建的素材类型。
3. 在……下 *着陆页*，选择以下任一项 **默认** 或 **自定义** 来自  **\[下拉菜单]**，然后输入用于素材重定向的目标着陆页 URL。
4. 在 URL 字段中，输入 **完整 URL** （不含 `https://`）即您希望广告将访问者发送到的位置。
5. 选择 **保存**.
#### 批量为素材设置深度链接
这将更新多个素材，使其深度链接到您网站上的同一页面。
1. 在左侧导航栏中，选择  **\[Engage]** → **内容** → **广告**.
2. 将鼠标悬停在要编辑的素材上，然后选择  **\[未选中复选框]**.
3. 选择 **更多操作**  **\[下拉菜单]** → **更改着陆页**.
4. 使用  **\[下拉菜单]** 选择 **自定义**.
5. 在……中 **网址** 字段，输入 **完整 URL** （不含 `http://`）即您希望素材将访问者发送到的地址。
* 可选地，  **\[开启]** 进行 **如果 Impact 未检测到您的应用已安装，请将此广告的移动流量重新定向**.
6. 选择 **确定**.
---
# 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/brand/zh/what-would-you-like-to-learn-about/platform-features/ads/manage-ads/deep-link-an-asset.md?ask=&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.
