GA4 User-Provided Data: Separate the Property and Tag Controls

By Dave TanguayPublished Updated Editorial draft

Quick Answer

GA4 user-provided data and User-ID are different features. Before an approved change, identify the fields, collection route and receiving property. Review property settings and tag behavior separately: turning off processing in a property does not, by itself, establish that the tag has stopped collecting the data.

An old rollout announcement is a poor substitute for an implementation record. Start with what the feature currently does and what your approved setup is meant to send, rather than enabling it because an article predicted a cookie deadline.

Identify the data feature precisely

Google’s user-provided data documentation distinguishes a business-assigned, non-personally identifiable User-ID from supported hashable user-provided fields such as email, phone and address. It currently labels user-provided data collection an open beta. A value being hashed does not make it equivalent to User-ID or establish permission to collect it.

Have the responsible owner approve the purpose, permitted fields and relevant privacy requirements before implementation. This guide explains technical review boundaries; it does not determine legal compliance or authorize collection.

Map the separate controls

Google says acknowledging the feature policy is permanent, although its collection checkbox can be unchecked. With that checkbox unchecked, the property does not process the data, but the Google tag may still collect it. The documentation separately identifies tag controls and Measurement Protocol implementation changes.

Layer Question to resolve
Approved purpose Which permitted fields and uses has the responsible owner approved?
Property Which exact property and relevant streams are affected by the setting?
Website tag Does collection use automatic detection, manual variables or code, and what is the actual behavior?
Other route Does a server or Measurement Protocol implementation send the fields independently?

Keep evidence for each layer. An unchecked property box is evidence about a setting, not a complete inventory of scripts, server routes or information handling.

Review an illustrative change request

Suppose a hypothetical website owner asks to stop sending user-provided data. The developer first identifies the property and every implemented sending route. The approved task specifies which collection behavior must stop and which unrelated analytics events should remain available.

After the authorized change, test with approved non-sensitive data and inspect the relevant tag or server evidence. Check the receiving behavior through the provider’s supported tools. Record the time and scope of the observation without copying customer details into a ticket, screenshot or analytics parameter. This example is a proposed review method, not an account change we performed.

If a route remains unknown, keep that as an unresolved dependency. Do not declare the whole site’s collection disabled because one interface changed.

Keep the cookie premise current

The original article anticipated a general third-party-cookie phaseout and promoted proposed API integrations. Our cookie-dependency guide explains why current browser behavior and provider support need checking. Those historical predictions should not become a present technical requirement.

Similarly, a consent-policy notice is a separate matter with its own scope. The notice-response guide explains how to preserve that distinction. Review the actual requirement before changing either settings or public wording.

Key Takeaways

  • Identify user-provided data separately from User-ID.
  • Review property processing, tag collection and server routes.
  • Keep permission decisions and technical observations explicit.

Frequently Asked Questions

Does hashing establish that collection is permitted?

No. It is a technical transformation. The approved purpose, provider requirements and applicable privacy obligations still need review.

Does a property setting describe every sending route?

No. Inspect the implemented website and server routes separately, then verify the approved change within its defined scope.

Archives