> For the complete documentation index, see [llms.txt](https://integrations.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.impact.com/ai-solutions/mcp-skills/brand-skills/brand-order-investigation-pack-skill.md).

# Brand Order Investigation Pack Skill

Use this skill to look up conversion and action-tracking status for a list of order IDs from live data and return a summary table. It shows which orders were found, which were not found, and whether their actions are payable, with three next actions tied to specific rows.

### Prerequisites

* MCP access enabled on your impact.com brand account.
* Client connected per [MCP Quick Start](https://integrations.impact.com/ai-solutions/mcp-quick-start.md).
* A list of order IDs (OIDs) in a CSV or pasted text, plus the program ID (`campaignId`) they belong to.

### Install the skill

{% file src="/files/VuLbCFT8gZJImLEf9Zcx" %}

1. Download or copy the skill package above.
2. Install it in Claude, Cursor, or VS Code using [Install an MCP Skill](https://integrations.impact.com/ai-solutions/mcp-skills/install-an-mcp-skill.md).
3. Use this package's frontmatter when the AI client asks for metadata:
   * Name: `Brand order investigation pack`
   * Description: `Look up conversion and action-tracking status for a list of brand order IDs from live MCP and return a summary table. Use when the user pastes or attaches a CSV/list of OIDs and asks why orders did not convert, whether actions are payable, or for a bulk order-status brief.`
   * Folder name (Cursor / VS Code): `brand-order-investigation-pack`
4. With impact.com MCP connected, prompt: "Run the order investigation pack on the attached CSV of order IDs."


---

# 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://integrations.impact.com/ai-solutions/mcp-skills/brand-skills/brand-order-investigation-pack-skill.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.
