> 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/partner/it/di-cosa-vorresti-saperne-di-piu/getting-started/readme-1/im-a-creator/step-4-apply-to-creator-campaigns.md).

# Passaggio 4: candidati alle campagne per creator

In una campagna per creator, completerai una serie di post sui social media, chiamati *attività*—per il brand, in cambio di un compenso maggiore.

Ogni attività ha una vista *dei dettagli* che spiega cosa devi includere nei tuoi contenuti. Ricordati di annotare eventuali link di tracciamento o pagine di destinazione da includere nel tuo post!

Trova e [candidati](https://help.impact.com/partner/it/di-cosa-vorresti-saperne-di-piu/campaigns/creator-campaigns/campaign-management/join-creator-campaigns.md) alle campagne per creator nella pagina **Scopri →** [**Campagne**](https://app.impact.com/secure/mediapartner/marketplace/influencer-marketplace-flow.ihtml?) .

## Dopo aver inviato la candidatura

1. Il brand riceverà la tua candidatura. Potrebbe negoziare con te il compenso, le attività o altri dettagli.
2. Quando la candidatura viene approvata o rifiutata, riceverai un'email e una notifica nell'app.
3. Il tuo [contratto](https://help.impact.com/partner/it/di-cosa-vorresti-saperne-di-piu/platform-features/working-with-brands/contracts/contracts-explained-for-partners.md) definitivo mostrerà i dettagli e i requisiti delle attività del brand.
4. Le attività della campagna che ti sono state assegnate saranno visibili nella tua [dashboard](https://help.impact.com/partner/it/di-cosa-vorresti-saperne-di-piu/account-management/account-settings/manage-tasks-as-a-partner.md) o nella schermata [Le mie attività della campagna](https://help.impact.com/partner/it/di-cosa-vorresti-saperne-di-piu/campaigns/creator-campaigns/campaign-management/manage-campaign-tasks-as-a-creator.md) .

<div data-with-frame="true"><figure><img src="https://1708986086-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fb2rE79d9UhOKZQLgzSqx%2Fuploads%2Fgit-blob-7650fc918038c974e03026d86e0bde570f601149%2Fd84a1b9f701b91a78545786aab2d65c75bdd6c38b569a46cacc68963fb814c20.svg?alt=media" alt=""><figcaption></figcaption></figure></div>


---

# 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/partner/it/di-cosa-vorresti-saperne-di-piu/getting-started/readme-1/im-a-creator/step-4-apply-to-creator-campaigns.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.
