> ## Documentation Index
> Fetch the complete documentation index at: https://help.autoady.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Install and verify website tracking

> Prove domain ownership, install the supplied script, and confirm the first received event.

A complete website setup has three separate checks: ownership verified, tracking installed, and an event received. Passing the ownership check alone does not prove tracking works.

## Before you begin

You need access to your website publishing tools and either its DNS or the supported verification-file location. A website owner or editor can configure installation; a viewer needs someone with that access to make changes.

## Add and verify the site

1. Open [Websites](https://www.autoady.io/web-analytics) and choose **Add website** when available.
2. Enter the **Website name**, **Public HTTPS domain**, **Timezone**, and **Currency**. Save, then open **Install & settings**.
3. Copy the ownership proof shown for this site. Add the supplied DNS TXT record, or publish the supplied HTTPS verification file with its exact contents.
4. Choose **Check DNS** and confirm **Domain verified**. Use the exact domain and token shown by the product rather than creating your own.

## Install and prove tracking

1. Copy this site's **Install tracking** snippet into the website through your publishing workflow. Preserve its website key, endpoint, and environment.
2. Connect your consent manager using the supplied **Consent change handler**. Leave analytics off until the visitor allows analytics; marketing requires its own permission.
3. Publish the website change. Visit the intended domain with the configured environment and grant the relevant consent for the test.
4. Return to **Install & settings** and check the **Test first event** or **Production first event** timestamp. Refresh the website report to confirm the visit.

You can also follow the installation-agent instructions supplied in the panel. Copying instructions is not installation: the website change must be published and verified by a received event.

## If the checks disagree

* **Verification fails:** check the record or file contents, domain, and propagation, then repeat the ownership check.
* **Snippet unavailable:** read the setup reason. A missing tracking endpoint requires workspace setup; a viewer may also lack permission to see the code.
* **Verified but no events:** confirm the script is on the published page, the key and environment agree, and analytics consent is being sent.
* **Only test events appear:** test and production are separate. Confirm the intended production setting before expecting live visitors in the production view.

Next: [Track actions and outcomes](/websites/events).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.