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
← Back to Resources
Remediation·November 10, 2026·6 min read

Site Search and Form Events: What Tags Send When Visitors Type

How site search terms and form events reach analytics and advertising vendors through page addresses, titles and event parameters, and how to set tags so they do not.

PR
Privacy Resolve
Last reviewed November 10, 2026

A search box and a form are where visitors type in their own words. On a health, legal or financial site, those words are often the most sensitive thing on the page. This guide explains how search terms and form activity reach analytics and advertising vendors, quotes the vendors' documentation for each route, and lists the settings that keep the words on the site.

How does a site search term leave the website?

Usually in the page address: many search boxes load a results page whose address carries the search words, and every tag that reports page addresses then sends those words to its vendor.

A search for knee pain on https://example.test might load https://example.test/search?q=knee+pain. Any tag that sends the page address with its events now carries the search words. That includes the page address Google Analytics 4 sends with every event and the page location in the Meta Pixel's HTTP header data. Results pages often repeat the words in the page title too, and GA4 sends the page title with every web event. These sample addresses illustrate the pattern; they are not a record of a real visit.

What does GA4 do with a search results page?

With enhanced measurement's site search option on, GA4 sends a view_search_results event with a search term parameter whenever the page address carries a search parameter such as q, s, search, query or keyword.

Google says the event is detected from "the presence of one of the following 5 query parameters in the URL," those five being q, s, search, query and keyword, and that the list can be extended. The search term parameter populates GA4's Search term dimension.

GA4's data redaction can remove listed query parameters before the data leaves the browser; Google says redaction happens "before data is sent to Analytics." It applies to the parameters you list in fields such as the page address and the referring page address. It does not change words in the path, such as /search/knee-pain, or in the page title.

What does the Meta Pixel's Search event carry?

Meta's Search event takes a search string parameter, which Meta describes as the "String entered by the user for the search."

Even without a Search event, the pixel's PageView on a results page carries the page location. Meta says "PageView standard events record the referrer URL of the page that triggered the function call," and its documentation lists page location among the HTTP header data the pixel collects.

What do form events send?

GA4's form events send the form's ID, name and destination, and form_submit adds the submit button's text; form_start fires the first time a visitor interacts with a form in a session.

Google lists the parameters as the form's HTML id and name attributes, the "URL to which the form is being submitted," and the "text of the submit button, if present." It lists no typed values among them. The context is the identifying detail: a form named new-patient-intake, a destination such as /appointment-request/thank-you, or a submit button that reads "Request my consultation" says what the visitor began.

Three other routes deserve a check:

  • User-provided data collection in GA4. Google describes it as sending "specific hashable fields, such as email addresses, phone numbers, and addresses," with an option to "detect user-provided data on your website automatically." Leave it off where forms collect health, financial or legal details.
  • The Meta Pixel. Meta says the pixel collects form field names and that "[w]e don't capture field values unless you include them as part of Advanced Matching or optional values." Check both. The Meta Pixel on Health Websites covers advanced matching.
  • Thank-you pages. A page reached only after a form is sent tells every tag on it that the form was sent.

Can typed text reach a vendor before a form is submitted?

It can through session replay and similar tools that record page interactions, which is why masking or excluding form fields matters; GA4's form events report that a form was used, not what was typed.

Replay vendors' masking and exclusion controls differ, and a setting that covers input boxes may not cover the text around them. See Session Replay on Healthcare Sites: Masking Settings by Vendor for each vendor's documented controls. Chat widgets and embedded form or scheduling tools can run their own analytics as well, so list them in the site's tag inventory.

Why do search terms and form entries matter legally?

Because the Wiretap Act protects a communication's "contents," which 18 U.S.C. § 2510(8) defines as "any information concerning the substance, purport, or meaning of that communication," and typed words sit closest to substance.

The Ninth Circuit drew a line in In re Zynga Privacy Litigation, 750 F.3d 1098 (9th Cir. 2014). On its facts, the court treated the information sent there, a user ID and the address of the page the user was viewing, as record information rather than contents, and it affirmed dismissal. Id. at 1107, 1109. The same opinion said that "[u]nder some circumstances, a user's request to a search engine for specific information could constitute a communication such that divulging a URL containing that search term to a third party could amount to disclosure of the contents of a communication." Id. at 1108-09.

For a site owner the practical reading is simple. Requests that carry a visitor's own words are the ones most likely to be argued about, and keeping those words out of every vendor request avoids the argument. The federal prohibition itself is in 18 U.S.C. § 2511(1)(a); Federal Wiretap Act for Websites explains how it applies to tracking code.

How should search and forms be configured?

Keep search words and form details out of everything sent to a vendor: send searches by POST or strip the search parameter, turn off search and form events, and keep advertising tags off results and form pages.

  1. Search method. A search form that submits by POST keeps the words out of the address. If it must use GET, keep advertising tags off results pages and redact the parameter in analytics.
  2. Titles. Give results pages a fixed title, such as "Search results," instead of one that repeats the words.
  3. Analytics events. Turn off GA4's site search and form interactions where searches or forms concern health, money or legal matters, and leave user-provided data collection off.
  4. Advertising events. Keep search terms and form details out of advertising platforms, and keep lead or scheduling events off health forms.
  5. Thank-you pages. Keep advertising tags off pages reached only after a form is sent.
  6. Replay. Mask or exclude every field, or keep replay off forms entirely.
  7. Server routes. Apply the same rules to any server container; see Meta Conversions API and Server-Side Tagging.

How do you test without sending real information?

Use made-up words and a test entry on a staging copy, watch the Network panel for each vendor's host, and never submit a real intake, appointment or contact request to check a configuration.

Search the site for an unusual made-up word, then use the Network panel's search, which Chrome documents as a way "to search across request headers, payloads, and responses." Any request that contains the word shows a vendor receiving it. Repeat after clicking the banner's refusal, and keep a dated note of what you found. The five-minute Reject button test walks through the Network panel setup.

What sources does this guide rely on?

This guide relies on vendor documentation, the statute text and the decision listed here, quoted from the pages linked. Checked on November 10, 2026.

General information only, not legal advice, and not a substitute for the advice of an attorney. Laws, deadlines, defenses and outcomes vary by jurisdiction and facts.