> For the complete documentation index, see [llms.txt](https://docs.claimr.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.claimr.io/tasks/common-tasks/visit-a-link-task.md).

# Visit a link task

## What are Visit a link tasks?

Visit a Link tasks in claimr allow you to reward users for simply clicking on a specified URL. These tasks are perfect for driving traffic to a landing page, referral link, article, external app, or any other destination. Once the user visits the link, the task is considered complete: no proof or submission required.

Use Visit a link tasks to:

* Drive traffic: Direct users to campaign pages, partner sites, or custom URLs.
* Promote engagement: Highlight specific features, announcements, or calls to action.
* Integrate referral flows: Use masked or dynamic links to connect with external reward systems.

{% hint style="info" %}
For detailed information about general task settings, including task name, header, description, rewards, dependencies, and more, refer to our [Task Settings](/tasks/task-settings.md) article.
{% endhint %}

## Create a task

<figure><img src="/files/HY0useARuCBTcZ0XbMEJ" alt="" width="563"><figcaption></figcaption></figure>

To create a Visit a Link task:

1. Go to your quest and click <mark style="color:green;">**+ Create new task**</mark>.
2. Under the Category section, select **Web**.
3. Choose **Visit a Link** from the list of task types.
4. Click <mark style="color:green;">**Continue**</mark> to proceed to task settings.

## Configurate a task

Visit a Link tasks offer an extensive set of configuration options. While only the destination link is required, you can fine-tune how the link is displayed and how users interact with it.

<figure><img src="/files/OJcRn1TXQuOgQ7NbHP4B" alt="" width="375"><figcaption></figcaption></figure>

#### Required field

* Completion points: This is the base value shown at the top of the game UI. It may or may not match the actual reward the user receives.
* Points multiplier (%): Optional bonus that increases the user’s final reward by a percentage. For example, if the selected reward is 500 and the multiplier is 10%, the final payout will be 550 points.
* Recurrence: Define how often the game task can be completed:
  * Once
  * Daily
  * Weekly
  * Multiple times (immediate repeat)
* Link: The full URL users will be redirected to.

#### Display options

* Button text: Customize the button label that users click to visit the link.
* Timeout (in seconds): Add a delay before the task is marked as complete. For example, setting 600 means the task won’t be marked complete until 10 minutes after the click.
* WIP text: Show a custom “work in progress” message during the waiting period (only applies if a timeout is set).
* Link text: Customize how the link is displayed below the button. Useful when you want to show a branded or shortened link instead of the full destination.
* Hide link: Toggle this on to remove the link preview entirely and display only the button.
* Enable copy link button: Let users copy the link with one click (appears next to the button).

## How it looks to users

Once the task is live, users will see a button prompting them to open the link.&#x20;

<figure><img src="/files/5ME6gVy7SyeIY7KprQGY" alt="" width="375"><figcaption></figcaption></figure>

Depending on your settings, they might also see:

* A visible link below the button, with either the raw URL or a custom label.
* A copy icon that allows them to copy the link to clipboard.
* A delay (timeout) before the task can be marked complete.<br>

After clicking the button, the user is taken to your destination URL, and the system logs the action. \
If you’ve set a timeout, points will be awarded only after the specified delay.


---

# 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://docs.claimr.io/tasks/common-tasks/visit-a-link-task.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.