> 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/other/zh/reference-documentation/direct-tracking-parameters.md).

# 直接跟踪参数

impact.com 直接跟踪使用附加到落地页 URL 的参数，为由以下内容标识的合作伙伴创建点击事件 `irmp`，无需使用跟踪链接。使用这些参数来创建该点击事件。

| 参数名称                | 说明                                                           |
| ------------------- | ------------------------------------------------------------ |
| `irmp`              | 必填。impact.com 合作伙伴 ID。用于从落地页 URL 参数创建点击。                     |
| `irad`              | impact.com 广告 ID。用于作为从落地页 URL 参数创建的点击的广告 ID。如果省略，则使用活动广告 ID。 |
| `subid1`            | 由合作伙伴定义的点击跟踪值。通常用于版位、活动或合作伙伴内部报告值。                           |
| `subid2`            | 由合作伙伴定义的点击跟踪值。通常用于关键词、受众或流量细分值。                              |
| `subid3`            | 由合作伙伴定义的点击跟踪值。通常用于其他合作伙伴侧细分。                                 |
| `sharedid`          | 与品牌共享的合作伙伴定义跟踪值。                                             |
| `trafcat`           | 由合作伙伴提供的流量类别，例如与品牌约定的版位或流量类型。                                |
| `trafsrc`           | 由合作伙伴提供的流量来源，例如搜索、社交、展示或其他来源标签。                              |
| `kw`                | 与点击相关的关键词或搜索词。                                               |
| `matchtype`         | 与点击相关的搜索匹配类型。                                                |
| `adnetwork`         | 与点击相关的广告网络或平台。                                               |
| `adposition`        | 广告展示的位置。                                                     |
| `adplacement`       | 广告展示的版位。                                                     |
| `adcampaign`        | 与点击相关的外部活动名称。                                                |
| `adcampaignid`      | 与点击相关的外部活动 ID。                                               |
| `adcampaigngroup`   | 与点击相关的外部活动组名称。                                               |
| `adcampaigngroupid` | 与点击相关的外部活动组 ID。                                              |
| `adgroup`           | 与点击相关的外部广告组名称。                                               |
| `adgroupid`         | 与点击相关的外部广告组 ID。                                              |
| `adtype`            | 与点击相关的外部广告类型或媒介。                                             |
| `adname`            | 与点击相关的外部广告或创意名称。                                             |
| `adid`              | 与点击相关的外部广告或创意 ID。这不同于 `irad`.                                |
| `prodcat`           | 与点击相关的产品类别。                                                  |
| `prodsubcat`        | 与点击相关的产品子类别。                                                 |
| `prodsku`           | 与点击相关的产品 SKU。                                                |
| `param1` - `param4` | 随点击传递的品牌定义元数据值。这是 4 个单独的参数。                                  |


---

# 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/other/zh/reference-documentation/direct-tracking-parameters.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.