Public pages use no advertising trackers. The secure portal uses an essential session cookie and the service providers described in our privacy policy.

Skip to main content
For web teams

For web agencies and developers

When a business receives a letter, its web team or agency is often the first call. This page shows how to check the client's case file against the site's tag manager and consent settings, one request at a time. The letter describes a visit on a stated date, and the work is to match each request in the case file to the setting or code that sent it.

First

Before you start

  • Work from the documents your client shares with you: the letter, its exhibits and the files posted in its case portal. A business may share case materials with a technical adviser who needs them for the matter.
  • Keep the access code out of tickets, chats and public posts. It is your client's credential, so ask for the documents instead.
  • Change nothing yet. Export the configuration as it stood on the visit date first, and keep the export.
  • When you test the live site, do not submit any form.
Case file

What the case file contains

  • A network record. The requests the browser made during the visit, in order, with where each one went, when it went, what it carried and how the receiving server answered.
  • Screenshots. The pages as the browser showed them, including any cookie banner, each with the time it was taken.
  • Timestamps. The time of the visit, of each screenshot and of each request. Times are in UTC unless the page says otherwise.
  • SHA-256 values. Fingerprints of the files, so you can confirm a file has not changed.

Some case files have a second part that shows what the site sent after the banner's own reject or necessary-only control was used.

Where the portal offers a copy of the network record to download, it is a redacted copy: some request and response bodies are left out, and the complete record is preserved. Most desktop browsers can open the copy in their Network panel and show it the way they show live traffic.

Method

Check the case file, step by step

  1. Confirm the files. On a Mac, open Terminal and run shasum -a 256 followed by a space and the file. On Windows, open PowerShell and run Get-FileHash followed by the file and -Algorithm SHA256. A value that matches the one in the case file means the file has not changed.
  2. Set the time window. Note the start and end of the visit in UTC, and convert them to the time zone your tag manager and server logs use.
  3. List the destinations. For each request to a third party, note the host, the page address it carried, the page title, the event name, any identifiers such as cookie values, and whether it went before or after a choice on the banner. Field names differ from one vendor to the next, so look for your own page address in each request.
  4. Find the version that was live. Open the tag manager's version history and find the version published before the visit and not replaced until after it. Export that version and note its number and publish date.
  5. Match each request to a tag. Match the host to the tag or base code that sends to it, the event name to the tag's event settings, and the page to the trigger that fired. Note the tag, its trigger and its consent settings.
  6. Read the consent setup for that date. Check whether tags waited for consent, what applied before any choice, what the reject or necessary-only choice was set to do, and whether any tag ran without a consent condition, under an opt-out or implied-consent model, or in a mode that still sends measurements while consent is denied.
  7. Look outside the tag manager. Check for tags pasted into the theme, header or footer; plugins and extensions; and chat, scheduling, video or review widgets, which load tags of their own. If the site sends events to its own subdomain for a server-side container, check that container's configuration and logs for where it forwarded each event.
  8. Line up the screenshots. See what the banner showed and when, and place each request beside the screenshot nearest to it in time. A request that comes before the banner screenshot was sent before the visitor could choose.
  9. Write it up request by request. For each request, give the tag or code that sent it, its trigger, the container version and the consent setting, and mark any request you could not match.
Corrections

If something does not match

  • If the case file names the wrong website or business, or shows a request you can show the site did not send, ask for a factual correction. Name the request or field, what is wrong, the correction and your source, such as the exported container version.
  • Your client sends it through its secure portal, or by email to contact@privacyresolve.com with the subject “Factual correction request.”
  • A factual review is separate from the legal merits, and a correction request does not change the deadline in the letter.
Records

Preserve, then fix

  • Keep the tag manager's version history, consent logs and server logs. Do not delete or unpublish old versions while a matter is open.
  • Before you change a setting, keep a dated note of the old and new settings.
  • To see how the site behaves now, run the five-minute reject button test in a private window and keep the result. A change today does not alter what happened on the visit date.
  • Fixing the site protects future visitors. It does not resolve the claim about the earlier visit, which the business resolves separately.
Scope

What to leave to others

  • Questions about the law, the claim or a settlement belong to your client and its attorney. Privacy Resolve is not a law firm and gives no one legal advice.
  • Your client, or its attorney, can send questions about the record to contact@privacyresolve.com. Include the website domain.

Related guides: How to Read Your Evidence File, How to Read a Website Data Transmission, Remove Unauthorized Website Trackers and Request a Factual Correction.

Privacy Resolve is not a law firm. Each claim is pursued directly by the person who sent the letter. Nothing here is legal advice.