> For the complete documentation index, see [llms.txt](https://messagematch.gitbook.io/messagematch-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://messagematch.gitbook.io/messagematch-docs/getting-started/installation-testing.md).

# Installation Testing

You can test if your MatchAgent is connected properly serveral ways, either in the MatchAgents tab- see verification box for confirmation, on the Chrome Extension when hovering over a page, or by testing the product directly by appending the allowed UTM's after install and loading that new link in the browser.

After the first time a successful CampaignMatch is rendered, it should propagate in the analytics soon after refreshing in the dashboard.

***

Attend our weekly office hours to ask questions and gain assistance as needed: <https://meet.messagematch.com/joinofficehours>

Tue/Thur 12-1pm PST, 3-4pm EST


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://messagematch.gitbook.io/messagematch-docs/getting-started/installation-testing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
