Inventory and categorization
Before you publish a banner, Agreely builds an inventory of your site's cookies and storage objects, proposes a category and a purpose for each, then asks you to review anything it could not classify with enough confidence. The principle is simple: the categorizer proposes, but a person decides.
The four-step flow
- Scan. Agreely opens your site in a headless browser and records the cookies set, the storage keys (local/session storage) and the third-party hosts contacted.
- Auto-categorization. Each item is first matched against a deterministic reference list of known cookies. Unknown or ambiguous items are sent to the categorizer (see Sub-processor: Anthropic), which proposes a category and bilingual purpose descriptions, along with a confidence score.
- Human review. Any entry with low confidence (below 0.85) is flagged "to review" until a person confirms or corrects it. You confirm or correct the category and purpose; you can also reclassify any other entry.
- Publish. Nothing is served automatically: from the Publishing page, a person sees what the version will cover, then publishes it; the categories and purposes it holds become the ones the visitor sees.
The categories
Agreely sorts every non-essential item into one of these categories, plus the strictly-necessary category that is never subject to consent:
| Category | Role |
|---|---|
| Strictly necessary | Required for the site to work (session, security, the consent mechanism itself). Never subject to consent. |
| Functional | Comfort and preferences (language, widgets, chat). |
| Analytics | Audience measurement and statistics. |
| Marketing | Advertising, retargeting, social networks. |
The categorizer may propose "strictly necessary" for a first-party cookie; if it does so with high confidence, the entry is not flagged "to review". It can never assign it to a third-party cookie: such a proposal is brought down to "Functional" and flagged "to review". So review the entries classified strictly necessary before publishing: deciding is your organization's call. Each purpose carries a French label and an English label, shown to the visitor in their language.
The "to review" queue
In the dashboard, under Cookie banner (cookies) > your site > Cookies, a badge shows the number of entries "to review". For each cookie or storage key you see:
- the name, domain and attributes (expiry,
httpOnly,secure,sameSite, third-party or not); - the proposed category and purpose;
- a control to confirm, correct or reclassify.
An entry you edit manually is permanent: the automatic pipeline never touches it again. Your decisions win.
The publish gate
Publishing a banner is blocked while any entry is still "to review". This gate is enforced server-side: as long as a low-confidence cookie or storage key has not been confirmed or corrected by a person, publishing is refused. High-confidence entries do not block: they appear in what the Publishing page shows before you publish.
An item that is missing from the latest scan (plain inventory drift) is not part of this gate: it does not block publishing. Only to-review entries (low confidence, undecided) block it.
What the scan does not replace
The scan explores a representative subset of your site; it does not necessarily explore every page or every journey. It also does not see server-side cookies (see Server side). The inventory is a documented starting point, not an exhaustive certificate.
Agreely helps document and demonstrate your categorization work; your organization, as the responsible party, remains accountable for the accuracy of the declared purposes and the legal validity of consent.