# Visit evidence

> API type: visit. Attribute a visit to your destination URL.

Source: https://dashboard.adquest.batriders.ir/docs/quest-evidence/visit · Audience: Developers · Section: Quest evidence

## Record the visit before completion

Start the quest without a timer. On the participant’s visit action, call client.visitQuest(id) and open its redirectUrl. This records the attributed visit. For web hosts, preserve the user gesture when opening a new tab to avoid popup blocking. For a WebView, handle the destination with the host’s URL policy.

**Visit flow — client and config from the Quest evidence overview**

```typescript
await client.startQuest(questId, { requiresTimer: false });
const { redirectUrl } = await client.visitQuest(questId);
// Open redirectUrl through your web/native navigation handler.
// When the participant returns and requests completion:
const completion = await questRequest(config, questId, "complete");
```

## Understand what is verified

> **A visit is not a conversion.** A tracked destination visit does not prove a purchase or signup occurred on that site. Use Verified event when you need evidence of a product outcome.

- Check that completion cannot succeed before the configured visit evidence.
- Test a blocked popup, returning from an external app and a repeated visit.

## Next steps

- [Quest evidence overview](https://dashboard.adquest.batriders.ir/docs/quest-evidence): The shared request helper and the completion flow.
- [Quest actions API](https://dashboard.adquest.batriders.ir/docs/api/quest-actions): Every request and response.
- [Set up this quest in the dashboard](https://dashboard.adquest.batriders.ir/docs/dashboard/quests/visit): For publishers: configure and publish the quest.