This feature is part of an open beta and is subject to change.
You can check that user-provided data is being hashed and sent to Google Analytics using Google Chrome's Developer Tools.
Validate your implementation using Chrome Developer Tools
- In the Google Chrome browser, right-click your web page, then select Inspect.
- Open the Network tab and reload the page while the tab is open.
- In the search bar, enter "google".
- Find the network request to "google-analytics.com/g/collect" (or "analytics.google.com/g/collect" on some browsers).
- While the row is selected, open the Payload tab to view the list of query string parameters.
- Look for a parameter "em" with a hashed string as the value. The value should start with "tv.1~em" followed by a long string of characters. If you see the "em" parameter, this means that the tag is picking up and hashing the data.
If you see the "em" parameter but you only see "tv.1~em" without a long hashed string following it, then you’re sending the enhanced conversions parameter but it’s empty. This may happen if user-provided data isn’t available at the time of conversion.
Troubleshoot missing user-provided data
If you don't see hashed data being sent to Analytics, try these troubleshooting tips:
- Make sure that both user-provided data collection is activated and user-provided data capabilities are allowed. Both settings must be turned on for user-provided data collection to work properly.
- If you set up user-provided data collection with Tag Manager, make sure you use the correct variable types (e.g., User-Provided Data, Custom JavaScript) when configuring your GA4 Event tag.
- If you set up user-provided data collection with Tag Manager, make sure you publish the container changes by clicking Submit in the top right of the container.