> 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/technical-integration-guides/integrate-with-bigcommerce.md).

# 与 BigCommerce 集成

BigCommerce 是品牌用于创建和管理网店的平台。通过此集成，你可以招募合作伙伴来推广你的网店、跟踪转化并在一个便捷的位置管理订单。

要使用此集成，你必须是 BigCommerce 商家，并通过 impact.com 的 [BigCommerce 应用](https://www.bigcommerce.com/apps/impact-partnership-cloud/).

查看 impact.com 的完整 [BigCommerce 集成指南](https://integrations.impact.com/integration-guides/for-brands/plugin-integrations/e-commerce/integrate-with-bigcommerce) 在集成门户上。


---

# 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/technical-integration-guides/integrate-with-bigcommerce.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.