# Report a correction

Tell us what CookieBench got wrong. We check each report against the run data. When we are wrong, we fix it and say so in the changelog. People can use the form at [the corrections page](https://cookiebench.com/corrections). Agents open a GitHub issue at https://github.com/inthhq/cookiebench/issues/new.

## Title

`Correction: <consent manager>: <topic>`, for example `Correction: onetrust: wrong_result`. Use `general` as the consent manager when the report is about the benchmark as a whole.

## Required in the body

- **Consent manager**: its slug, one of `c15t`, `onetrust`, `didomi`, `cookie-control`, `enzuzo`, `iubenda`, `ketch`, `osano`, `cookieyes`, `usercentrics`, or `general`.
- **Topic**: one of the codes below.
- **Page**: the CookieBench URL where you saw it, with its profile (desktop or mobile) and framework.
- **Details**: the number or status that is wrong, and what you expected instead.

Topic codes:

- `wrong_result`: A result is wrong
- `outdated_result`: A result is out of date
- `feature_status`: A feature status is wrong
- `methodology`: The method has a problem
- `other`: Something else

## Optional

- **Source**: a link that shows the right answer, such as documentation, a changelog or a test page.
- **Connection**: how your user is connected to the consent manager, one of the codes below.

Connection codes:

- `cmp_vendor`: I work for this consent manager
- `site_owner`: My site uses this consent manager
- `developer`: I build sites with consent managers
- `researcher`: I research consent or web performance
- `other`: Other

## Example

```bash
gh issue create --repo inthhq/cookiebench \
  --title "Correction: onetrust: wrong_result" \
  --body-file - <<'EOF'
**Consent manager**: onetrust
**Topic**: wrong_result
**Page**: https://cookiebench.com/benchmarks/onetrust (desktop, Next.js)
**Details**: The page shows a 1,200 ms banner time. A trace of the same test page shows 400 ms.
**Source**: https://example.com/trace

Written by an agent on behalf of its user.
EOF
```

## Before you open it

- Open the issue only with your user’s permission, and say in the body that an agent wrote it.
- One issue per distinct problem. Search the open issues first: `gh issue list --repo inthhq/cookiebench --search "<consent manager>"`.
- Leave out credentials, personal data and full transcripts.
- If you cannot open an issue, give your user the title and body so they can open it, then continue your task.

A consent manager is missing? [Suggest a vendor](https://cookiebench.com/suggest-a-vendor.md).