Run your first consent check

Start with your personal workspace#

Sign in and open your dashboard. CookieTrail prepares a personal workspace for your sites, reports, and usage. You can start your first check immediately; creating a team is optional.

If you audit with colleagues or want to keep a client’s work separate, create a team workspace in the switcher below the sidebar logo. Check the workspace name before adding a site: its sites, history, plan, and check allowance belong to that workspace.

Connect your workspace to Claude#

1. Choose Create key & connect Claude on your dashboard. This creates a workspace Development key valid for 30 days.
2. Select Copy setup for Claude, then paste the complete message into Claude Code. The message includes the API key and connection instructions.
3. Ask Claude to add your public site, choose a visitor location, run the first audit, and explain the saved findings. It can inspect your repository and help implement and verify fixes.

For custom access, expiry, or audit origins, open API & MCP. To start in the browser, choose Run my first check here on the dashboard, or add a site from Sites.

Run a check in the browser#

1. Enter a public website address, such as example.com. You can use a specific page URL to check that page.
2. Choose the visitor location you want to investigate. Available locations are Germany, United Kingdom, United States East, United States West, Canada, and Singapore.
3. Start the check. The first-check flow saves your site and queues its audit together. You can give the saved site a recognizable name later from Edit site.

Use a publicly reachable HTTP or HTTPS site. Localhost, private hostnames, IP-address URLs, embedded credentials, and custom ports are not supported. Authentication, bot protection, or a site outage can prevent usable evidence.

Know what happens next#

Your check first appears as Queued, then Checking when a worker starts it. CookieTrail observes first load, acceptance, and rejection in fresh browser sessions. The report shows progress as evidence arrives; you can leave the page and return from Sites or Run log.

Starting the same site and location again while its check is active reopens the active check rather than using another slot. Activity and the sidebar bell show recently finished checks, including interrupted checks. Completion is shown in the app; no result email is sent.

Turn the first result into a fix#

1. Read the consent path coverage before drawing a conclusion.
2. Open the highest-priority finding and inspect its observed cookies, consent state, and screenshots.
3. Use the suggested fix and copy the fix brief for the person changing your tags or consent platform.
4. Record progress and a note. After deploying the change, choose Verify this fix on the original finding.