Keeping plumbing inquiry data out of public analytics

The decision to make first

A marketing team may want conversion measurements without sending a customer’s problem description, address or contact details into analytics events. Measure a limited event such as a consented submission success while keeping field values and private request identifiers out of the payload.

What the handoff should contain

Document permitted event names, public page categories, consent behavior and the form fields that must never be included in analytics.

Suggested wording to approve

Example wording: “Website analytics measure general usage when permitted. The details you submit for service are used through the inquiry process, not copied into marketing event labels.”

Test the difficult case

Submit fictional distinctive values and inspect the network requests to confirm those values do not appear in analytics calls. Do not put customer details into URL query strings, page titles or event parameters merely to make reports easier to read.

Worked example

Fictional example: Use a distinctive fictional name and address in a form test. After submission, inspect permitted analytics requests for those exact strings and for the private request identifier. Passing means the general conversion event can be observed without carrying the form content, and declining analytics prevents the measurement integration from loading.

Review it in operation

Repeat the check after form or tag changes and review whether new event names accidentally reveal request-specific information.

Check before you launch

• Measure a limited event such as a consented submission success while keeping field values and private request identifiers out of the payload.
• Document permitted event names, public page categories, consent behavior and the form fields that must never be included in analytics.
• Submit fictional distinctive values and inspect the network requests to confirm those values do not appear in analytics calls.
• Repeat the check after form or tag changes and review whether new event names accidentally reveal request-specific information.

Related guides