The DSR tab in the cookie banner lets visitors send privacy requests. With Premium, you can decide which account identifiers they can provide to help you locate their records. This changes the options under Account / Verification Method, not the whole request form.
1. Open the domain’s DSR settings
Select your domain in QookieQloud and open Settings → Privacy requests. The switch at the top controls whether the DSR tab is shown in the banner. The identification options are below it.
2. Choose the standard options
New configurations start with the five existing options: customer number, order number, account email, member ID / national ID, and other identifier. Switch off the options you do not use. Standard options remain in the admin panel so you can switch them back on later.
3. Add your own identifier
Click Add identifier and enter the field name visitors should see, for example Fortnox customer ID. Keep it enabled. You can rename, disable or remove your own options. Enter only a field name here; the visitor enters their actual ID in the banner. Your custom name is displayed as written and is not translated automatically.
4. Save and check the banner
Click Save, reload your website and open the banner’s Privacy Rights tab. A new domain keeps the standard set until you save a change. If an older open form no longer matches your settings, reload it before sending a request.
What will the visitor see?
- Several active options: a dropdown and one input for the selected identifier. The visitor does not fill in every identifier.
- One active option: its input is shown directly, without a dropdown.
- No active options: the identification section is hidden. The rest of the DSR form remains available while DSR is enabled.
Switch off the five standard options, add “Fortnox customer ID”, keep that option enabled and save. The visitor sees one field with that name. This is a custom reference field, not a connection to Fortnox: QookieQloud does not look up or verify the ID there.
What happens to the submitted value?
The identifier is optional; the form’s contact email is still required. The value is stored encrypted with the request and is available in its handling view and the merchant notification email. It is also included in the visitor’s confirmation email if they request a copy. The name of a custom field is saved on the request, so existing requests retain that name if you later rename or remove the option.
A customer number does not automatically prove identity. Enable only the identifiers you actually need for handling requests.
