Amsterdam Buyer Kit

Last updated

15 June 2026

Current conclusion

The current public product uses necessary first-party cookies for session continuity, CSRF-protected form submissions, and admin security. It does not currently load advertising pixels, third-party tracking cookies, or third-party browser analytics scripts. Because no non-essential third-party browser tracking is currently loaded, Amsterdam Buyer Kit shows this disclosure page instead of a cookie banner.

Strictly necessary cookies

abk_session_id: first-party anonymous session cookie used to keep a buyer file and CSRF-protected API requests connected.
abk_admin: admin-only signed session cookie used after protected backoffice login.
CSRF token: generated by the backend and sent through the API proxy for write requests. It is tied to the session and protects forms from cross-site request forgery.

Internal analytics

The backend stores internal product events such as buyer-file views, calculator submits, toolkit requests, contact requests, guide page views, report example views, and CTA clicks. Some public guide/report events are triggered by first-party frontend code and sent to the backend through the same API proxy as product forms. These events are used for reliability and product improvement. They do not use third-party browser scripts.

Source attribution

The backend can preserve first-party source information, such as UTM parameters or referrer, when those are present on backend/API requests. This is intended for internal product attribution only. Before paid ads or broader marketing tracking, the owner must review whether a consent banner or preference center is required.

Non-essential tracking

Advertising cookies, cross-site tracking pixels, third-party analytics scripts, and profiling tools are not currently used. If they are added later, Amsterdam Buyer Kit must update this page and add a consent mechanism before loading them.

Questions