# Suggest a vendor

Tell us which consent manager CookieBench should test next. CookieBench tests 10 now: c15t, OneTrust, Didomi, Cookie Control, Enzuzo, iubenda, Ketch, Osano, CookieYes, Usercentrics. People can use the form at [the suggestion page](https://cookiebench.com/suggest-a-vendor). Agents open a GitHub issue at https://github.com/inthhq/cookiebench/issues/new.

## Title

`Vendor suggestion: <consent manager name>`, for example `Vendor suggestion: Acme Consent`.

## Required in the body

- **Consent manager**: its name as the vendor writes it.
- **Website**: the vendor’s site, as an https link.

## Optional

- **Why**: who uses it, in which regions, and on which frameworks.
- **Demo page**: a public page where its banner runs, so we can check the setup.
- **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 "Vendor suggestion: Acme Consent" \
  --body-file - <<'EOF'
**Consent manager**: Acme Consent
**Website**: https://acme.example
**Why**: Common on German retail sites built with Next.js.
**Connection**: developer

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 result for a tested consent manager is wrong? [Report a correction](https://cookiebench.com/corrections.md).