# Launch & Edit Campaigns

### Launch a campaign

\
Check a preview of the draft campaign outlook in the "**Preview**" section. \
If you wish, campaign drafts can be deleted.

Once you are ready follow the following:

1. If haven't done yet. **verify** your space
2. Deploy the campaign: click on the "**Publish**" button and sign the contract
3. After deployment, the **campaign URL** will be activated (it may take a few seconds, please refresh the page)
4. Users with access to the link **will be able to participate in the campaign**.
5. You can see the deployed campaigns in the "hidden section"

### Go live and publish the campaign&#x20;

1. Click on the publish button.
2. Your campaign is now public. Everyone on Tide website will be able to see and participate in the campaign.

Here is an example.&#x20;

1. Approve the reward tokens&#x20;

<figure><img src="/files/V8Dr9NGKP4oYniXxGfUc" alt=""><figcaption><p>Approve rewards</p></figcaption></figure>

2. Publish the campain. Now the campaign contract is deployed and you will be given a link to access the campaign. You can now preview and test that everything is working properly. Only users with the link are able to see and participate.
3. When your campaign starts, click the "List" button on the right side of the screen. Now everyone can see your campaign live on the Tide Platform.

<figure><img src="/files/hEUPnbAkaWRpCzBZrwIB" alt=""><figcaption><p>Publish your Web3 quest campaign</p></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://fiveelementslabs.gitbook.io/tide/projects/campaigns/launch-and-edit-campaigns.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
