> 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/pt-br/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participants/referrals-and-events/mark-an-event-as-a-test-for-advocate.md).

# Marcar um evento como teste para o Advocate

Você pode enviar *eventos de teste* para o seu programa Advocate ao vivo para confirmar que sua configuração funciona como esperado. É recomendado marcar esses eventos como testes na sua conta da impact.com depois que eles forem enviados. Os eventos de teste serão removidos de análises, relatórios e faturamento relacionados à receita.

{% hint style="warning" %}
**Aviso**: Marcar um evento como teste não pode ser desfeito.
{% endhint %}

1. No menu de navegação à esquerda, selecione ![](https://impact-1.gitbook.io/docs/emvxfLrwrlacc4y3y02Y/~gitbook/image?url=https%3A%2F%2F4048883401-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FwMLlMoFBtKJa8ptd3zaw%252Fuploads%252Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%252Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg%3Falt%3Dmedia\&width=300\&dpr=3\&quality=100\&sign=71dd50ef\&sv=2) **\[Engage]** → **Participantes**.
2. Pesquise e selecione a **nome** do participante para o qual o evento foi enviado.
3. Dentro do *Visão geral* aba do perfil do participante, encontre o evento na *Eventos* tabela na parte inferior da página.
   * Saiba mais sobre as seções de um [perfil do participante](/brand/pt-br/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participants/advocate-participant-profiles-explained.md).
4. Passe o cursor sobre o evento e, em seguida, selecione **Marcar como teste**.

   <div data-with-frame="true"><figure><img src="https://526234278-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FVPA8wVu3vPYWyMJwlEmq%2FUntitled%20design.png?alt=media&amp;token=e2afc2fa-415d-48ba-868f-65c428f7337b" alt="" width="563"><figcaption></figcaption></figure></div>
5. Revise os detalhes do evento e, em seguida, selecione **Marcar como teste**.
6. Por fim, confirme que você deseja **Marcar como teste**. Esta ação é irreversível.


---

# 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/pt-br/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participants/referrals-and-events/mark-an-event-as-a-test-for-advocate.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.