Capture a useful network log for support
Use this guide when a loading problem cannot be explained by the installation result alone.
Reproduce the issue on a test page you control, without signing in to a customer account or entering personal information.
1. Record one short reproduction
Open the browser’s developer tools and its Network panel before loading the page. Clear the request list, then reproduce one specific action, such as opening the page without a consent choice. Keep rejected and accepted scenarios in separate recordings. Use Preserve log only when following a reload or redirect is necessary.
2. Describe the observation
Note the page, time and timezone, browser, intended test region, consent choice and exact symptom. Identify the relevant failing resource and its status or blocked reason. A request log shows network activity; it does not prove that every browser-storage operation was prevented.
3. Export only when needed
In Chrome, choose the sanitized HAR export. This excludes sensitive headers such as Cookie, Set-Cookie and Authorization. It is not a guarantee of anonymity: inspect URLs, query parameters, request bodies and response content before sharing. If you cannot remove confidential content safely, provide a short description of the failing request instead.
4. Send the minimum useful evidence
Use the support channel requested for your case. Include the reproduction steps, expected result and actual result. Do not publish a raw HAR file in a support article, public issue or community post. Do not share passwords, API keys, full consent exports or cookie values.
Expected result: support can identify the failing step from a short, relevant reproduction without receiving unrelated personal data.